WikiLeaks Posts Mysterious 'Insurance' File, page 22
Pages: <<  19    20    21    22    23    24    25  >>
ATS Members have flagged this thread 150 times


reply posted on 1-8-2010 @ 07:52 PM by JBA2848
reply to post by freedommusic



Has anybody thought that maybe tor must be installed and the required ports open on your pc. Tor is used as a ip location verifier. Tor sends out your ip to check on external database to compare to ips allowed access to the file.

Might have to spoof your own pc ip in order to appear as a authentic user. That ip could be military or government ip even could be wikis.

[edit on 1-8-2010 by JBA2848]


reply posted on 1-8-2010 @ 07:57 PM by misinformational
Originally posted by JBA2848
reply to
post by freedommusic



Has anybody thought that maybe tor must be installed and the required ports open on your pc. Tor is used as a ip location verifier. Tor sends out your ip to check on external database to compare to ips allowed access to the file.

Might have to spoof your own pc ip in order to appear as a authentic user. That ip could be military or government ip even could be wikis.

[edit on 1-8-2010 by JBA2848]


Previous to this thread, I knew squat about Tor.. I've been impressed with its engineering from what I've learned the past couple days - just sayin'-


reply posted on 1-8-2010 @ 07:58 PM by Smack
reply to post by Ahmose



You think we're paranoid on ATS? Try the spy world.

I think this quote from Cryptome sums it up for me.


The security watchword is: don't ever expect infallible security, that is always snail oil. The intelligence watchword is never trust an intelligence source, they are all unreliable. The classification watchword is never trust the highest classification, that is bullshovel to dupe those who believe only they have access.
The sysadmin watchword is ... lay low, log everything, copy, replace with a fake, tell no one especially another sysadmin who will rat you: l'enfer, c'est les autres.



reply posted on 1-8-2010 @ 08:00 PM by IAMNOTWHOITSAYSIAM
People read up on your cryptography before getting all excited, all it means when openssl barfs at a key you give it is that it has issues processing the padding (look up PKCS#5 padding on google) the odds of getting an error when decrypting with a wrong key is slightly above 1 in 256. Thats why there are so many keys 'that work' (if you don't belive me fetch the source code of openssl and look for your self)

Open ssl doesn't (want to) know when you enter the 'correct' key its just running the input though an algorhitm and therefore not getting an error doesn't mean your key is 'good' it just means the last byte in the file is probably a 0x00 not making the padding code unhappy.

as for bruteforcing this (problem 1 ofcourse is how do you know when you have the correct key, since we have no idea about the plaintext) distributed.net has been going at an rc5-72 key (which is a significant faster algorhitm then aes) for 2799 days (done 0.947% of the keyspace) and predicts it needs atmost 47,429 days (about 133 years) to search the complete keyspace. Now lets for the sake of argument lets assume aes and rc5 as just as fast (which they are not) for every bit above 72 (thats 184) multiply those 133 years by 2.
Giving us 133 * (2^184) = 3261150510962611490586562473775857942740676852006705430528 *YEARS*

Even if computing power 100.000 folds in the next few years the odds of bruteforcing this before the universe ends are still virtually *ZERO*

If you don't belive any of what I tell you and still convinced you guessed the correct key since you are not getting an error, do your on research, encrypt a picture of your dog or cat with openssl then try random passwords to see how many don't produce an error and how many of those actually reproduce your orginal picture of your adorable pet.

sorry to crush your hopes and dreams but a little reality check was needed in this thread.


reply posted on 1-8-2010 @ 08:01 PM by ymgve
The password is not ONION or ROUTER or any of the suggested alternatives. OpenSSL only does very basic validity checking - it only checks the padding of the decrypted data. What this means in practice is that one in every 256 wrong passwords will seem valid to OpenSSL and not produce any error message. As an example, try this:

openssl enc -d -aes256 -in insurance.aes256 -pass pass:heyabovetopsecretthepasswordisnotonion149 > insurance.out

Definitely not the correct password, but it doesn't give any error.


reply posted on 1-8-2010 @ 08:05 PM by makeitso
reply to post by JBA2848



I suppose you could have a point.
Wikileaks does have links up that you can only connect to with their version of Tor.

To upload a document anonymously using tor
When you have installed our Tor access package (see below), you may then connect to Wikileaks via our anonymous address (the ".onion" is short for "Onion Routing", but you do not need to be concerned with this detail). Then whenever you want to establish an encrypted anonymous (even to internet spies) connection to Wikileaks goto our magic link:
http: // gaddbiwdftapglkq.onion/ (this link will only work once you have installed and configured Tor.) http: // www.wikileaks.org/wiki/WikiLeaks:Tor


[edit on 8/1/10 by makeitso]


reply posted on 1-8-2010 @ 08:32 PM by mikeATSuser
Originally posted by ymgve
The password is not ONION or ROUTER or any of the suggested alternatives. OpenSSL only does very basic validity checking - it only checks the
padding of the decrypted data. What this means in practice is that one in every 256 wrong passwords will seem valid to OpenSSL and not produce any error message. As an example, try this:

openssl enc -d -aes256 -in insurance.aes256 -pass pass:heyabovetopsecretthepasswordisnotonion149 > insurance.out

Definitely not the correct password, but it doesn't give any error.


ymgve mind if I ask how you found that password? Did you attempt decrypting 149 times?


[edit on 1-8-2010 by mikeATSuser]
Pages: <<  19    20    21    22    23    24    25  >>    ^^TOP^^