Update directories with PATCH

Create public and private SSH keys

First thing that you need to do on your OSX 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

cd ~/

Create a SSH directory name .ssh and move into it

mkdir .ssh ; cd .ssh

Make sure that the file permissions are set to read/write/execute only for the user

chmod go-rwx .ssh

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!

ssh-keygen -b 1024 -t rsa -f id_rsa -P ""
￼

keygen-generate-ssh-keys
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.
touch authorized_keys
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

chmod u+w authorized_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.

chmod u-w authorized_keys

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

ssh This email address is being protected from spambots. You need JavaScript enabled to view it.

Make an alias in your bash shell you could alias it to

alias now='ssh This email address is being protected from spambots. You need JavaScript enabled to view it.'

Run diskutil unmountDisk /dev/diskN (replace N with the disk number from the last command; in the previous example, N would be 2) NOTE: Maybe you need to force the unmount command for the USB disk by adding the force parameter