AES128 has been BTFO! NSA can literally decrypt most of your

I use Tor to access clearweb and I use 4096-bit RSA encryption to encrypt all my traffic, nice try NSA.

>>61153699
Did you even try to read the (two year old) blog post you linked to, OP? No? Because you clearly didn't understand it

OP is eternally a faggot

>>61153817
>I use Tor to access clearweb
You can't post on the 4chins with tor.

>and I use 4096-bit RSA encryption to encrypt all my traffic
I see a contradiction here: Tor uses ed25519/dh1024/rsa1024
Also, nobody uses RSA for anything else than signing the DH key (and nobody uses DH for anything other than key exchange) which means that you probably use a symmetric encryption algo in order to encrypt the actual data (which is probably AES128).

>>61153868
Yes, I did. It clearly says that if you have enough ciphertexts a state actor can easily recover some of their 128bit keys.
Is there any part where you disagree?

>>61153699
Remember to set AES256 as the default algorithm in your GPG. Either with the --cipher-algo AES256 argument when encrypting or with personal-cipher-preferences AES256 in your gpg.conf. Also with setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed in the gpg console after you have selected the key you want to attach the preferences to.

>>61153699
>AES128 is compromised

It's okay, I use threefish.

>>61155493
What keysizes do you use?
The sad part is that it's not supported for almost anything, including TLS traffic. Also all the attention from it went away after the sha-3 competition, why not Chacha20 or Keccak/Keyak/NORX instead?

>>61153699
FYI, quantum computing makes AES256 equivalent to AES128, so very likely the NSA can break AES256 if they really had to.

>>61156780
>quantum computing makes AES256 equivalent to AES128
Not exactly, you can't really combine grover's algorithm with this.
Also, grover's algorithm reduces the difficulty of AES128 to 64 bits.

>>61154572
Wish it would support chacha20

>>61153699
>128 bit key
>2011+6
Hahaha.

That ram chest :(

What is the alternative

File: big boss 1.jpg (239KB, 500x713px) Image search: [Google]

239KB, 500x713px

>>61153699
Well, I sure do hope they have jurisdiction here.

>>61153699

you have to use AES512

actually, fuck it, I'm using AES2048

AES128 is still secure. Once it isn't you'll know, it will be major news.

>>61153699
What do you have to hide, OP. You should have nothing to fear if you're not a criminal or terrorist. The state is protecting you by busting terrorists before they have a chance to kill lots of people or a druggie sells more meth on the streets.

>not using AES2952790016 bit encryption
>not taking 4 years for every packet to become an indecipherable mess
>not crashing systems every time you send a HTTP/GET request
>not having to replace a hard drive every time you open your encrypted text file because it's been layered with so much encryption that your drive head looks like a fucking phonograph going Mach 7 like those astronaut training machines trying to read all the numbers
>in 2017

>>61160166
>I am using things that do not exist

>>61160184
See >>61153699

>>61161636
>>not having to replace a hard drive every time you open your encrypted text file because it's been layered with so much encryption that your drive head looks like a fucking phonograph going Mach 7 like those astronaut training machines trying to read all the numbers
The encryption does not happen by the hard drive, duh.