From: Jeff Johnson <n3npq@nc.rr.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: trusted vs untrusted packages
Date: Tue, 14 Oct 2003 13:26:40 -0400 [thread overview]
Message-ID: <3F8C31D0.2080209@nc.rr.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0310140805090.1093-100000@thoron.boston.redhat.com>
James Morris wrote:
>On Tue, 14 Oct 2003, Russell Coker wrote:
>
>
>
>>Now this raises some interesting issues. If a signed package has a program
>>which relies on some other program (and has a dependency), what happens if
>>the dependency is satisfied by an unsigned package? Installing the unsigned
>>package may not result in the system being fully functional (execution of the
>>file in question may be denied).
>>
>>
>
>This should be like enforcing vs. non-enforcing -- you either want all of
>your packages signed (and the above would fail) or not (just generate a
>warning).
>
>
Not true. The signature mechanism is different than the trust model.
Existence of
signature, or constraint of all all packages must be signed, is not an
adequate definition
of "trust".
73 de Jeff
--
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:[~2003-10-14 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 1:07 trusted vs untrusted packages Russell Coker
2003-10-14 11:33 ` Carsten Grohmann
2003-10-14 17:23 ` Jeff Johnson
2003-10-14 12:06 ` James Morris
2003-10-14 17:26 ` Jeff Johnson [this message]
2003-10-14 23:31 ` Diyab
2003-10-15 0:20 ` Robert Potter
-- strict thread matches above, loose matches on Subject: below --
2003-10-14 16:47 Jeff Johnson
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=3F8C31D0.2080209@nc.rr.com \
--to=n3npq@nc.rr.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.