Skip to content
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.

Sign up for GitHub

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

Update SSH text #9

Merged
merged 1 commit into from
Feb 15, 2024
Merged

Update SSH text #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/utilities/ssh/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ tags:

I had a hard time understanding what to do with my private/public keys when I was learning SSH. I don't know why it was a difficult concept for me, but I have worked with enough other people who were confused in the same way I was that I think it's worth it to just spell out what to do with each key.

Your private key (default name is `id_rsa`) should **NEVER** leave the server it was created on, and should not be accessible to any other user (`chmod 600`).
Your private key (default name is `id_rsa`) should **NEVER** leave the server it was created on, and should not be accessible to any other user (`chmod 600`). There are exceptions to this, such as when uploading a keypair to an Azure or Hashicorp vault, or providing to a Docker container. But in general, when creating SSH tunnels between machines, the private key is meant to stay on the machine it was created on.

Your public key is like your swipe card; when using the `ssh` command with `-f /path/to/id_rsa.pub` and the correct `user@server` combo, you will not need to enter a password to authenticate.

Expand Down
Loading