When connecting from the latest OpenSSH client (ie running Arch Linux for example) you have to use: ssh -l user host -p port -c aes256-cbcI noticed the same thing when I tried to SSH from one of my more recent Linux systems, it complained about ciphers when I tried to connect. I hadn't dug
Older clients still supports aes256-cbc as part of their base
ciphers configuration so no need to specify.
If there is a NAT device, the behavior is a little bit different.I've observed the same behavior on this side while using NAT with SSH. I was about to post a question asking about SSH when I ran across this reporting the same issue I noticed.
1, After authentication, the session sits there without displaying anything and you get disconnected after a couple of seconds.
2, After authentication, when the session sits you press any key, the
node comes up and you can use it normally.
I've observed the same behavior on this side while using NAT with SSH. I was about to post a question asking about SSH when I ran across this reporting the same issue I noticed.
On 11/07/18, eggy said the following...
I've observed the same behavior on this side while using NAT with SSH was about to post a question asking about SSH when I ran across this reporting the same issue I noticed.
To follow up on this thread some more.. after testing with a couple
random volunteers from the EFNet IRC channel, we have confirmed SSH is working through NAT when using SyncTERM. It doesn't seem to work to well with anything else. I tested with putty on windows, I haven't tried from an external Linux system.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 12:51:33 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,292 |