Bug 426004 - /etc/cron.d has permissions 700 - readable/executable only by root
Summary: /etc/cron.d has permissions 700 - readable/executable only by root
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vixie-cron
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-17 18:18 UTC by Need Real Name
Modified: 2008-11-26 00:16 UTC (History)
1 user (show)

Fixed In Version: 4.2-8.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-16 02:06:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2007-12-17 18:18:31 UTC
Description of problem:
Not sure what the advantage is of hiding this directory from non-root users and
requiring root privileges just to see the names of the files added to the crontab.

Shouldn't this have perm 755 like cron.monthly, cron.weekly, cron.daily, etc.?

Are there any secrets we are trying to hide here from non-root users?

Comment 1 Need Real Name 2008-01-01 07:31:07 UTC
Anybody following this bug?
It really is a PITA to have /etc/cron.d hidden.
It means I need to sudo/su just to check what are the cron programs being run.

Please either explain rationale for this non-standard perm or correct.
Either should be easy and quick allowing closure of this bug

Thanks

Comment 2 Need Real Name 2008-01-15 19:11:14 UTC
Anybody following this bug? If so any reason not to fix since fix is soooo easy?

Comment 3 Marcela Mašláňová 2008-01-16 08:51:42 UTC
You're right, but I'd rather fix more bugs in one update.

Comment 4 Fedora Update System 2008-02-13 07:31:18 UTC
vixie-cron-4.2-8.fc8 has been submitted as an update for Fedora 8

Comment 5 Fedora Update System 2008-02-16 02:06:08 UTC
vixie-cron-4.2-8.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.


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