kingToolbox / kingToolbox/WindTerm

Support encrypted storage for post-login commands (e.g., enable password) in session settings

Open
#3,579 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
32.3k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

Currently, when configuring post-login commands in session properties under Authentication (e.g., sending enable\npassword to enter privileged mode after SSH login), the password is stored in plain text in the session configuration.

This poses a security risk, especially when session profiles are shared or stored in version control.

Similar functionality exists in SecureCRT's "Logon Actions", but it also stores credentials in plain text. It would be great if WindTerm could improve this by allowing the password (or the entire post-login command sequence) to be stored in an encrypted format, possibly using the same master password mechanism that WindTerm already uses to protect saved session passwords.

Suggestion:

Allow post-login commands to reference the session's saved (encrypted) password, so users can simply use something like enable\n$(PASSWORD) without re-entering it in plain text.

Or provide an option to encrypt the entire "execute after authentication" script.

This would enhance security while maintaining convenience for users who need to automate privilege escalation after login.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in session properties under Authentication and review how post-login commands and saved session passwords are currently stored, including the existing master-password mechanism. Define whether the session password can be referenced by post-login commands or whether the entire execute-after-authentication script should be encrypted, then verify that shared or version-controlled session profiles no longer expose the secret.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
authentication, cli, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.