mikefr wrote: scott wrote:
Does this mean if I keep using shell.sonic.net I won't have to make any changes to my SSH configuration? I just tried connecting to sh.sonic.net using the same SSH config except for changing the host name from shell.sonic.net to sh.sonic.net and the connection failed with the following message:
Client to Server cipher algorithm could not be negotiated
Unable to locate IP Host/Gateway
(I'm using Open Text Secure Shell).
I'll have to try that client to see why it wouldn't work with sh.sonic.net.
It might use an old cipher, in which case, please make sure your client is the latest version.
Is there any way to tell what cipher is being attempted when I get the failure? The list of ciphers that shows in my SSH Session Properties seems to consist of current ciphers (e.g., Blowfish, AES256, etc), but this may not be what's at issue. [As I said, if I take the same config (which, BTW, is just using Username/Password for authentication) it works with shell.sonic.net
but not with sh.sonic.net
]. Does this mean that even once the former points to latter host I'll still get failure?
On the assumption that I won't be able to get my Open Text SSH client to work in the new environment, I've resolved this by switching to puTTY, which does allow me to connect to sh.sonic.net
But now I have another question:
One of the things I've been using my shell access for is to retrieve the access logs for my web site. Now it appears that in the new restricted sh.sonic.net
environment, those logs are not accessible. Currently (at shell.sonic.net
) I use a perl script I wrote that peels off the access.log entries for my own userid (from /var/log/custweb
) and creates a file which I then download to my own system via SFTP, after the script has sent me email that the log extract has been created (each night, via crontab). I'd like to keep doing this, but it seems this isn't possible using sh.sonic.net
Are there any plans to make personal web site access logs accessible in the new environment?