All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: selinux@tycho.nsa.gov
Subject: Re: SELinux on Debian (Sid)
Date: Fri, 18 Jun 2004 19:01:43 +0000	[thread overview]
Message-ID: <20040618190143.GQ362@lkcl.net> (raw)
In-Reply-To: <20040614033955.GA14338@yggdrasil.localdomain>

On Sun, Jun 13, 2004 at 10:39:55PM -0500, Greg Norris wrote:
> On Sun, Jun 13, 2004 at 06:26:22PM -0500, Greg Norris wrote:
> > I case anyone else encounters this issue, I've submitted a bugreport
> > to the Debian bug-tracking system.  You can view it at
> > "http://bugs.debian.org/254219".
> 
> Ok, I've finally managed to get the package to install... it turns out
> that I needed to include chkpwd.te and inetd.se in my policy
> selections.  I'm not actually using the corresponding software for
> either, but they apparently include some definitions which are needed
> by other policies.

well done :)

greg, i am curious: the debian selinux policy packages that i
installed (1.12-1) i didn't get asked any questions about policy
selections.

at least, i don't _remember_ being asked any...

what gives?

-- 
-- 
Information I post is with honesty, integrity, and the expectation that
you will take full responsibility if 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.

  parent reply	other threads:[~2004-06-18 19:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 14:44 SELinux on Debian (Sid) Magnus Therning
2004-06-09 17:50 ` Luke Kenneth Casson Leighton
2004-06-10  8:13   ` Russell Coker
2004-06-10 22:04     ` Luke Kenneth Casson Leighton
2004-06-10 12:09   ` Magnus Therning
2004-06-10 21:46     ` Luke Kenneth Casson Leighton
2004-06-10  8:17 ` Russell Coker
2004-06-10 12:03   ` Magnus Therning
2004-06-10 13:53     ` Russell Coker
2004-06-10 21:54     ` Luke Kenneth Casson Leighton
2004-06-11  4:13       ` Russell Coker
2004-06-11 20:40         ` Luke Kenneth Casson Leighton
2004-06-12  2:11           ` Russell Coker
2004-06-12  8:14             ` Luke Kenneth Casson Leighton
2004-06-12  8:15             ` Luke Kenneth Casson Leighton
2004-06-11 23:26         ` Greg Norris
2004-06-12  8:19           ` Russell Coker
2004-06-12 14:37             ` Greg Norris
2004-06-13  0:29               ` Russell Coker
2004-06-13  1:28                 ` Greg Norris
2004-06-13  7:54                   ` Luke Kenneth Casson Leighton
2004-06-13 15:40                     ` Greg Norris
2004-06-13 16:03                       ` Greg Norris
2004-06-13 23:26                         ` Greg Norris
2004-06-14  3:39                           ` Greg Norris
2004-06-14 11:38                             ` Russell Coker
2004-06-14 12:31                               ` Greg Norris
2004-06-18 19:01                             ` Luke Kenneth Casson Leighton [this message]
2004-06-13 18:29                       ` Luke Kenneth Casson Leighton

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=20040618190143.GQ362@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.