Re: [Spacewalk-devel] Rationale for "rhncfg-actions should not log the diff of files that are not readable by all"

2012-11-09 Thread Cliff Perry
ff /aron -Original Message- From: Stephen Herr [mailto:sh...@redhat.com] Sent: Thursday, November 08, 2012 1:03 PM To: spacewalk-devel@redhat.com Cc: Parsons, Aron Subject: Re: [Spacewalk-devel] Rationale for "rhncfg-actions should not log the diff of files that are not readable by all&

Re: [Spacewalk-devel] Rationale for "rhncfg-actions should not log the diff of files that are not readable by all"

2012-11-08 Thread Parsons, Aron
le? /aron -Original Message- From: Stephen Herr [mailto:sh...@redhat.com] Sent: Thursday, November 08, 2012 1:03 PM To: spacewalk-devel@redhat.com Cc: Parsons, Aron Subject: Re: [Spacewalk-devel] Rationale for "rhncfg-actions should not log the diff of files that are not readable by

Re: [Spacewalk-devel] Rationale for "rhncfg-actions should not log the diff of files that are not readable by all"

2012-11-08 Thread Stephen Herr
On 11/08/2012 10:34 AM, Parsons, Aron wrote: Can anyone explain the rationale behind commit 7a18b250b07ff4ed0c34fa48e69029c114ec3ab1? I do not have access to the BZ that it references. I don't see the security implications of generating a diff for a non-world-readable file. Unauthorized use

[Spacewalk-devel] Rationale for "rhncfg-actions should not log the diff of files that are not readable by all"

2012-11-08 Thread Parsons, Aron
Can anyone explain the rationale behind commit 7a18b250b07ff4ed0c34fa48e69029c114ec3ab1? I do not have access to the BZ that it references. I don't see the security implications of generating a diff for a non-world-readable file. Unauthorized users can't read the file on the system and you n