From: "Per Jessen" <per@computer.org>
To: "Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Mircea Ciocan" <mirceac@interplus.ro>
Subject: Re: Is there something that can be done against this ???
Date: Mon, 13 Aug 2001 22:00:00 +0200 [thread overview]
Message-ID: <3B776EA500038438@mta3n.bluewin.ch> (raw)
On Mon, 13 Aug 2001 22:20:08 +0300, 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.
This is an EXCELLENT comment - we need to be concerned not just about fact,
but also about perception. For those of you in admin jobs with clueless
IT managers watching over your shoulder, this is a real challenge. Hopefully,
since you have *already* adopted Linux, you'll be able to prove that
this particular script was no threat to Linux.
> So at least to learn something from this, is there a way to stop
>completly that crap ???
> My apologies to get you disturbed.
I think you did rightly so. No apologies needed.
regards,
Per Jessen
regards,
Per Jessen, Zurich
http://www.enidan.com - home of the J1 serial console.
Windows 2001: "I'm sorry Dave ... I'm afraid I can't do that."
next reply other threads:[~2001-08-13 19:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 20:00 Per Jessen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 16:00 S2464 (K7 Thunder) hangs -- some lessons learned 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
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
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=3B776EA500038438@mta3n.bluewin.ch \
--to=per@computer.org \
--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