From: Diyab <diyab@diyab.net>
To: russell@coker.com.au
Cc: Kerry Thompson <kerry@crypt.gen.nz>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: SELinux on Slackware 9 with PAM
Date: Mon, 18 Aug 2003 13:29:12 -0400 [thread overview]
Message-ID: <3F410CE8.9060807@diyab.net> (raw)
In-Reply-To: <200308181510.29857.russell@coker.com.au>
Russell Coker wrote:
> On Mon, 18 Aug 2003 13:27, Kerry Thompson wrote:
>
>>- you should mention that the Vixie crond in the SE release has been
>>modified for SELinux and really needs to be installed if you want cron.
>>Alternatively the user would need to modify Dillon's crond code to support
>>the SELinux extensions.
>
>
> http://archives.neohapsis.com/archives/linux/lsap/2001-q1/0142.html
> Solar Designer says some nice things about Dillon Cron at the above URL (the
> Linux Security Auditing Project mailing list - which should be of interest to
> people on this list).
>
> It would be good to have some SE Linux patches to Dillon Cron if someone's got
> the time for the coding.
>
> Especially as Vixie cron seems as good as dead upstream.
>
I noticed Vixie looks dead also, so I guess I'll try fixing Dillon's
crond. I can learn to code along the way and the rest of you can at
least tell me if I did it right once I'm finished. Of course if anyone
else wants to do this or if anyone wants this soon you can go right
ahead and do it.
Timothy,
--
I put instant coffee in a microwave and almost went back in time.
-- Steven Wright
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-08-18 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 7:26 SELinux on Slackware 9 with PAM Diyab
2003-08-18 3:27 ` Kerry Thompson
2003-08-18 5:10 ` Russell Coker
2003-08-18 17:29 ` Diyab [this message]
2003-08-18 17:23 ` Diyab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F410CE8.9060807@diyab.net \
--to=diyab@diyab.net \
--cc=kerry@crypt.gen.nz \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.