(The following text is generated by AI (base on my opinion) because my English skill is not good lol, btw I'm not a real Engineer, but a student studying Network Engineering)
Description:
Hi developer,
First of all, thank you for creating WindTerm – it's a fantastic tool! I'm a network engineer and use WindTerm daily to manage network devices (switches, routers, etc.) via both SSH and Serial (Console) connections.
I have a feature suggestion that I believe would significantly improve the workflow for network administrators and embedded engineers.
The Problem
I frequently need to connect to the same network device using both SSH (for remote access) and Serial (for out-of-band management or initial configuration). These two connection methods use the same username and password credentials. However, currently, OneKey credentials are tied to a specific session protocol. This means I have to create and manage two separate OneKey entries for the same set of credentials – one for SSH and one for Serial.
This duplication defeats the purpose of a centralized password manager and adds unnecessary friction, especially when credentials are rotated regularly.
The Request
I would like to request a feature that allows a single OneKey credential entry to be associated with multiple session types (SSH, Telnet, Serial, etc.), not just the session it was originally created for.
In other words, when creating or editing a OneKey entry, there could be an option to select which protocols this credential is valid for, or simply allow any session to reference any OneKey entry regardless of its protocol.
Use Case / Workflow
- I create a OneKey entry named "CoreSwitch-Admin" with username
admin and password ******.
- I create an SSH session to connect to
10.0.0.1. I select the OneKey entry "CoreSwitch-Admin" for authentication.
- I create a Serial session to connect to the console port of the same device (e.g., COM3, 115200). I want to select the same OneKey entry "CoreSwitch-Admin" for authentication.
Currently, step 3 is not possible – the Serial session's OneKey dropdown only shows credentials that were originally created for a Serial session (if I recall correctly). I would like to be able to reuse the same credential across both.
Benefit
This would make OneKey a truly "universal" credential manager, reducing redundancy and making credential rotation much simpler – update the password once in OneKey, and all sessions (SSH and Serial) using that credential are updated automatically.
Alternative Considered
I am aware that I could use a standalone password manager (e.g., Bitwarden) and copy-paste credentials manually, but this breaks the "one-click login" experience that makes WindTerm's OneKey so convenient.
Thank you for considering this request! I'm happy to provide more details if needed.
(The following text is generated by AI (base on my opinion) because my English skill is not good lol, btw I'm not a real Engineer, but a student studying Network Engineering)
Description:
Hi developer,
First of all, thank you for creating WindTerm – it's a fantastic tool! I'm a network engineer and use WindTerm daily to manage network devices (switches, routers, etc.) via both SSH and Serial (Console) connections.
I have a feature suggestion that I believe would significantly improve the workflow for network administrators and embedded engineers.
The Problem
I frequently need to connect to the same network device using both SSH (for remote access) and Serial (for out-of-band management or initial configuration). These two connection methods use the same username and password credentials. However, currently, OneKey credentials are tied to a specific session protocol. This means I have to create and manage two separate OneKey entries for the same set of credentials – one for SSH and one for Serial.
This duplication defeats the purpose of a centralized password manager and adds unnecessary friction, especially when credentials are rotated regularly.
The Request
I would like to request a feature that allows a single OneKey credential entry to be associated with multiple session types (SSH, Telnet, Serial, etc.), not just the session it was originally created for.
In other words, when creating or editing a OneKey entry, there could be an option to select which protocols this credential is valid for, or simply allow any session to reference any OneKey entry regardless of its protocol.
Use Case / Workflow
adminand password******.10.0.0.1. I select the OneKey entry "CoreSwitch-Admin" for authentication.Currently, step 3 is not possible – the Serial session's OneKey dropdown only shows credentials that were originally created for a Serial session (if I recall correctly). I would like to be able to reuse the same credential across both.
Benefit
This would make OneKey a truly "universal" credential manager, reducing redundancy and making credential rotation much simpler – update the password once in OneKey, and all sessions (SSH and Serial) using that credential are updated automatically.
Alternative Considered
I am aware that I could use a standalone password manager (e.g., Bitwarden) and copy-paste credentials manually, but this breaks the "one-click login" experience that makes WindTerm's OneKey so convenient.
Thank you for considering this request! I'm happy to provide more details if needed.