All of lore.kernel.org
 help / color / mirror / Atom feed
* [refpolicy] userdom_list_user_home_dirs for system cronjobs
@ 2011-12-10  8:49 Sven Vermeulen
  0 siblings, 0 replies; only message in thread
From: Sven Vermeulen @ 2011-12-10  8:49 UTC (permalink / raw)
  To: refpolicy

Hi guys,

We had a case (logwatch) where running logwatch from within a cronjob failed
because /etc/crontab had "HOME=/root" set [1]. The application used the current
working directory for scanning and failed because the job did not have the
proper privileges. As a result, logwatch died out and didn't function.

I think that we have HOME=/ by default, but HOME=/root for system cronjobs
is not all that uncommon. But policy-wise, what is the best way to handle
this?

We can
- document that /etc/crontab must use HOME=/ and leave any job that needs
  HOME=/root for the root users' cronjobs
- allow the necessary privileges for logwatch_t only, or
- grant this to all domains through cron_system_entry

I personally think that the first one (document) is the proper one, but
perhaps one of you have a more profound vision on this?

Wkr,
	Sven Vermeulen

[1] https://bugs.gentoo.org/show_bug.cgi?id=392699

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2011-12-10  8:49 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-10  8:49 [refpolicy] userdom_list_user_home_dirs for system cronjobs Sven Vermeulen

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.