Server-side session limit per client identity

[nicolascbl]

Feature Request

When a client binary is deployed with a persistence mechanism (cron, schtasks..),
each execution creates a new session on the server even if a session for the same host is
already active. This results in session proliferation that operators must clean up manually.

Proposed Solution

Add a server-side option to limit the number of concurrent sessions per client identity
(user.hostname) or per public key:

• --max-sessions-per-identity N in server config
• as a link flag: link --max-sessions 1

When the limit is reached, either:

• Reject the new connection (client retries later)
• Or drop the oldest session in favor of the new one

I actually have a external script polling ls and calling kill -y

[NHAS]

Howdy, this is a good idea, going to add it via link --single-session mainly because I dont see a need to define how many sessions an rssh binary can spawn >1

[NHAS]

This'll also be based on public key rather than on hostname.

[NHAS]

This is now on unstable. Feel free to test it via either using link --single-session to generate a new binary, or for your existing connections find their entry in the authorized_controllee_keys file and add single_session as an option.

E.g

cat authorized_controllee_keys 
owner="",single_session ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAINu8PudE5Cd+wkMqOzdtvXPj04/9fxA+TgASEjHpLQ/h