-
Notifications
You must be signed in to change notification settings - Fork 59
Key based ssh Authentication
rpwoodbu edited this page Sep 23, 2014
·
3 revisions
You may use a private ssh key to authenticate when connecting over ssh. It may be encrypted with a passphrase if desired. Click on "Add ssh key" on the right side of the session setup window, paste your key into the box, and click "Save".
A few notes:
- The key should be in PEM format. This is typically what you would find in your
~/.ssh/id_rsa
file, so you can just copy/paste the whole contents of that file. - Mosh for Chrome will not display your saved key when you return to the "Add ssh key" window. As the key is sensitive information, there is no way through the UI to retrieve your saved key.
- For similar security reasons, your key is not synchronized across browsers. If you use multiple browsers (or browser profiles), you must add your key separately in each one. If there is demand for key synchronization, I will consider adding it as an option.
- Unless your key is protected with a passphrase, it is not encrypted, and can be read by anyone who gains access to your computer. It is recommended to use encrypted local storage for maximum security. If you are using Chrome OS, congratulations, you already enjoy per-user encrypted local storage. But even then, if someone gains authenticated access your account on your Chromebook, they can use the Javascript Console to retrieve your key. You have been warned.
- To remove the key, either uninstall Mosh for Chrome, or "add" a blank key. Currently, only one key can be stored at a time, so storing a blank key overwrites any existing key.