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. It's written pythong (2.x), and acts as a secondary tool to process sosreports after they have been created. After several talks with the sosreport developers and many talks with customers, this seems to be the work flow that they desire.
I've submitted soscleaner to Fedora under https://bugzilla.redhat.com/show_bug.cgi?id=1104746 and am looking for a sponsor.
In my spare time I hang out in and around Richmond, VA and spend most of my non-working hours with my wife working on our old 1927 bungalow.
Have a good day, everyone.
Cheers,
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
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
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
Hi again, everyone.
This whole process has been a pretty amazing learning experience for me. I'm not a developer by trade, but a sysadmin and reformed Liberal Arts major. Putting together everything that is needed to truly 'release' a piece of software was humbling and a lot of fun to do (at least in the micro instance that I've done it in).
I documented it, a little bit, in a blog post at http://lostinopensource.wordpress.com/2014/07/10/and-you-think-the-code-is-t... .
Regarding Fedora, so far I have:
Gotten approval for my small app - https://bugzilla.redhat.com/show_bug.cgi?id=1104746
Participated as much as I was able to in a handful of package reviews: https://bugzilla.redhat.com/show_bug.cgi?id=1119095 https://bugzilla.redhat.com/show_bug.cgi?id=1104322 (learned a little here) https://bugzilla.redhat.com/show_bug.cgi?id=1114267
There is also a request for me to become a co-maintainer for the sos project.
My next step is to create the SCM requests.
All of this to say politely that I'm fishing around for a sponsor to be added to the packaging group. My daily work is on the enterprise side of life and I don't seem to have daily interaction with anybody who is able to be a package sponsor.
So if there's anybody out there willing to take a chance on a python fanboy with dreams of the big leagues, I'd be most appreciative.
Jamie Duncan, RHCE Senior Technical Account Manager Red Hat, Inc.
jduncan@redhat.com
From: "Jamie Duncan" jduncan@redhat.com To: devel@lists.fedoraproject.org Sent: Wednesday, June 4, 2014 2:23:34 PM Subject: self-introduction: Jamie Duncan
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. It's written pythong (2.x), and acts as a secondary tool to process sosreports after they have been created. After several talks with the sosreport developers and many talks with customers, this seems to be the work flow that they desire.
I've submitted soscleaner to Fedora under https://bugzilla.redhat.com/show_bug.cgi?id=1104746 and am looking for a sponsor.
In my spare time I hang out in and around Richmond, VA and spend most of my non-working hours with my wife working on our old 1927 bungalow.
Have a good day, everyone.
Cheers,
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