Handling Authorized Public and Private SSH keys #1
Unanswered
justserdar
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is about SSH console access as the root user or any user using 'pubkey auth' only.
Current options/solution provided by IceWhale Team in ZimaOS

Solution 1:
mkdir /DATA/real_ssh/ cd /DATA/real_ssh/ echo "what you want" > .authorized_keys # TODO mount --bind /DATA/real_ssh/ ~/.ssh/ cat ~/.ssh/.authorized_keys # show pseudo keysNotes: The above method is not currently persistent as mentioned in Discord (image below).
Solution 2:
To get persistent configuration changes: modify the /etc/ssh/sshd_config configuration and modify the AuthorizedKeysFile, for example, change the AuthorizedKeysFile to /DATA/.ssh/authorized_keys and set PubkeyAuthentication yes.


Image:
Settings:
Interesting resources:
https://www.zimaspace.com/docs/zimaos/Setup-Python#How-to-pull-GitHub-projects-without-password
^
Due to some problems, git **cannot find ssh public key normally**.^^ Does this also affect us when trying to login as root inside Coolify to validate the server's ssh key?
Beta Was this translation helpful? Give feedback.
All reactions