Skip to content
Discussion options

You must be logged in to vote

Proposed in PR #151, with one SSH protocol caveat documented explicitly: SSH_MSG_USERAUTH_BANNER is 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.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@ap0int3d
Comment options

Answer selected by bifrost0x
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Ideas
Labels
roadmap Approved for the WebSSH roadmap
2 participants