From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "Helge Hafting" <helgehaf@idb.hist.no>,
"Florian Weimer" <Weimer@CERT.Uni-Stuttgart.DE>,
<linux-kernel@vger.kernel.org>
Subject: Re: SSSCA: We're in trouble now
Date: Mon, 4 Mar 2002 10:40:14 +0100 [thread overview]
Message-ID: <003d01c1c360$96194600$0201a8c0@homer> (raw)
In-Reply-To: <1015028463.2276.231.camel@thanatos> <87bse7nz8g.fsf@CERT.Uni-Stuttgart.DE> <20020304083055.GB21138@hh.idb.hist.no>
----- Original Message -----
From: "Helge Hafting" <helgehaf@idb.hist.no>
To: "Florian Weimer" <Weimer@CERT.Uni-Stuttgart.DE>;
<linux-kernel@vger.kernel.org>
Sent: Monday, March 04, 2002 9:30 AM
Subject: Re: SSSCA: We're in trouble now
> On Sat, Mar 02, 2002 at 09:35:43AM +0100, Florian Weimer wrote:
> [...]
> > That's not necessarily true. Most people cannot circumvent even basic
> > obstacles when it comes to computers, and both industry and
> > legislative might be content with that.
>
> Don't be too sure about that. If a "few" knows how to circumvent,
> they'll release circumvention kits that anybody can use.
>
> Few people can use a new buffer overflow exploit, much
> more can use a rootkit.
Well, even if those who uses a rootkit are many more than those who knows
how to use a buffer exploit, that doesn't mean they represent more than 5%
of all computer users.
My stepfather just recently figured out that you can actually DRAG a window
around the desktop. I don't think he will be using a rootkit in some time,
and I am pretty sure he don't know anyting about SSSCA, nor will he, nor
will he be able to understand if I told him.
(btw. I might very well be ~69.5% off topic now, as I missed some of the
conversation)
_____________________________________________________
| Martin Eriksson <nitrax@giron.wox.org>
| MSc CSE student, department of Computing Science
| Umeå University, Sweden
next prev parent reply other threads:[~2002-03-04 9:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-02 0:21 Thomas Hood
2002-03-02 8:35 ` Florian Weimer
2002-03-02 17:34 ` M. Edward (Ed) Borasky
2002-03-04 8:30 ` Helge Hafting
2002-03-04 9:40 ` Martin Eriksson [this message]
2002-03-04 17:02 ` Paul G. Allen
2002-03-06 4:41 ` Petro
2002-03-06 9:27 ` Helge Hafting
2002-03-02 15:30 ` Paul P Komkoff Jr
2002-03-02 21:58 ` Rik van Riel
2002-03-03 1:29 ` Greg Louis
2002-03-06 4:51 ` Petro
2002-03-02 17:47 ` Jurgen Botz
2002-03-06 5:00 ` Petro
2002-03-06 16:42 ` Alan Cox
2002-03-06 18:24 ` Paul G. Allen
2002-03-06 23:56 ` Petro
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 17:20 Ed Vance
2002-03-06 18:31 ` Paul G. Allen
2002-03-04 19:27 Jesse Pollard
2002-03-01 19:46 Paul G. Allen
2002-03-01 20:27 ` Shawn Starr
2002-03-01 21:29 ` Shawn Starr
2002-03-01 22:19 ` Alan Cox
2002-03-02 3:08 ` Neale Banks
2002-03-02 3:03 ` eddantes
2002-03-02 18:32 ` Alan Cox
2002-03-01 22:47 ` Florian Weimer
2002-03-02 2:59 ` Paul G. Allen
2002-03-06 4:26 ` Petro
2002-03-06 4:41 ` Trever L. Adams
2002-03-06 16:26 ` Rik van Riel
2002-03-06 17:03 ` Richard B. Johnson
2002-03-06 18:16 ` Paul G. Allen
2002-03-06 18:35 ` Trever L. Adams
2002-03-07 22:54 ` Florian Weimer
2002-03-08 2:12 ` Tom Rauschenbach
2002-03-01 20:30 ` Xavier Bestel
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='003d01c1c360$96194600$0201a8c0@homer' \
--to=nitrax@giron.wox.org \
--cc=Weimer@CERT.Uni-Stuttgart.DE \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®