ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Security & identity · #ssh
I run long-lived SSH sessions from PuTTY through a home NAT router, and idle sessions are dropped after some period of inactivity. PuTTY's Connection panel offers two distinct mechanisms: "Seconds between keepalives", which sends SSH-level null packets, and "Enable TCP keepalives", which relies on the OS socket layer. My understanding is that the null-packet
CLion allows developers to decouple the IDE from the build environment using Remote Toolchains via SSH. This setup synchronizes source code to a remote host and executes CMake commands using the remote system's compiler and debugger. A discrepancy exists between the environment variables available in the remote shell and those recognized by the CLion CMake p
Goal: migrate a small application over SSH without noticeable downtime while the client may switch networks, causing its IP address to change. Constraint: the migration must avoid repeated authentication and keep interruption to a minimum, but OpenSSH does not natively support IP‑address mobility, so any change in client IP breaks the existing TCP session. U
Signature Algorithm Deprecation OpenSSH 8.8 and later versions have disabled the ssh-rsa signature algorithm by default. This change targets the use of SHA-1 for signatures during the authentication handshake, though the underlying RSA key pair remains valid if a more secure signature scheme is employed. Compatibility Constraints Systems maintaining legacy c
Goal Our team standardizes developer machines on TortoiseGit over Windows. Repositories authenticate to our Git server over SSH, and the setup works on every interactive desktop where Pageant holds a PuTTY-format .ppk key. The same repositories fail authentication when cloned from a Windows service account on a build machine, and we are considering changing
SSH session persistence relies on ClientAliveInterval and ClientAliveCountMax to detect dead peers at the protocol layer. These settings ensure the server terminates sessions when clients crash or lose connectivity without sending a TCP FIN packet. However, intermediate stateful firewalls often maintain their own idle timeout timers. There is uncertainty reg
putty
clion
tortoisegit