linux-kernel - Re: [ANNOUNCE] Merkey's Kernel Debugger

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 for Android: free password hash cracker in your pocket

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

Message-ID: <48987A24.3060000@nortel.com>
Date:	Tue, 05 Aug 2008 10:04:52 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	jmerkey@...fmountaingroup.com
CC:	Nick Piggin <nickpiggin@...oo.com.au>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	Josh Boyer <jwboyer@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger

jmerkey@...fmountaingroup.com wrote:

> If you go back to LKML from 2000, this debugger has been around for 10
> years.  I agree not in the hands of the public, but its very mature
> in comparison to kdb or kgdb.

Without public use, it's difficult to determine that there aren't any 
nasty interactions.

If you want to maximize your chances of getting this code into the 
kernel, you might want to read Jonathan Corbet's post, "[PATCH] A 
development process document, V2".  It discusses the normal process, how 
to prepare patches for submission, etc.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/