Rahul,
There are 2 primary trains of though for doing it this way.
1. For several reasons related to how the sosreport plugin architecture works, processing an entire sosreport in the way it would have to be processed to do this sort of work is problematic. Bryn and the sosreport team are working on that issue as time allows, but it's still several iterations away.
2. During our discussions with people who want this usability, having it decoupled from the process of creating an sosreport is desirable. Since many systems have limited or no outbound connectivity, an sosreport for one system is usually analyzed and uploaded from another. Another desire for uses is to maintain a 'gold' copy of the sosreport and then upload the 'cleaned' one for troubleshooting, etc. The current sosreport architecture would make it difficult to create two copies at the same time.
Does that answer your question?
Thanks,
Jamie Duncan, RHCE Senior Technical Account Manager Red Hat, Inc.
jduncan@redhat.com
w-804.343.6086 c-804.307.7079 tech support-888.GO.REDHAT
----- Original Message -----
From: "Rahul Sundaram" metherid@gmail.com To: "Development discussions related to Fedora" devel@lists.fedoraproject.org Sent: Wednesday, June 4, 2014 2:34:05 PM Subject: Re: self-introduction: Jamie Duncan
Hi
On Wed, Jun 4, 2014 at 2:23 PM, Jamie Duncan < jduncan@redhat.com > wrote:
Hi, Everyone.
My name is Jamie Duncan. I work in the Strategic Customer team at Red Hat. One of the big things that our more security-minded (and some of the vaguely paranoid) users ask for is an easier way to obfuscate data in an sosreport before they send it out to Red Hat Support.
There have been several failed attempts at this over the years, and soscleaner ( https://github.com/jduncan-rva/soscleaner/ ) is another attempt at it.
Is there a particular reason, this feature isn't being integrated into sosreport itself?
Rahul