Re: Bits from the release team: the plans for etch
Stephen Frost <email@example.com> writes:
> * Andreas Barth (firstname.lastname@example.org) wrote:
>> * Stephen Frost (email@example.com) [051026 20:13]:
>> > This is just patently false, as has been pointed out elsewhere. What
>> > security hole, exactly, is created by orphaning a file?
>> Well, if some process (maybe within the package) creates a private log
>> file that contains sensitive information, and this log file can later on
>> be read by a process with much less privileges, this is usually
>> considered as security relevant issue.
> Except log files are supposed to be removed and I don't know of any
> actual case of this happening anyway.
We aren't talking about log files created by the package, but by the
What if the sysadmin has taken the sensitive log and squirreled it
away, saving it for future reference? Is that no longer a supported
> Additionally, this is *not* a problem with the orphaning of the file,
> it's a problem with the reuse of a previously-used uid. I could see
> adding a system to track previously-used uids and not reusing them. I
> don't believe using passwd for that (and keeping unused accounts in
> passwd/shadow/group/gshadow/etc) is appropriate.
Why? What purpose is served by segregating the information?