|
Hi, I am not sure it is a great idea for the user experience but it could be interesting from a security stand point. |
Replies: 1 comment 1 reply
|
Proposed in PR #151, with one SSH protocol caveat documented explicitly: |
|
Hi, I am not sure it is a great idea for the user experience but it could be interesting from a security stand point. |
|
Proposed in PR #151, with one SSH protocol caveat documented explicitly: |
Proposed in PR #151, with one SSH protocol caveat documented explicitly:
SSH_MSG_USERAUTH_BANNERis delivered during authentication and Paramiko exposes it after authentication completes, so WebSSH cannot display it before credentials are used. The new flow pauses immediately afterward and before opening a jump-host forwarding channel, target shell, tmux probe, or startup command. A mandatory modal requires Continue or Cancel; decline, browser disconnect, or a 60-second timeout fails closed. The audit log records only the user, host/context, and decision—not remote-controlled banner text. Target and jump-host banners both use this flow.