ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Security & identity · #ssh
On Windows, PuTTY’s documented Connection settings expose SSH application keepalives and TCP keepalive separately. The goal is to determine whether either control can enforce a maximum period without user data before PuTTY closes a session whose peer has disappeared without FIN or RST. The SSH keepalive interval is not a connection timeout: it sends global r
Observed behavior When using the Tower Git client (commercial Git GUI by fournova) on macOS, remote operations such as fetch, push, and clone intermittently trigger a fresh SSH key passphrase prompt, even though the passphrase was previously stored in the macOS keychain. The re-prompting appears to correlate with keychain sync events or macOS upgrades, but t
Password expiry versus account expiry during key-based SSH sessions On openSUSE Leap 15.x, the shadow suite stores password aging in /etc/shadow , managed through chage or YaST. Two mechanisms are easy to conflate: password expiry past the maximum age, which normally forces an immediate change at the next login via PAM, and a hard account expiry date, which
The goal is to lower the observable SSH session latency introduced by Teleport’s short‑lived certificate handshake while preserving the security benefit of frequent credential rotation. Teleport issues new TLS/SSH certificates every 60 minutes by default, and clients cache them to avoid reconnection delays. Reducing the renewal interval could increase handsh
When using GoLand's remote development over SSH, the local JetBrains client relies on a remote Go toolchain and Delve debugger running on the target host. If the underlying SSH connection drops—due to a network interruption or laptop sleep—the state of an active debug session becomes uncertain. The IDE may attempt to re-establish the tunnel, but Delve sessio
The goal is to determine whether Artix Linux should apply a default network filter that limits incoming SSH connections to trusted interfaces or subnets while the OpenRC sshd service remains enabled by default. Currently, installing the openssh package starts sshd listening on 0.0.0.0:22 and :::22, and the base ISO does not activate nftables/iptables or a de
SSH Agent Forwarding allows a client to use local private keys for authentication on a remote server, enabling subsequent jumps to other hosts without storing sensitive keys on intermediate servers. This mechanism relies on the creation of a Unix domain socket on the remote host to communicate back to the local ssh-agent. While this simplifies multi-hop work
When executing a non-idempotent command via OpenSSH, a network disconnection during the write phase can leave the remote process in an ambiguous state. Because the SSH protocol does not provide a built-in mechanism to track the completion status of a remote command after a transport-layer failure, the client cannot natively determine if the command was fully
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
putty
towergit
opensuse
artixlinux