All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: Colin Walters <walters@verbum.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: Linuxfromscratch.org
Date: Mon, 28 Jul 2003 19:17:07 +0200	[thread overview]
Message-ID: <20030728191705.G5998@lemuria.org> (raw)
In-Reply-To: <1059336784.13122.260.camel@columbia>; from walters@verbum.org on Sun, Jul 27, 2003 at 04:13:04PM -0400

On Sun, Jul 27, 2003 at 04:13:04PM -0400, Colin Walters wrote:
> That is clever, but it seems to me you'd still have to take into account
> the machine's usage.  Again, none of what you listed above should be
> going to a file server, for example.  

Those were just examples. You can put your stuff into ANY traffic. If
the machine has any outside connections whatsoever, and be they DNS
requests, you have a channel you can use.

> to a development workstation.  So it doesn't seem too unlikely that some
> machine learning based IDS, somewhere, will eventually pick up on it. 
> Once that happens in multiple places, people will get suspicious.
> I guess all I'm saying is that the chances of a trojan going undetected
> for a long period of time approaches nil.

True, but "long period of time" is relative. All you need is enough
time to accomplish your goal. That may be months or seconds, depending
on what the goal is.

Again, we see why SELinux is what it is - all the race conditions and
other timing-based exploits show that "we'll catch them quickly" isn't
enough. Catching them works if you talk about theft or something else
where you can still undo the damage. It doesn't work for murder or
rape. Same in computer security: If you have something where the damage
likely can't be undone, monitoring isn't the correct approach because
it acts too late.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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-07-28 17:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22  1:42 Linuxfromscratch.org Charlie Watts
2003-07-22 20:06 ` Linuxfromscratch.org Russell Coker
2003-07-22 20:49   ` Linuxfromscratch.org Dean Anderson
2003-07-23 15:09     ` Linuxfromscratch.org Carsten P. Gehrke
2003-07-23 15:44       ` Linuxfromscratch.org Russell Coker
2003-07-23 20:01         ` Linuxfromscratch.org Dale Amon
2003-07-23 21:24         ` Linuxfromscratch.org Dean Anderson
2003-07-23 19:34       ` Linuxfromscratch.org karlm
2003-07-23 22:08         ` Linuxfromscratch.org Dean Anderson
2003-07-24 14:06           ` Linuxfromscratch.org Dale Amon
2003-07-24 14:16           ` Linuxfromscratch.org Dale Amon
2003-07-24 14:18             ` Linuxfromscratch.org Dale Amon
2003-07-24 17:40         ` Linuxfromscratch.org Colin Walters
2003-07-24 18:52           ` Linuxfromscratch.org Dean Anderson
2003-07-27 15:28             ` Linuxfromscratch.org Tom
2003-07-27 20:13               ` Linuxfromscratch.org Colin Walters
2003-07-28 17:17                 ` Tom [this message]
2003-07-24 19:42           ` Linuxfromscratch.org Russell Coker
2003-07-27 15:19         ` Linuxfromscratch.org Tom
2003-07-23 20:26       ` Linuxfromscratch.org Lukasz Luzar
2003-07-24  0:29         ` Linuxfromscratch.org Dale Amon
2003-07-24  6:39           ` Linuxfromscratch.org Brian May
2003-07-24 12:32             ` Linuxfromscratch.org Dale Amon
2003-07-23  1:17   ` Linuxfromscratch.org Carsten P. Gehrke

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=20030728191705.G5998@lemuria.org \
    --to=tom@lemuria.org \
    --cc=selinux@tycho.nsa.gov \
    --cc=walters@verbum.org \
    /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.