All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Potter" <robertp72@charter.net>
To: "'SELinux Mail List'" <selinux@tycho.nsa.gov>
Subject: Trust Basics
Date: Tue, 14 Oct 2003 15:29:25 -0700	[thread overview]
Message-ID: <000a01c392a2$a7b24020$d9017444@eng21> (raw)
In-Reply-To: <1066162420.5054.395.camel@moss-spartans.epoch.ncsc.mil>

I suggest we also consider using the concept of time for upgrading our
"trust" of code. This is in addition to other methods of knowing the source.
It is another line of defense.

Not all code has to be trusted immediately, or applied. 

I think this is what all of us do anyway, as we have learned to wait and
listen for problem reports before applying patches.

It is what many of us do when we rescan our download subdirectories with the
latest anti-virus, worm and trojan sigs.

Rob




--
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.

      reply	other threads:[~2003-10-14 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 20:07 [Fwd: Re: trusted vs untrusted packages] Chris PeBenito
2003-10-14 20:13 ` Stephen Smalley
2003-10-14 22:29   ` Robert Potter [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='000a01c392a2$a7b24020$d9017444@eng21' \
    --to=robertp72@charter.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.