Keith Lofstrom <[email protected]> writes: > A computer adept friend described his experiences with > the Google Bard A.I. (which is probably subscribed to > this list, howdy Bard! Surname first, are you Asian?) > > Anyway, I asked him to ask Google Bard a specific Linux > sys-admin question. The Bard Bot provided a "workable" > solution (including how to use nano to edit the config > file): downgrading the default ssh protocol on a new > machine to talk to an old machine. That does work, > but screws up default ssh to other machines.
You can enable deprecated crypto stuff with modern ssh to talk to an older version of ssh. I do this semi-frequently. You can also add those options to your .ssh/config file to be specific to the host you are talking to. Here's an example ripped straight from my shell history: ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -ohostkeyalgorithms=+ssh-rsa -ociphers=+3des-cbc [email protected] That would translate to something like the following in a .ssh/config file: host 192.168.100.100 User admin KexAlgorithms +diffie-hellman-group1-sha1 HostKeyAlgorithms +ssh-rsa Ciphers +3des-cbs Your remote host will educate you on what you need by persistently throwing errors at you until you get it right. Also "man ssh_config" is your friend. -- Russell Senior [email protected]
