XPost: alt.privacy.anon-server, alt.computer.security, comp.security.firewalls XPost: alt.security

In article <66da992f2f6696d2c18e07e66dba19f6@dizum.com>
Nomen Nescio <nobody@dizum.com> wrote:

Most are probably using RSA. Since the NSA and other intels were in on the RSA diluting so that it could be more easily broken, it would seem wise that all remailers switch to Curve25519 (ECC) keys to access their servers. This is not difficult to

do.

Use PUTTYGEN.EXE that comes in the Putty folder.
1. Check the EC25519 button at the bottom.
2. Click Generate.
3. Save public key. Save private key.
4. Point to the new private key in Putty.exe under Connection/SSH/Auth/Private key file for identification:
5. Add the newly generated public key into the /root/.ssh/authorized_keys file on the server.
5. Login

Already done here. I would suggest that you backup the server first and then duplicate your Putty AES login session and then modify the new session with the new key. Then you can fall back on your AES login if the 25519 doesn't work for some reason.

After the 25519 login is working, you need to delete the AES pub key from the authorized_keys file or an AES attack can still be performed.

attack my aes-256 all you want. you and i will both be dead for
a century before anyone ever sees any results - even with
quantum computing.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)