|
the Wikileaks/ Cablegate scandal (pg. 9)
|
View this Thread in Original format
| jon jon |
| "assange arrested" in now trending on twitter, yet "wikileaks" hasn't trended all week... SKETCH!!!!!! |
|
|
| jester |
| quote: | Originally posted by Abercrombie
Israel is behind eveything in the middle east, doncha know? They were even blamed for releasing the sharks that attacked tourists in Egypt. :haha: :haha: :haha: |
Killer Israeli-breed sharks going after Germans in Egypt lol Aint that something. |
|
|
| exraver |
| quote: | Originally posted by jester
Killer Israeli-bread sharks |
WTF? |
|
|
| infinity HiGH |
| quote: | Originally posted by jon jon
"assange arrested" in now trending on twitter, yet "wikileaks" hasn't trended all week... SKETCH!!!!!! |
You watch Jon Stewart? Notice how he only had something to say about the wikileaks thing on the first day it was released. Then the following episodes it's as if it never happened. They're clearly covering this up. Pretty soon Del will mysteriously censor the word wikileaks and anybody mentioning it will be banned/never heard from again. |
|
|
| jester |
| quote: | Originally posted by exraver
WTF? |
Meant breed. Try typing on an old iMac... its bloody slow. Having Safari open for 10 mins... some how eats half the memory :whip:
Its funny how I can type faster than my computer buffer can handle at times (due to what I posted above) :p |
|
|
| mahalliner |
| quote: | Originally posted by Sly_Guy
funny thing is, I'm studying the AES algorithm for an exam tomorrow. Sufficed to say, it'd take my computer around 3 million years to break his encryption. |
I don't know much about cryptography but don't most of the effective attacks against AES have to do with attacking how it was implemented rather than the algorithm itself?
Also, Anon. has shifted their DDOS attack to the Swedish prosecutors office. http://twitter.com/search?q=%23ddos |
|
|
| Sly_Guy |
| quote: | Originally posted by mahalliner
I don't know much about cryptography but don't most of the effective attacks against AES have to do with attacking how it was implemented rather than the algorithm itself?
Also, Anon. has shifted their DDOS attack to the Swedish prosecutors office. http://twitter.com/search?q=%23ddos |
actually that's the craziest thing about modern encryption, is that even with the full release of the algorithms associated with the encryption, analysis of the ciphertext alone will still not yield solutions to the plaintext.
AES is basically an upgrade of the DES encryption system. DES has been protecting your bank accounts for the last 30 years. AES is also the current standard for protecting government and military information.
AES works in the following manner: in the beginning, you've got your plaintext and your key. You enter the plaintext and key into AES. AES will use a round key generator to create a set of apparently randomized but privately known keys to the system [the algorithm itself will generate the same round keys each time it's run with that specific key, although they will look random to a user of the system]. Those round keys will be used to XOR the output from a series s-box lookups [essentially just replacing one letter or number with another by looking up in a table], then mixing rows of the data in matrix form, then mixing the columns. This process of s-box->rows->columns->XOR with round key, proceeds to happen for as many rounds as you have keys, and the result is your ciphertext.
Ideally you are correct, if an attack of the system is based on the encryption method itself then it will succeed every time, but none are known at this time, and likely won't be known. This means hackers are essentially limited to brute force attacks, and I'm sure this guy has chosen a randomly generated key, so even an offline dictionary attack will prove no more effective.
Based on what my textbook says, to break a 256-bit key AES system, a machine operating at one decryption attempt every microsecond would need 10^6 years to try all the keys. Cut that in half for the statistical average time to guess the right one, and cut it again by a factor of how much faster your processor can compute a decryption try and you're still never gonna figure it out.
Haha, this is actually good and useful review for me, who knew? |
|
|
| VDub |
| quote: | Originally posted by jester
Meant breed. Try typing on an old iMac... its bloody slow. Having Safari open for 10 mins... some how eats half the memory :whip:
Its funny how I can type faster than my computer buffer can handle at times (due to what I posted above) :p |
You gonna blame the computer for the extra e as well???
Bred is past tense...
Lol |
|
|
| exraver |
Whoever has linux and downloaded file, try this:
#AES PASSWORD == ONION
$ openssl enc -d -aes256 -in insurance.aes256 > out_ONION_AES.dec
#BF PASSWORD == ROUTER
$ openssl enc -d -bf -in insurance.aes256 > out_ROUTER_BF.dec
#BF PASSWORD == ONION
$ openssl enc -d -bf -in insurance.aes256 > out_ONION_BF.dec
A common infosec subterfuge is to use every notable occasion to claim a system is invulnerable in order to promote continued use of the system. NSA has run a number of these disinformation campaigns about "unbreakable" encryption, secret (German, Japanese, Soviet, et al) and public -- the most famous public system involved Crypto AG, within whose cryptosystem NSA installed a backdoor to gain access to communications of worldwide users who believed the system was invulnerable.
Doubts about the invulnerability of AES have persisted since NSA selected an algorithm from an AES competition that was considered by cryptographers not to be the strongest. And that it is likely for strongest protection NSA uses a top secret cryptosystem while promoting AES for public and official use. It is argued that NSA, like all official comsec agencies, would never endorse a system it could not secretly access. And these agencies never reveal that capability -- NSA's backdoor access to Crypto AG was revealed by an employee of the company.
Bet that NSA has cracked the insurance file and is keeping quiet. NSA may have replaced the file with its own when it first appeared -- Wikileaks long on instant crypto radar -- the hash forged, covertly marked for tracking. Bluff becomes bait for entrapment, SOP.
Could Wikileaks have intended to entrap NSA and allies with a crackable file, covertly marked for tracking? Some of Wikileaks infosec-comsec advisors do top-classified work for the US and other governments. A very handsome sum would be quietly paid for that service. Cyberwarfare secrets are yet to be spilled, never to be revealed in courts. Fierce dirty combat could do that, unless the combatants reach a secret deal to share the benefits of dual use technology while pretending to be at odds, SOP. |
|
|
| Sly_Guy |
| quote: | Originally posted by exraver
Whoever has linux and downloaded file, try this:
#AES PASSWORD == ONION
$ openssl enc -d -aes256 -in insurance.aes256 > out_ONION_AES.dec
#BF PASSWORD == ROUTER
$ openssl enc -d -bf -in insurance.aes256 > out_ROUTER_BF.dec
#BF PASSWORD == ONION
$ openssl enc -d -bf -in insurance.aes256 > out_ONION_BF.dec
A common infosec subterfuge is to use every notable occasion to claim a system is invulnerable in order to promote continued use of the system. NSA has run a number of these disinformation campaigns about "unbreakable" encryption, secret (German, Japanese, Soviet, et al) and public -- the most famous public system involved Crypto AG, within whose cryptosystem NSA installed a backdoor to gain access to communications of worldwide users who believed the system was invulnerable.
Doubts about the invulnerability of AES have persisted since NSA selected an algorithm from an AES competition that was considered by cryptographers not to be the strongest. And that it is likely for strongest protection NSA uses a top secret cryptosystem while promoting AES for public and official use. It is argued that NSA, like all official comsec agencies, would never endorse a system it could not secretly access. And these agencies never reveal that capability -- NSA's backdoor access to Crypto AG was revealed by an employee of the company.
Bet that NSA has cracked the insurance file and is keeping quiet. NSA may have replaced the file with its own when it first appeared -- Wikileaks long on instant crypto radar -- the hash forged, covertly marked for tracking. Bluff becomes bait for entrapment, SOP.
Could Wikileaks have intended to entrap NSA and allies with a crackable file, covertly marked for tracking? Some of Wikileaks infosec-comsec advisors do top-classified work for the US and other governments. A very handsome sum would be quietly paid for that service. Cyberwarfare secrets are yet to be spilled, never to be revealed in courts. Fierce dirty combat could do that, unless the combatants reach a secret deal to share the benefits of dual use technology while pretending to be at odds, SOP. |
you gotta tell me then, if the keys and s-boxes in a AES algorithm are essentially up to the implementor, how can a there possibly be a backdoor? There are just way too many variables at play. It's simple enough to build the algorithm from scratch using nothing more than fips diagrams, so it's not like you'd even have to use someone else's software.
To me, the algorithm looks good, and I have a hard time believing that someone using a next-gen encryption method, with a key space double that of the standard would be broken so easily.
But if you know something I don't, I'm all ears, cuz hell, this is tomorrow's exam for me. |
|
|
| Magnetonium |
| quote: | Originally posted by jon jon
"assange arrested" in now trending on twitter, yet "wikileaks" hasn't trended all week... SKETCH!!!!!! |
Thats ed. What the world establishment is doing to Wikileaks is much worse than what Wikileaks have done. This is a vendetta. Even the UK judge has refused bail for Assange - like where is he gonna run and hide??? Its ridiculous.
If this is gonna get uglier then me and my buddies are gonna make a serious financial donation to Wikileaks (wire transfer), because I sure as hell do not want government to silence this rare and important historic opportunity. Maybe Assange did go a bit too far and some documents should have not been released, BUT: All signs are pointing to a huge cover-up and silencing of the case, which is really pissing me off. ARE WE ING LIVING IN A SOVIET RUSSIA ALL OF A SUDDEN???
:whip: :whip: :whip:
Nice to see Wikileaks publish a new wire on secret NATO plans to build a huge defense system in Poland and Baltic countries, including military bases. You see, I was right from the beginning - they want to build a defense wall (including missile strike/defense systems) around Russia, and NOT protect Europe against Iranian threat. Iran is not interested in attacking Europe ... What a waste of money, they want to start another arms race / Cold War. How is that gonna make better friendly relations with Russia?
|
|
|
|
|
