Bug 235369 - /etc/shadow has wrong permissions
/etc/shadow has wrong permissions
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: LiveCD (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-05 09:58 EDT by Ray Strode [halfline]
Modified: 2013-03-05 22:49 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-23 19:58:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ray Strode [halfline] 2007-04-05 09:58:45 EDT
To my great surprise, I discovered this morning that my /etc/shadow file was
world readable.  It didn't really matter, because i'm just on a laptop with only
one user, but I don't think I made it that way.  

I did a livecd install of slightly before test3 and have been synching with
rawhide since.

I asked a few people on IRC to check their shadow files and they were all 0400
so its probably a false alarm, and I did screw it up somehow myself.

Anyway, filing just to be on the safe side, in case there were changes recently
that might be responsible for it.

Feel free to CLOSE -> WORKSFORME if appropriate or whatever.
Comment 1 Phil Knirsch 2007-05-23 10:19:34 EDT
This probably only happens for a livecd install. I've tried it with several
normal installations here and haven't been able to reproduce it.

Maybe check with the livecd guys if they do something special for the
installation? Reassigning to LiveCD component at least for now, as thats the
only real difference i see here.

Read ya, Phil
Comment 2 Jeremy Katz 2007-05-23 19:58:24 EDT
I just did a live install of today's rawhide and it came out looking fine.  I
vaguely remember there being a problem like this at one point that we've since
fixed though, so going to close

Note You need to log in before you can comment on or make changes to this bug.