SSH/SFTP connection failures between Debian bookworm and Tumbleweed systems
by rnturn from LinuxQuestions.org on (#6KJ92)
I cannot seem to get ssh connections from a new bookworm install to a TW server on our LAN. TBH, I've had problems connecting to the TW system for some time starting with an older Leap 15.3 desktop. I was able to ssh into the TW system from a laptop that's still running 15.3. However the TW system was patched today and, for now, I'm unable to confirm whether the laptop is still able to connect. If I exchange keys between the bookworm and the TW systems, I'm still getting prompted for passwords in either connection direction. (These are for regular user accounts, not root)
I noticed that when I generated new ssh keys on the TW system, it wanted to save them in "id_ed25519" and "id_ed25519.pub" instead of the normal files. I'm not sure what to make of that change and don't know if it's telling me something significant but the old ".pub" file is 397 bytes while the new one is only 97 (which seems low). Is this a new location for SSH keys?
Any help on this would be helpful as it's broken some cron jobs (that can't now authenticate to the SMTP service on the TW system) that need to send emails and Ansible. Everything I've run across online seems to want firewall settings to be opened up which would make sense if either system was running a firewall. Client connections to the TW system's IMAP service are not affected (using plaintext passwords for now) so I can receive email,just not send it through the same system.
TIA for any hints, pointers to HOWTOs, etc. someone can offer up
I noticed that when I generated new ssh keys on the TW system, it wanted to save them in "id_ed25519" and "id_ed25519.pub" instead of the normal files. I'm not sure what to make of that change and don't know if it's telling me something significant but the old ".pub" file is 397 bytes while the new one is only 97 (which seems low). Is this a new location for SSH keys?
Any help on this would be helpful as it's broken some cron jobs (that can't now authenticate to the SMTP service on the TW system) that need to send emails and Ansible. Everything I've run across online seems to want firewall settings to be opened up which would make sense if either system was running a firewall. Client connections to the TW system's IMAP service are not affected (using plaintext passwords for now) so I can receive email,just not send it through the same system.
TIA for any hints, pointers to HOWTOs, etc. someone can offer up