full-disclosure - Re: the agenda

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a8fe69350805161154m3a16789fn1d10e24607d3a7ca@mail.gmail.com>
Date: Sat, 17 May 2008 04:54:24 +1000
From: "Fredrick Diggle" <fdiggle@...il.com>
To: Valdis.Kletnieks@...edu
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: the agenda

yes fredrick is very jealous :> your ability to accidentally crash
software is astounding, almost as astounding as your inability to
determine the actual problem beyond the debug output. You sir are a
genius and Fredrick wishes he was you.

Actually in all seriousness I am jealous of you but it's your
mustache. Is it real or did you glue a squirrel to your face?




On Sat, May 17, 2008 at 3:32 AM,  <Valdis.Kletnieks@...edu> wrote:
> On Sat, 17 May 2008 02:36:33 +1000, Fredrick Diggle said:
>> Has your mustache contributed any opps logs to kernel dev lately
>
> No, but 2.6.26-rc2-mm1 just came out, so expect more soon. :)
>
>> valdis? keep them coming they really benefit society. If you find 10
>> more random crashes in retarded configurations
>
> The config can't be *too* retarded - it's been a *long* time since I managed to
> crash the kernel that *didn't* result in a fix being committed.  So apparently,
> people like Linus Torvalds and Andrew Morton think that the stuff I trip over
> are legitimate bugs that need fixing. And if you actually paid attention to the
> linux-kernel list, you'd already know that the vast majority of "retarded"
> configurations result in either Kconfig breakage or compile-time errors about
> undefined variables or functions.  Runtime breakage is usually indicative of
> actual bugs.
>
> For example, the *last* oops that I reported was a totally legitimate bug - it
> was possible to force SELinux to re-enter some filesystem code it didn't belong
> in if there was memory pressure.
>
> I suspect you're just jealous of my ability to find ways to DoS the kernel :)
>
>
>

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/