All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 9 Jun 2004 23:39:46 +0000	[thread overview]
Message-ID: <20040609233946.GI5727@lkcl.net> (raw)
In-Reply-To: <20040609214126.GF5727@lkcl.net>

On Wed, Jun 09, 2004 at 09:41:26PM +0000, Luke Kenneth Casson Leighton wrote:
> hi,
> 
> debian's postfix init.d script does a whole stackload of
> things like copy over /etc/localtime, /etc/services.
 
 i should be more specific: in the creation of the chroot jail,
 in /var/spool/postfix, the permissions (contexts) are preserved
 and recreated (see file_contexts/programs/postfix.fc)

 i.e., in order for the /etc/init.d/postfix script to create the
 chroot jail, it is necessary to give initrd_t permissions
 sufficient to write to etc_t, amongst other things.

 the chroot jail needs a copy of /etc/localtime and /lib/libnss* and
 such-like.

 clearly from an selinux perspective, the /etc/init.d/postfix
 script cannot be an appropriate place to set up a chroot jail.

 can anyone think of a way in which this could be better achieved?

 bearing in mind that the solution must take into account that
 postfix can be run in a chroot jail or not, depending on
 an administrative decision.

 l.


--
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.

  parent reply	other threads:[~2004-06-09 23:42 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
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 [this message]
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=20040609233946.GI5727@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.