public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@idb.hist.no>
To: Mircea Ciocan <mirceac@interplus.ro>, linux-kernel@vger.kernel.org
Subject: Re: Is there something that can be done against this ???
Date: Tue, 14 Aug 2001 10:12:08 +0200	[thread overview]
Message-ID: <3B78DD58.3DE697D2@idb.hist.no> (raw)
In-Reply-To: <E15WK98-0007gd-00@the-village.bc.nu> <3B7822E5.9AE35D4A@interplus.ro> <m3itfru5rj.fsf@otr.mynet> <3B782868.95729E1E@interplus.ro>

Mircea Ciocan wrote:
> 
>         OK, I realized is a hoax, I should look at the code first then cry the
> wolf is comming :), but anyhow this crap is VERY effective in
> demonstrating to a clueless IT manager that Linux is oh, sooo easy to
> break in.

Good.  I don't want a clueless it manager administrating a linux box
anyway.
Of course the same applies to NT.  Try creating a unprivileged account
named "administrator" with full access to a faked control panel.  Or
for something a little easier - a fake program named "format" 
or "deltree" that writes the same on screen as the real thing.  
And makes the disk click by seeking. :-)

Any os is sooo easy to simulate a break in. 

>         So at least to learn something from this, is there a way to stop
> completly that crap ???

Don't work for a manager that clueless - or tell him it's a hoax.

Helge Hafting

  parent reply	other threads:[~2001-08-14  8:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  1:24 S2464 (K7 Thunder) hangs -- some lessons learned Eric S. Raymond
2001-08-13  1:41 ` Paul G. Allen
2001-08-13  5:12   ` Christopher Abbey
2001-08-13 12:34 ` Alan Cox
2001-08-13 15:18   ` Eric S. Raymond
2001-08-13 15:46     ` Alan Cox
2001-08-13 15:52       ` Eric S. Raymond
2001-08-13 16:00         ` Alan Cox
2001-08-13 18:56           ` Is there something that can be done against this ??? Mircea Ciocan
2001-08-13 19:19             ` Jakob Østergaard
2001-08-13 19:19             ` Ulrich Drepper
2001-08-13 19:20               ` Mircea Ciocan
2001-08-13 19:41                 ` Aaron Lehmann
2001-08-13 19:53                 ` Chris Meadors
2001-08-13 20:09                 ` Admin Mailing Lists
2001-08-13 22:01                 ` Rik van Riel
2001-08-14  8:12                 ` Helge Hafting [this message]
2001-08-13 19:24             ` Peter T. Breuer
2001-08-13 19:34               ` Eli Carter
2001-08-13 19:32             ` Ben Collins
2001-08-13 19:48             ` Ronald Jeninga
2001-08-13 20:02             ` Richard B. Johnson
2001-08-14  8:02             ` Henning P. Schmiedehausen
2001-08-14  8:16             ` joseph.bueno
2001-08-14 10:00               ` David Schwartz
2001-08-14 12:42                 ` Helge Hafting
2001-08-14 17:10                   ` David Schwartz
2001-08-14 13:16                 ` joseph.bueno
     [not found]                   ` <9lb8vp$10q$1@ns1.clouddancer.com>
2001-08-14 16:34                     ` Colonel
2001-08-15  9:08                   ` Helge Hafting
2001-08-14 17:47                 ` Scott Wood
2001-08-14 21:27           ` S2464 (K7 Thunder) hangs -- some lessons learned Eric S. Raymond
2001-08-14 22:13             ` Alan Cox
2001-08-14  1:45       ` Paul G. Allen
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13 20:00 Is there something that can be done against this ??? Per Jessen

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=3B78DD58.3DE697D2@idb.hist.no \
    --to=helgehaf@idb.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirceac@interplus.ro \
    /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