Dev Accounts Adding Public Key
I'm an admin on a team account. Can dev accounts add public keys to the org?
14 Replies
https://discord.com/channels/912829806415085598/1193851455598231562/1193956399659634789
Not sure if this is what ur talking about? U want an API key for ur org?
I want folks who have dev accounts to be able to ssh into a pod. To do so they need to share their public keys w/ runpod. In attempts to do so, they mentioned they came across and error which said they didn't have permission to do so.
Ah. But you can ssh into your pod? That is weird. I would imagine ssh into a pod, people can share a public key, since that is the method to ssh. Ill let a runpod staff look at this.
Just wondering, how are you generating the ssh keys / adding it to the pods / stuff?
Prob would be helpful thing to put down
I have been able to ssh into a pod on another account. Will try on this one. I asked the team member who came across this error to send me steps to reproduce.
Maybe I forgot how exactly ssh keys work, but my impression is that we need unique public-key private key pairs for each machine no?
I think the way it works from memory is that:
server has a public key
When you try to connect to the server, it checks if you have a corresponding private key that then does some sort of encryption thingy, makes sure you are correct person.
So you can share your private key around if you want others "in a restricted fashion" to also access the pod
This is really more for a single user account, but I've been able to ssh into runpod pretty easily with:
https://discord.com/channels/912829806415085598/1185336794309468210/1192614128137814144
This is the runpod doc for a more proper way to do it:
https://docs.runpod.io/docs/use-real-ssh
RunPod
Use Real SSH
The basic terminal SSH access that RunPod exposes is not a full SSH connection and, therefore, does not support commands like SCP. If you want to have full SSH capabilities, then you will need to rent an instance that has public IP support and run a full SSH daemon in your Pod.Setup Generate your pu...
Sharing around private keys seems like a poor practice. Also, I'm not sure what you mean by "in a restricted fashion".
It was just more of half a joke lol
xD b/c sharing private keys is weird as u said haha
I guess that iddn't come through
it seems like what you can do tho is:
1) generate a private/public key pair, just add more public keys to the pod 🙂
from reading the article
and then that way everyone has their own public key / private key
at least for a single user account
there is a place to put ur ssh public keys under settings
so every pod gets it that u start up
Yup. What is currently unclear to me whether dev accounts have access to add their own public keys.
Or whether only admin accounts have that privilege
Yeah.. might be that the person gives u a public key, and u add it for them 🤔, i have no clue. how team accounts work as i dont use it
I gues ill leave that again to staff haha to answer...
But i guess also something to just try
Thanks for your help:)
Its a limitation of the "dev" role, it can't add public keys to the team, you can get an admin to add them on behalf of the devs. My clients add my SSH keys to their team accounts for me.