-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add ssh key of gislab user to gislab client #487
Comments
Confirmed, currently I am bypassing it by special user after-add hook. |
I don't understand this issue. Can you explain this issue in detail ? |
You cannot connect from the server to the running client:
says 'Error: Permission denied (publickey)'. |
It is true, only SSH keys authentication is allowed. Do you propose creating some password-less SSH keys on user account creation ? |
Yes, the
|
'gislab' user account doesn't contain private or public SSH key. But it contains public key used for provisioning user (ubuntu or vagrant). So adding this key to ssh-agent ($ ssh-add ) and logging with agent forwarding enabled ($ ssh -A) should allow logging to server and jumping to clients as well. |
Run "$ vagrant ssh-config" to get SSH connection information used by Vagrant which contains also path to SSH key used by Vagrant |
I don't understand, there is no vagrant used/installed on GIS.lab unit, right? |
@landam, I meant that every user account used for GIS.lab installation ('vagrant' if using Vagrant, 'ubuntu' for other installations) contains public SSH key. For GIS.lab Unit, it is the one which is specified during basic OS ISO image creation. This key is copied during installation also to 'gislab' user account (see: /storage/home/gislab/.ssh/authorized_keys). Therefore, you can use this SSH key for connection. See ssh-agent for more information how to forward SSH keys. |
OK, but I still think that gislab user should be able to connect from the server to the clients out of box (without any extra effort).
|
Currently it is not possible to log in to the gislab client from the server by ssh.
The text was updated successfully, but these errors were encountered: