From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
SELinux List <SELinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: Seusers vs ldap
Date: Fri, 20 Jan 2006 06:25:55 -0700 [thread overview]
Message-ID: <43D0E4E3.40505@cornell.edu> (raw)
In-Reply-To: <43D0E148.6010400@tresys.com>
>
> Now that I think of it loading a random network module into the memory
> space of semanage is a bad idea, we should be limiting the amount of
> trust we put in the alternate (esp networked) backends
Does that mean there will be no networked policy server backend?
I don't trust the pserver very much at the moment :)
--
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 prev parent reply other threads:[~2006-01-20 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 18:25 Seusers vs ldap Ivan Gyurdiev
2006-01-18 18:37 ` Daniel J Walsh
2006-01-18 21:13 ` Joshua Brindle
2006-01-20 8:52 ` Ivan Gyurdiev
2006-01-20 13:10 ` Joshua Brindle
2006-01-20 13:25 ` Ivan Gyurdiev [this message]
2006-01-20 12:00 ` LDAP vs Dbase semantics Ivan Gyurdiev
2006-01-20 12:13 ` Ivan Gyurdiev
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=43D0E4E3.40505@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=sds@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.