full-disclosure - Re: [full disclosure] agile hacking?

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]

Date: Wed, 19 Mar 2008 11:12:36 -0600
From: don bailey <don.bailey@...il.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: [full disclosure] agile hacking?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I have no clue how it will go. However, just because no one has done
> it and there are too many IFs, it does not mean that we should not
> approach this problem. 
>

Actually attempting to submit the book to a publisher would probably
not work because they're publishing to make money. How can you make
money off a bunch of people noone knows or gives a shit about? The
publisher isn't going to be technically capable of researching every-
thing the book claims unless it's old news. So, because you've got a
ton of random people contributing that don't necessarily have any
valid credentials the publisher isn't going to be confident releasing
material they can't substantially verify. Hell, if I were a contributor
they'd probably burn the manuscript.

If you publish the book "open source" online, you're just another
Phrack knock-off.

Either way, it's been done.

D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFH4Ul9yWX0NBMJYAcRAu2JAKCy43I6L8Q3WummORPcxDAE3Va+yACgqFqx
Qwo045QXOWstyUwBOdIAI84=
=4+W9
-----END PGP SIGNATURE-----

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