All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos Anísio Monteiro" <monteiro@ipen.br>
To: Stephen Smalley <sds@epoch.ncsc.mil>, selinux <selinux@tycho.nsa.gov>
Subject: Re: Installation of packages
Date: Mon, 01 Dec 2003 15:54:24 -0200	[thread overview]
Message-ID: <3FCB8050.7060300@ipen.br> (raw)
In-Reply-To: 1070287593.12270.44.camel@moss-spartans.epoch.ncsc.mil

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

Stephen Smalley wrote:

>If you are working from our last public release on nsa.gov, then the
>most important ones are:
>- util-linux (patched login program to set the user security context)
>- openssh (patched sshd to set the user security context)
>- vixie-cron (patched crond to set the user security context)
>
>If you are working from Dan's packages
>(ftp://people.redhat.com/dwalsh/SELinux), then the most important ones
>are:
>- SysVinit (patched init program to perform the initial policy load,
>obsoletes the need to modify your initrd)
>- pam (pam_selinux module and other SELinux modifications to pam)
>- util-linux (login pam configuration modified to use pam_selinux)
>- openssh (patched sshd)
>- vixie-cron (patched crond)
>
>The patched coreutils and procps are certainly useful, but they aren't
>essential to basic system operation.
>
>  
>
And over Debian/testing and Debian/unstable packages ?

Thanks.

-- 
Carlos Anisio Monteiro  <monteiro@ipen.br>
IPEN/CNEN-SP
Sao Paulo - Brasil



[-- Attachment #2: Type: text/html, Size: 1496 bytes --]

      reply	other threads:[~2003-12-01 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 11:58 Installation of packages Carlos Anísio Monteiro
2003-12-01 14:06 ` Stephen Smalley
2003-12-01 17:54   ` Carlos Anísio Monteiro [this message]

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=3FCB8050.7060300@ipen.br \
    --to=monteiro@ipen.br \
    --cc=sds@epoch.ncsc.mil \
    --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.