From: Robin Miyagi <penguin@dccnet.com>
To: linux-assembly@vger.kernel.org
Subject: Re: kernel vulnerabilities
Date: Sun, 22 Sep 2002 08:19:04 -0700 [thread overview]
Message-ID: <B0314846716@yoda.dccnet.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0209221525350.704-100000@cannabis.daphnes.ro>
Wouldn't a venue such as comp.os.linux.security be a more appropriate venue
for such a question?
Or are you trolling for help exploiting such vulnerabilities :)
On Sunday 22 September 2002 05:29, halfdead wrote:
> Hey,
> Its been rumoured for a while that certain vulnerabilities reside at
> kernel level in different unix flavours (solaris/bsd/linux). Some of them
> claim to be remotely exploitable (ABfrags.c, ABremkrnl.c, etc.). I have
> seen local kernel vulnerabilities and they seem to be pretty tricky to
> exploit hence i highly doubt that anyone would be able to work out a
> clean remote exploitation. Is any of you guys aware of any method or is
> this just FUD?
>
> - halfdead
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-assembly"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Robin Miyagi<penguin@dccnet.com>
http://www.geocities.com/SiliconValley/Ridge/2544/asm/assembler.html
The funny thing about brakes, is that when they break, they don't brake.
next prev parent reply other threads:[~2002-09-22 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 13:24 asmutils libc fun and games Paul Furber
2002-05-18 23:58 ` h-peter recktenwald
2002-05-30 17:51 ` asmutils - Linux 2.4.18 h-peter recktenwald
2002-09-13 8:09 ` Is this list dead? halfdead
2002-09-13 9:20 ` Frederic Marmond
2002-09-22 12:29 ` kernel vulnerabilities halfdead
2002-09-22 15:19 ` Robin Miyagi [this message]
2002-09-13 9:55 ` Is this list dead? lx
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=B0314846716@yoda.dccnet.com \
--to=penguin@dccnet.com \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).