Always asking for password

[Sasha Zivanovic]

No matter what I do, I am always prompted to input my password.  I know my key is working I can get the input passphrase, which I have done.  But now I am getting prompted for a password for the server.  

There has to be a solution for this, I can't be the only one that has this issue?

Nextologies Limited

120 Amber Street

Markham, Ontario, Canada

Direct NOC: 416-650-6336

www.nextologies.com

---

This e-mail and any attachment is confidential and may be privileged. Any unauthorized use; disclosure, dissemination or copying of this email is strictly prohibited. If you receive it in error, please advise immediately by return e-mail and delete it. Thank you.

Ce courriel et tout annexe sont confidentiels et peut-être privilégiés. Toute utilisation, divulgation, diffusion ou copie non autorisée de ce courriel est strictement interdite. Si vous le recevez par erreur, veuillez nous en aviser immédiatement par retour de courriel et effacer le message. Merci.

[Sasha Zivanovic]

Some things to add..... Running on chrome on mac.

There is no ssh-agent as there would be, like on putty on windows.

Could that be the issue?

[Chris Shelton]

Sasha,

Are you sure that you have added your public key in the appropriate location on the ssh server that you are connecting to?  For openssh server, are the permissions on the .ssh directory set correctly (full permissions for user, no permissions for group or other, aka 700)?  While debugging this issue, I would suggest adding -v to your ssh command line arguments to see many more details related to your connection.  

It is also possible for your ssh server to not allow public key authentication to work, or require both a public key and password for a connection to work.  

Chris

[Sasha Zivanovic]

It works already with my current ssh terminal solution on mac, so I know the server is all setup.

[Mike Frysinger]

you should still follow Chris's advice and add -vvv to your ssh command line to see where things are going wrong

-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/baa2e027-8865-4a2d-a70b-d8043a8e8046n%40chromium.org.

[Sasha Zivanovic]

Yeah that's a great idea I didn't think about that the first time.  I will give that a try and see what the verbose tells me.

--

Sasha Zivanovic

CEO
416-301-3100 x351

[Sasha Zivanovic]

Ok so a little more research.  My keys have to be in exported as "open ssh" format, so now I can reliably get my key to be used.

I still get "enter passphrase", but now I don't need to have my server password anymore.

So next question is how to I not have to put my passphrase every time?

My current iterm ssh solution works just fine.  Just not in this browser solution.... Any suggestions?

[Mike Frysinger]

when you created the key, you configured it to have a passphrase.  so you'll want to remove the passphrase from it before importing into Secure Shell.

-mike

[Sasha Zivanovic]

Thats not correct.  I have the key now and passphrase in iterm working just fine.  Sorry can't take that as a valid answer.

The purpose of moving ssh to the browser is to make it easier.  Using standard SSH on terminal or bash allows me to add my key and passphrase on my system.

This means I don't need to type my password or passphrase to access another machine via SSH.

S

[William Furr]

There's no persistent ssh agent in the ssh extension.  You'll have to unlock the key every time with your passphrase.

The only way to have passwordless ssh with the ssh extension is to use keys with no passphrase.

If you want to add ssh agent support, you're welcome to write the code and send a change request or fork the extension and write your own.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAHM%3D8qq%3D21JZP1_gSXBAi1tPfcF4Au6n9edskMNSK%3DY9ec%3DD9Q%40mail.gmail.com.

[Sasha Zivanovic]

That’s what I figured. Thanks.

[Matthew Blecker]

Try the "SSH Agent for Google Chrome™" extension.

https://github.com/google/chrome-ssh-agent/blob/master/README.md

https://chrome.google.com/webstore/detail/ssh-agent-for-google-chro/eechpbnaifiimgajnomdipfaamobdfha

With that extension you only need to unlock encrypted SSH keys once per login session.

Read its short README carefully!  In particular:

1) Unlike Secure Shell extension, if you sync your extensions in Chrome Sync, this extension WILL sync any SSH keys saved in it.

2) See the step about adding --ssh-agent SSH relay server option.  Without that, Secure Shell extension (or app) won't find the find SSH Agent extension.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAHM%3D8qq%3D21JZP1_gSXBAi1tPfcF4Au6n9edskMNSK%3DY9ec%3DD9Q%40mail.gmail.com.

[Sasha Zivanovic]

Thanks that looks awesome.

[dragon788]

I'd also highly recommend looking into a Yubikey or Nitrokey or Solokey that can do GPG smartcard functionality because then you only need to enter your PIN to unlock the GPG key, which can act as your SSH private key and you don't have to copy any files to your system (meaning you can easily reset your Chromebook at any time without worrying about losing a key).

https://chromium.googlesource.com/apps/libapps/+/master/nassh/doc/hardware-keys.md