I was reading up on what the SSH-banner is meant for while working on bug 7372. It seems like one purpose of it is to deter unauthorized logins [1]. [1] https://linux-audit.com/the-real-purpose-of-login-banners-on-linux/ When you make a connection attempt with SSH in a terminal to a server that has a banner configured, it is shown before the password prompt -- before the user has logged in. This gives the user the option to abort the connection before a password is input. In ThinLinc, we are currently presenting users with the banner, but we do not give them the option to abort the connection if they are, in fact, deterred by the banner message. We should allow them to abort the connection if so desired.
It's worth noting that a banner can show up twice when connecting. One when connecting to the master host, and one when connecting to the agent host. Can we assume that it is enough to allow aborting the connection when connecting to a ThinLinc system (consisting of master and agents), or should users be able to accept the banner shown by the master host, but be able to abort when connecting later to an agent host?
