Repository navigation
v0.6.0
AWS without the AWS CLI set up
A workspace can now keep its own AWS key pair. Edit the workspace, choose
Use keys stored in mssh, and either type the keys in or press
Import from shell to copy the AWS_* variables your ~/.zshrc or
~/.bashrc exports — you see what was found before anything is saved.
Workspaces that use ~/.aws, SSO or a profile keep working exactly as before.
Credentials live in the local database
SSH passwords move out of the OS keychain and into mssh's own database, so they
work the same on macOS, Windows and Linux. The database is readable by you
alone (0600), and nothing is ever sent anywhere.
Before you upgrade
- macOS may ask once for each saved password. On first launch, mssh moves
the passwords earlier versions saved in your keychain into its database. The
build is not notarised, so macOS can prompt for each one — choose Always
Allow. It is the last time mssh touches the keychain. - AWS variables from your shell are no longer picked up automatically. mssh
now takes onlyPATHfrom your login shell. If a workspace relied on
AWS_PROFILEexported in~/.zshrc, set that profile on the workspace, or
switch it to stored keys and import them.