Skip to content
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

Closed
shazow opened this issue Dec 15, 2014 · 6 comments
Closed

Not working in Chrome's Secure Shell plugin #58

shazow opened this issue Dec 15, 2014 · 6 comments

Comments

@shazow
Copy link
Owner

shazow commented Dec 15, 2014

No idea why. Ideas? Symptoms?

@wpovell
Copy link
Contributor

wpovell commented Dec 15, 2014

Interestingly it prompts for a passphrase, something it doesn't do when I connect via a real terminal. Not sure what this means, though.

@shazow
Copy link
Owner Author

shazow commented Dec 15, 2014

aquilax claims it's working now, yay! http://i.imgur.com/II14xR5.png

@shazow shazow closed this as completed Dec 15, 2014
@wpovell
Copy link
Contributor

wpovell commented Dec 15, 2014

Do you know how he configured it? I tried when the issue was first posted but never figured it out.

@shazow
Copy link
Owner Author

shazow commented Dec 15, 2014

@empathetic-alligator Just restarted with the new version an hour ago, so give it a try again.

@aquilax Any tips?

@aquilax
Copy link
Contributor

aquilax commented Dec 15, 2014

When creating connection make sure you click [Identity] Import... , and pick your private key.

@songgao
Copy link
Contributor

songgao commented Dec 15, 2014

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 ssh-chat expects only PublicKey authentication (https://github.com/shazow/ssh-chat/blob/master/server.go#L66). The PublicKeyCallback wouldn't be called if no PublicKey is available in Chrome Secure Shell.

Issue #30 , when fixed, should address this issue as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants