Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, Tomas Kuchta wrote: The best way, IMHO, is to delete/move the configs, including your .ssh directory. Restart ssh and try to login somewhere. Then merge in the config changes you need, and only those you need. ssh -F /dev/null is the quicker way to ignore your

Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, wes wrote: the macs listed in ssh -Q mac are the macs the software is capable of using. the macs listed in sshd_config are the macs _enabled_ for use. macs are disabled by default when they are deemed to be below a desirable security threshold. sometimes this happens

Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, Russell Senior wrote: All Slackware why they aren't compatible and the best way to deal with it. Russell, It occurred to me that while the name might be the same the specifices might change between releases. Although, why there are more macs reported with `ssh -Q mac' on

Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, Russell Senior wrote: Both sides. The server's an earlier release and up-to-date for that one. Regards, Rich

Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, Russell Senior wrote: You should update openssh, I think. Ask someone who knows about slacker for suitable advice. Russell, I updated Slackware64-15.0 last Friday. If openssh was patched it would have been installed. I can update again and see if that makes a difference.

Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, Rich Shepard wrote: The mac issue remains: I need to specify one (and I used hmac-sha2-512), entered my password (not the passphrase) and was in. I can live with this if I must, but it was not an issue before now. Interesting. From the desktop (salmo) I can now ssh to the

Re: [PLUG] Secure shell from/to laptop [RESOLVED--Partially]

On Wed, 3 Apr 2024, Rich Shepard wrote: and the same macs are on the client. But, if I don't specify, e.g., hmac-sha2-512 I get the missing mac error. The perms on both the server and client .ssh/* match and those in . Had not before