full-disclosure - Re: BEGIN PGP PRIVATE KEY BLOCK

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: Sat, 30 Apr 2011 14:51:56 -0400
From: Valdis.Kletnieks@...edu
To: satyam pujari <satyamhax@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: BEGIN PGP PRIVATE KEY BLOCK

On Sat, 30 Apr 2011 15:58:19 +0530, satyam pujari said:
> http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=-----BEGIN+PGP+PRIVATE+KEY+BLOCK-----#q=BEGIN+PGP+PRIVATE+KEY+BLOCK+filetype%3Aasc&hl=en

118 hits I see.  Most of whom probably Didn't Get The Memo.

However, for bonus points, can you think of a plausible scenario(*) where posting
the private key actually makes sense?  (Hint - what are the crypto implications
of doing this as opposed to posting a revocation cert?)

(*) Besides the obvious "proof I pwned the owner of this key, hard" - I mean
cases where the legit owner intentionally does it for a reason.

Content of type "application/pgp-signature" skipped

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