-
-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working in Chrome's Secure Shell plugin #58
Comments
Interestingly it prompts for a passphrase, something it doesn't do when I connect via a real terminal. Not sure what this means, though. |
aquilax claims it's working now, yay! http://i.imgur.com/II14xR5.png |
Do you know how he configured it? I tried when the issue was first posted but never figured it out. |
@empathetic-alligator Just restarted with the new version an hour ago, so give it a try again. @aquilax Any tips? |
When creating connection make sure you click [Identity] Import... , and pick your private key. |
Whoa I was gonna comment here only to find it's closed. Yes it seems to be due to PublicKey authentication. When no key is imported, Chrome Secure Shell plugins doesn't initiate PublicKey authentication, while Issue #30 , when fixed, should address this issue as well. |
No idea why. Ideas? Symptoms?
The text was updated successfully, but these errors were encountered: