Private Key for Team Members #3035
-
Yesterday I added a member to my team on a free account. I added an AWS EC2 Server and managed to connect by creating the public and private keys. However, my team member could only see the public key and when clicking on connect in Shellhub the only connection option was by private key. Eventually I had to send him the server's private key. Question: Since Shellhub is currently only allowing connection via private key, couldn't I just add the key to my account and allow other users to use it? Or better yet, couldn't I enable login using my public key? since it appears on the dashboard of all my team members? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
A more secure approach would be to continue allowing access via public keys only. This means each team member generates their own key pair, shares their public key, and keeps their private key safe. This way, we maintain a higher level of security by not storing or sharing private keys.
Private keys, as the name suggests, are meant to be kept confidential. That's why we don't store private keys on the ShellHub server. When you upload a private key to ShellHub, it's actually saved in your browser's local storage. This ensures that the key remains exclusively accessible to you and can only be used within the ShellHub environment. |
Beta Was this translation helpful? Give feedback.
-
Could no one explain? |
Beta Was this translation helpful? Give feedback.
@projetosfsi A authenticação funciona com 2 partes: publica e privada. Para conectar em um dispositivo configurado com uma chave pública você deve fornecer a privada. Pra isso, entre na parte de Settings da UI do ShellHub e vá até a aba de chaves privadas e faça o envio.