[prev in list] [next in list] [prev in thread] [next in thread] 

List:       full-disclosure
Subject:    Re: [Full-disclosure] BEGIN PGP PRIVATE KEY BLOCK
From:       Gary Baribault <gary () baribault ! net>
Date:       2011-04-30 22:17:55
Message-ID: 4DBC8A93.7000005 () baribault ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


He's looking to deny an encripted or signed message??

Gary B


On 04/30/2011 02:51 PM, Valdis.Kletnieks@vt.edu wrote:
> 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.
> 
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    He's looking to deny an encripted or signed message??<br>
    <br>
    Gary B<br>
    <br>
    <br>
    On 04/30/2011 02:51 PM, <a class="moz-txt-link-abbreviated" \
href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</a> wrote:  <blockquote \
cite="mid:249659.1304189516@localhost" type="cite">  <pre wrap="">On Sat, 30 Apr 2011 15:58:19 \
+0530, satyam pujari said: </pre>
      <blockquote type="cite">
        <pre wrap=""><a class="moz-txt-link-freetext" \
href="http://www.google.com/search?sourceid=chrome&amp;ie=UTF-8&amp;q=-----BEGIN+PGP+PRIVATE+KEY \
+BLOCK-----#q=BEGIN+PGP+PRIVATE+KEY+BLOCK+filetype%3Aasc&amp;hl=en">http://www.google.com/search \
?sourceid=chrome&amp;ie=UTF-8&amp;q=-----BEGIN+PGP+PRIVATE+KEY+BLOCK-----#q=BEGIN+PGP+PRIVATE+KEY+BLOCK+filetype%3Aasc&amp;hl=en</a>
 </pre>
      </blockquote>
      <pre wrap="">
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.
</pre>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Full-Disclosure - We believe in it.
Charter: <a class="moz-txt-link-freetext" \
href="http://lists.grok.org.uk/full-disclosure-charter.html">http://lists.grok.org.uk/full-disclosure-charter.html</a>
 Hosted and sponsored by Secunia - <a class="moz-txt-link-freetext" \
href="http://secunia.com/">http://secunia.com/</a></pre>  </blockquote>
  </body>
</html>



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

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic