Hi,
the attached patch against the 4.3.2 source [1] implements the solution
I've sketched earlier.
On 2012-Nov-11 23:19 (+), Clint Adams wrote with possible deletions:
* For the next release, make run-parts issue a warning that it changes
the umask, and that this behavior is going
* Clint Adams cl...@debian.org, 2012-11-11, 23:19:
Yes, I'm aware of that. On the other hand: The current behavior seems
insane to me, unless there would be a good reason for by default
changing the umask to a less secure setting, but then that should be
documented.
I agree that the current
On Thu, Oct 18, 2012 at 02:03:57PM +0200, Stefan Klinger wrote:
Suggested fix: By default, run-parts should not change the umask. The
user may still use -u022 to get the original behaviour.
That might surprise anyone relying on the current behavior.
--
To UNSUBSCRIBE, email to
Thank you for looking into this!
On 2012-Nov-11 16:22 (+), Clint Adams wrote with possible deletions:
That might surprise anyone relying on the current behavior.
Yes, I'm aware of that. On the other hand: The current behavior seems
insane to me, unless there would be a good reason for by
On Sun, Nov 11, 2012 at 10:35:46PM +0100, Stefan Klinger wrote:
Yes, I'm aware of that. On the other hand: The current behavior seems
insane to me, unless there would be a good reason for by default
changing the umask to a less secure setting, but then that should be
documented.
I agree
Package: debianutils
Version: 4.3.2
Problem description: As the manual for run-parts describes, it sets the
umask to 022 unless specified otherwise. IMHO this violates the
principle of least surprise: I would (did) not expect any tool to fiddle
with the umask (or any other environment stuff)
6 matches
Mail list logo
