Hi Robin, That solution doesn't work because when using sshkeys there is no option to fill in the password. You simply get the error message permission denied (public key).
In second instance you get a window to fill in a username/password but this only applies to password auyjentication. I have tighten the security on the server (changed the ssh port and only allowing ssh keys to authenticate). so password authenication doesn't work Best regards, Jasper van der Marel 2009/12/12 Robin Gloster <[email protected]>: > Hi, > > In the password field, ypu have to type in the ssh-key password and not the > user password. > Then all should work. > > Best regards, > > Robin > > 2009/12/12 jasper van der marel <[email protected]> >> >> Hi, >> >> To secure an x2go terminalserver enviroment from the bad big world >> outside we are thinking of implementing ssh-key based authenication. >> This works wonderfully with unencrypted ssh-keys. With encrypted >> ssh-keys it won't work because of the password challenge. Is there any >> way it can work with the x2goclient ? Then we can change the passwords >> set on the ssh-keys at an interval instead of reissuing ssh-keys. Any >> other ideas about implementing otp passwords with x2go are very >> welcome ;) >> >> In case you are wondering or interested about the client we are >> planning to implement x2go as a terminalserver solution: >> >> >> http://www.osor.eu/news/more-health-care-organisations-adopting-open-source >> -> part about Antonius Hospital in the Netherlands >> >> With kind regards, >> >> Jasper van der Marel >> Stone-IT >> >> http://www.stone-it.com >> _______________________________________________ >> X2go-dev mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/x2go-dev > > _______________________________________________ X2go-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
