10/18/2020 Mac Os X Public Key Generation
You generate an SSH key through macOS by using the Terminal application. Once you upload a valid public SSH key, the Triton Compute Service uses SmartLogin to copy the public key to any new SmartMachine you provision.
Joyent recommends RSA keys because the node-manta CLI programs work with RSA keys both locally and with the ssh agent. DSA keys will work only if the private key is on the same system as the CLI, and not password-protected.
FIGURE 2.4: SSH key generation in MAC OS terminal Get Microservices with Docker on Microsoft Azure™ (includes Content Update Program) now with O’Reilly online learning. O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers. If you forget the passphrase to a key, any Email or file encrypted to the key will remain encrypted and appear as cipher text. The Passphrase Quality bar provides a basic guideline for the strength of the passphrase you are creating. To save this passphrase in the Mac OS X Keychain, select the box Save passphrase in Keychain. Click Continue. The PGP Key creation summary screen is displayed.
About TerminalMac Os X Information
Terminal is the terminal emulator which provides a text-based command line interface to the Unix shell of macOS.
To open the macOS Terminal, follow these steps:
The Terminal window opens with the commandline prompt displaying the name of your machine and your username.
Generating an SSH key
An SSH key consists of a pair of files. One is the private key, which should never be shared with anyone. The other is the public key. The other file is a public key which allows you to log into the containers and VMs you provision. When you generate the keys, you will use
ssh-keygen to store the keys in a safe location so you can bypass the login prompt when connecting to your instances.
To generate SSH keys in macOS, follow these steps:
Mac Os X Public Key Generation Download
You will need to enter the passphrase a second time to continue.
![]()
After you confirm the passphrase, the system generates the key pair.
Your private key is saved to the
id_rsa file in the .ssh directory and is used to verify the public key you use belongs to the same Triton Compute Service account.
Your public key is saved to the
id_rsa.pub ;file and is the key you upload to your Triton Compute Service account. You can save this key to the clipboard by running this:
Importing your SSH key
Now you must import the copied SSH key to the portal.
Troubleshooting
You may see a password prompt like this:
This is because:
What are my next steps?
Right in the portal, you can easily create Docker containers, infrastructure containers, and hardware virtual machines.
In order to use the Terminal to create instances, set up
triton and CloudAPI as well as the triton-docker commandline tool.
This guide goes through setting up SSH keys on macOS Mojave 10.14 back to Mac OSX 10.11 and also a secure password-less SSH connection between a local macOS workstation and a remote server also running a Linux variant operating system.
The process requires generating a public and private key on the local computer and then adding the public key to the remote servers authorised list. What is great about this is that it allows a password prompt free session, handy for a lot of uses.
First thing that you need to do on your macOS machine is to create a directory that will store your SSH keys. Then you will generate a public and private key for your account, launch the Terminal and punch in some commands:
Create a .ssh Directory
Change to the home directory
Create a SSH directory name .ssh and move into it
Make sure that the file permissions are set to read/write/execute only for the user
Create your private and public key, the blank quotes at the end of the command gives the private key no password, so allowing for passwordless logins!
Change into the .ssh directory and list the contents of that .ssh directory
Thats your SSH keys created, the private key is the id_rsa and the public one is the id_rsa.pub, don’t give out the private one always keep that one only on your local machine.
Sharing the Public Key
Create an authorized_keys in the .ssh directory of the remote computer that you want to connect to.
You can create automatic logins by adding the contents of your public key to the authorized_keys file on the remote device.
To see and copy your public key use the cat command and copy the contents:
On the remote computer if needed, change the permssions on the authorized_keys file to write to add the public key, on a new line paste in your public key, and change permissions back to read only after for security.
Allow write on authorised_keys
Paste the entire id_rsa.pub content with vi or nano into the authorized_keys file, if using nano use the -w flag to not use incorrect line breaks.
If the remote host does not have an “authorized_keys” file simply create one and after the public key is pasted in don’t forget to takeaway write permissions.
Going Both Ways
So now when you connect via SSH no password is prompted as the remote computer has your public key which is only decrypted by your private key held in your local .ssh/ directory. If you want the communications to be bilateral then repeat the process in the opposite order between the two.
Now the two computers can securely connect with no password prompting, making it ideal to script between the two for file copies or back ups.
Doing it Quicker
Now instead of typing in
Make an alias in your bash shell you could alias it to
Reload the the shell
Then all you have to type in is the alias
RelatedComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |