All of lore.kernel.org
 help / color / mirror / Atom feed
From: "paul " <paul@bladestorm.com>
To: Dale Amon  <amon@vnl.com>
Cc: <selinux@tycho.nsa.gov>
Subject: Re: Selinux kernel patches
Date: Fri,  9 Feb 2001 10:41:55 -0500	[thread overview]
Message-ID: <200102091041.AA654180630@bladestorm.com> (raw)

I have seen a lot of these test and it is very hard to learn anything from these.  People have a lot of different definitions for "getting in" which usually includes "if you can't get into your own system then we win", meaning that you see a lot of things attack everything around the system, including the logging system and the routers, along with any firewalls or IDS system that might be present.

Yes, you learn, but what you often learn is not what you are looking to learn.  These kind of tests is like handing out 2,000 can openers to 2,000 15-year-olds and telling them to all be the first to open a can of pea soup.

The security community titans, such as Bruce Schneier, have constantly said that these kind of tests are just a publicity stunt and a waste of time.

If you want to see how good this is, set up a lab, eliminate variables such as someone attacking a border router, and have a few people that know what they are doing bang on the software internally and externally.  You will get much better results and something you can analyze right away.


---------- Original Message ----------------------------------
From: Dale Amon <amon@vnl.com>
Date: Fri, 9 Feb 2001 15:22:25 +0000

>On Fri, Feb 09, 2001 at 10:14:09AM -0500, paul  wrote:
>> These kind of shows never real mount to anything since the "hackers" 
>> will typically attack everything around the box as well, including 
>> the routers.  Besides, these things are more of a publicity stunt 
>> than a bona fide test of the operating system.
>> 
>
>PR or not, if someone does get in, you have learned something. And
>the reason I said "external" for the test was that very reason. I'd
>not want the machine under test to be anywhere *near* anything that
>was really important.
>
>> Our company is working with the findings here and integrating them 
>> into our own distribution, and our plan is to basically bang on it 
>> as much as we can in-house and then bite the bullet and put it out, 
>> patching and upgrading as problems are exposed.
>> 
>
>Which comes down to the resources you have as a company, or
>that I have as a company. I don't think it is such a bad
>idea to have some more impersonal baseline outside of
>ourselves.
>
>At the end of the day, proving security is like proving
>aliens don't exist. If a flying saucer lands in London, you've 
>proven they do; but no matter how much you spend you can 
>never absolutely guarantee the negation. You can only 
>add 9's to your statistical confidence in that conclusion.
>
>-- 
>------------------------------------------------------
>Use Linux: A computer        Dale Amon, CEO/MD
>is a terrible thing          Village Networking Ltd
>to waste.                    Belfast, Northern Ireland
>------------------------------------------------------
>

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

             reply	other threads:[~2001-02-09 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09 15:41 paul  [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-06 20:28 Selinux kernel patches Pete Loscocco
2001-02-08 18:41 ` Dale Amon
2001-02-08 21:37   ` Christopher McCrory
2001-02-06 17:50 Joshua Brindle

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=200102091041.AA654180630@bladestorm.com \
    --to=paul@bladestorm.com \
    --cc=amon@vnl.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.