Re: Snowden distributed encrypted copies of NSA docs around ...
by e3pi on Tuesday June 25, 2013 @09:39PM
(#5943590)
Rubber Hose Cryptanalysis:
"Good morning Mr Snowden? How was your sleep last night? Oh yes, that's right, you didn't get any.
So to begin with, No I will not get that light out of your face, What was this you or Mr Greenwald mentioned about having your distributed files securely backed up, and have you a deadman switch Mr Snowden, you understand, in case of your demise? .... a bash shell script? Why the hell you didn't you use python?! This is going to be a problem. How are we going to fix it?"
Re: Snowden distributed encrypted copies of NSA docs around ...
by cheald on Wednesday June 26, 2013 @12:17AM
(#5944162)
Assuming, of course, that you don't experience a network partition. MTAs are partition-tolerant; wget is not.
Whoops, that Github service outage just threw the world into political chaos. :)
Re: Snowden distributed encrypted copies of NSA docs around ...
by jlgreco on Tuesday June 25, 2013 @08:59PM
(#5943470)
It could work, but I know that if I were in Snowden's place I would be more keen on relying on people, and not having to "phone home" (I am fairly confident that news of his demise or "disappearance" would eventually become public).
Re: Snowden distributed encrypted copies of NSA docs around ...
by danbruc on Tuesday June 25, 2013 @09:06PM
(#5943492)
Find one, know the page, obtain the logs who accessed the page, find all. Or catch Snowden and keep updating the page yourself. Not that it can not be done in a similar way but it is non-trivial to get it right.
Re: Snowden distributed encrypted copies of NSA docs around ...
by pyre on Tuesday June 25, 2013 @09:48PM
(#5943624)
| it is non-trivial to get it right.
But malware writers / botnet owners have been doing it for a while.
Re: Snowden distributed encrypted copies of NSA docs around ...
by e3pi on Tuesday June 25, 2013 @11:46PM
(#5944072)
POST EDMS triggered launch, a simmering autonomous viral botnet, foisting ES plaintext onto infected email address lists, pastebin, etc., anything else it can fool CAPTCHA registration, with generating SHA256 signatures, new passwords, the whole open source kitchen sink of paranoidal-crypto-craft to effect public-at-large propagating whistle-blaring incriminating secrets, successfully leaked.
Of course, you'd want to test this and make it more fault tolerant.