From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: [debian] postfix chroot setup from /etc/init.d/postfix isn't working.
Date: Thu, 10 Jun 2004 21:11:12 +0000 [thread overview]
Message-ID: <20040610211112.GG2861@lkcl.net> (raw)
In-Reply-To: <20040609232932.GD2142@jmh.mhn.de>
On Thu, Jun 10, 2004 at 01:29:32AM +0200, Thomas Bleher wrote:
> * Luke Kenneth Casson Leighton <lkcl@lkcl.net> [2004-06-10 01:06]:
> > hi,
> >
> > debian's postfix init.d script does a whole stackload of
> > things like copy over /etc/localtime, /etc/services.
> >
> > it's rather scary.
> >
> > ... and it doesn't work.
> >
> > by disabling the chroot (setting SYNC_CHROOT="") i managed
> > to get postfix to start (and it works)
> >
> > i don't know if i was supposed to have these enabled
>
> IIRC the consensus was that the chroot setup should be disabled. The
> reasoning was that SELinux can provide better protection than a chroot
> and it would just give postfix unnecessary permissions.
oh.
ah.
hmm...
then, the question becomes - how should that information be
relayed?
if it bit me (who is coming into this blind with no prior
knowledge or expectations other than "install it and find out
how to fix it if it's broke") then it's definitely going to
bite other people.
how about having an se-postfix package that puts
SYNC_CHROOT="" into /etc/default/postfix for you?
or, adding an extra question to postfix dpkg questions to
ask?
> Thomas
>
> BTW:
> > allow postfix_cleanup_t postfix_cleanup_t:capability { sys_chroot };
> You can write these as
> allow postfix_cleanup_t self:capability sys_chroot;
> which makes it both shorter and easier to read.
thank you thomas :)
--
--
Information I post is with honesty, integrity, and the expectation that
you will take full responsibility for acting on the information contained,
and that, should you find it to be flawed or even mildly useful, you
will act with both honesty and integrity in return - and tell me.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
--
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:[~2004-06-10 21:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 21:41 [debian] postfix chroot setup from /etc/init.d/postfix isn't working Luke Kenneth Casson Leighton
2004-06-09 23:29 ` Thomas Bleher
2004-06-10 21:11 ` Luke Kenneth Casson Leighton [this message]
2004-06-11 1:07 ` Russell Coker
2004-06-11 23:02 ` Luke Kenneth Casson Leighton
2004-06-12 2:19 ` Russell Coker
2004-06-09 23:39 ` Luke Kenneth Casson Leighton
2004-06-10 2:22 ` Ed Street
2004-06-10 5:10 ` Russell Coker
2004-06-10 11:47 ` Ed Street
2004-06-10 12:20 ` Russell Coker
2004-06-10 19:32 ` Ed Street
2004-06-10 19:52 ` Stephen Smalley
2004-06-10 22:09 ` Luke Kenneth Casson Leighton
2004-06-10 21:22 ` Luke Kenneth Casson Leighton
2004-06-10 20:21 ` Luke Kenneth Casson Leighton
2004-06-11 0:46 ` Russell Coker
2004-06-11 23:11 ` Luke Kenneth Casson Leighton
2004-06-10 20:26 ` Luke Kenneth Casson Leighton
2004-06-10 20:39 ` Ed Street
2004-06-10 22:13 ` Luke Kenneth Casson Leighton
2004-06-10 0:44 ` Ed Street
2004-06-10 20:56 ` Luke Kenneth Casson Leighton
2004-06-10 21:06 ` Ed Street
2004-06-10 21:20 ` Luke Kenneth Casson Leighton
2004-06-10 23:08 ` Ed Street
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=20040610211112.GG2861@lkcl.net \
--to=lkcl@lkcl.net \
--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.