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 17:30:08 +0000
From: "Petko D. Petkov" <pdp.gnucitizen@...glemail.com>
To: "don bailey" <don.bailey@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: [full disclosure] agile hacking?

try me. I am quite confident that we can make this project into a
salable book but that's not the point. the point is to accumulate
valuable knowledge into one place and if, if this start making some
money you will decide what to do with them. I am for investing them
back into something positive.

moreover, the project is not a Phrack knock-off as you said. It is
very different. As I said, it wont contain explanations but like hands
on tips/tricks and techniques even the most knowledgeable can learn
from or use as a base reference.

On Wed, Mar 19, 2008 at 5:12 PM, don bailey <don.bailey@...il.com> wrote:
> -----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/
>

-- 

Petko D. (pdp) Petkov | GNUCITIZEN | Hakiri | Spin Hunters

gnucitizen.org | hakiri.org | spinhunters.org

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