From: "Ed Street" <blacknet@simplyaquatics.com>
To: "'Debian User'" <rogelio@evoworks.evoserve.com>, <selinux@tycho.nsa.gov>
Subject: RE: modifying utilities to use libselinux
Date: Thu, 27 Jun 2002 08:03:56 -0400 [thread overview]
Message-ID: <004601c21dd2$b6cc86b0$0a01a8c0@ed> (raw)
In-Reply-To: <3D1AB057.1040206@evoworks.evoserve.com>
Hello,
I am going to assume you are using potato :) Perhaps the best thing to
do, if this assumption is true, is go update to woody and use mr coker's
woody deb's located at http://www.coker.com.au/selinux/ you'll need to
do a kernel reconfiguration as well with the kernel-lsm patch
Ed
-----Original Message-----
From: owner-selinux@tycho.nsa.gov [mailto:owner-selinux@tycho.nsa.gov]
On Behalf Of Debian User
Sent: Thursday, June 27, 2002 2:28 AM
To: selinux@tycho.nsa.gov
Subject: modifying utilities to use libselinux
is it wise to modify utiliies to use libsecure? what kind of utilities
besides login and ssh should use libsecure? how about screen? I had a
big problem making it work in selinux.
--
You have received this message because you are subscribed to the selinux
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.
--
You have received this message because you are subscribed to the selinux 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:[~2002-06-27 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 6:27 modifying utilities to use libselinux Debian User
2002-06-27 12:03 ` Ed Street [this message]
2002-06-27 12:35 ` Debian User
2002-06-27 12:41 ` Ed Street
2002-06-27 13:07 ` Stephen Smalley
2002-06-27 19:43 ` Russell Coker
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='004601c21dd2$b6cc86b0$0a01a8c0@ed' \
--to=blacknet@simplyaquatics.com \
--cc=rogelio@evoworks.evoserve.com \
--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.