From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: [debian] postfix chroot setup from /etc/init.d/postfix isn't working.
Date: Wed, 9 Jun 2004 21:41:26 +0000 [thread overview]
Message-ID: <20040609214126.GF5727@lkcl.net> (raw)
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, but
i have added them to the end of the postfix.te file (which
came up during an "enforcing=no" boot)
allow postfix_cleanup_t postfix_cleanup_t:capability { sys_chroot };
allow postfix_local_t mail_spool_t:dir { remove_name };
allow postfix_local_t mail_spool_t:file { create unlink };
allow postfix_master_t postfix_master_t:capability { sys_chroot };
allow postfix_pickup_t postfix_pickup_t:capability { sys_chroot };
allow postfix_qmgr_t postfix_qmgr_t:capability { sys_chroot };
p.s. yes i tried an exim4 setup with those execve child renaming
tricks and it's all got horribly pear-shaped...
--
--
expecting email to be received and understood is a bit like
picking up the telephone and immediately dialing without
checking for a dial-tone; speaking immediately without listening
for either an answer or ring-tone; hanging up immediately and
believing that you have actually started a conversation.
--
<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 reply other threads:[~2004-06-09 21:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 21:41 Luke Kenneth Casson Leighton [this message]
2004-06-09 23:29 ` [debian] postfix chroot setup from /etc/init.d/postfix isn't working Thomas Bleher
2004-06-10 21:11 ` Luke Kenneth Casson Leighton
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=20040609214126.GF5727@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.