Storing secrets on other people's computers

[Christopher Tran]

How about putting it on to twitter so it can be archived into the LOC?

On May 5, 2011, at 6:46 PM, Robert J. Hansen wrote:

>> For the latter, I don't get it -- it's not like keeping the key secret takes a lot of effort -- but it does decrease your security ever so slightly. Besides proving a point, why would you publish?
> 
> Because the _New York Times_ keeps records of all the papers it's ever published.  It can be seen as a highly effective, if low-tech, long-term archival solution.  Paperkey the private certificate, publish it in the NYT, verify the accuracy of the published certificate, and presto: your key is archived for the next 100+ years.
> 
> Honestly, half the reason why I volunteer to publish my certificate in the NYT is for precisely this reason.  I think it'd be kind of cool to (a) have the NYT be my data archive, and (b) get someone else to pay for it.  :)
> 
> (Assuming, of course, the NYT survives its current financial problems.  Which may be a very big if.)
> 
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users

Christopher Tran
http://christran.in/
84730CD9



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3727 bytes
Desc: not available
URL: </pipermail/attachments/20110505/443254b3/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 881 bytes
Desc: This is a digitally signed message part
URL: </pipermail/attachments/20110505/443254b3/attachment.pgp>