From: "Andrus Nomm" <a.nomm@wap3.net>
To: <linux-kernel@vger.kernel.org>
Subject: Kernels 2.2 and 2.4 exploit (ALL VERSION WHAT I HAVE TESTED UNTILL NOW!) - removed link
Date: Wed, 19 Mar 2003 16:22:00 +0200 [thread overview]
Message-ID: <000701c2ee22$efe61fd0$0100a8c0@andrus> (raw)
Sorry but it was intended for kernel developers and not for other haxors
;)
It is an linux kernel development team fault that they do not give any
direct instructions how to submit bug, now this eploit is very public
probably.
However, what is done, is done.
next reply other threads:[~2003-03-19 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 14:22 Andrus Nomm [this message]
2003-03-19 16:03 ` Kernels 2.2 and 2.4 exploit (ALL VERSION WHAT I HAVE TESTED UNTILL NOW!) - removed link Alan Cox
2003-03-19 21:10 ` Stuart MacDonald
2003-03-19 23:17 ` Brad Laue
2003-03-20 1:58 ` Joshua Kwan
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='000701c2ee22$efe61fd0$0100a8c0@andrus' \
--to=a.nomm@wap3.net \
--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