From: Mircea Ciocan <mirceac@interplus.ro>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Is there something that can be done against this ???
Date: Mon, 13 Aug 2001 22:20:08 +0300 [thread overview]
Message-ID: <3B782868.95729E1E@interplus.ro> (raw)
In-Reply-To: <E15WK98-0007gd-00@the-village.bc.nu> <3B7822E5.9AE35D4A@interplus.ro> <m3itfru5rj.fsf@otr.mynet>
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.
So at least to learn something from this, is there a way to stop
completly that crap ???
My apologies to get you disturbed.
Mircea "washing the egg on his face" C.
Ulrich Drepper wrote:
>
> Mircea Ciocan <mirceac@interplus.ro> writes:
>
> > The attached piece of script kiddie shit is the first one that worked
> > flawlessly on my Mandrake box :((( ( kernel 2.4.7ac2, glibc-2.2.3 ),
> > instant root access !!!.
>
> This is a hoax. Try doing something with your "exploited" shell.
>
> --
> ---------------. ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Red Hat `--' drepper at redhat.com `------------------------
next prev parent reply other threads:[~2001-08-13 19:30 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 [this message]
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
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=3B782868.95729E1E@interplus.ro \
--to=mirceac@interplus.ro \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@cygnus.com \
--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 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.