Issue metadata
Sign in to add a comment
|
nassh: support importing public keys that are in .pem (BEGIN RSA PRIVATE KEY) format, with no accompanying .pub
Reported by
alex.gay...@gmail.com,
May 18 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.158 Safari/537.36 Steps to reproduce the problem: 1. Have a private key in PEM "BEGIN RSA PRIVATE KEY" format 2. Press import in nassh and select it What is the expected behavior? The private key is available for use in authenticating to servers What went wrong? It is not imported. From googling around, it appears to be required to pass an id_rsa _and_ id_rsa.pub file. It would be significantly more convenient for many use cases to accept just the .pem -- notably this is what AWS LightSail provides if you let it generate a private key for you. Did this work before? N/A Chrome version: 66.0.3359.158 Channel: n/a OS Version: 10452.85.0 Flash Version:
,
May 18 2018
the files are actually imported, but the display doesn't reflect it. you could pass -i to the file on the ssh command line manually. the UX isn't great. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by davidben@chromium.org
, May 18 2018