![]() $ service ssh restartĥ – Test the login $ ssh $ chmod 400 ~/.google_authenticatorĤ – Restart the ssh service. We’re going to install the program but not do the creation of any secret keys $ sudo apt-get install libpam-google-authenticatorĢ – Create the configuration file and add the content that we got from the other machine: $ cat -> ~/.google_authenticatorģ – Set permissions for the configuration file. ![]() Again, other places describe this in detail. This will let me log into each of them using that same secret key that I stored from the first machine.ġ – Install Google Authenticator. $ cat ~/.google_authenticatorĨ2870703 Installing Google Authenticator On Additional Machinesįor all other machines I’m going to install Google Authenticator as normal, but I’m going to use the secret key from the first machine. We’re going to copy these contents to our other machines that we want to have the same secret key. Welcome to Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-29-generic i686)ĥ – Let’s take a look at the configuration file. From another shell go ahead and try it out. I don’t need to comment that you actually have to enter the secret key into your phone, do I? $ google-authenticatorĤ – Give it a spin. This information will be stored in a configuration file that we’re going to get into later. $ sudo apt-get install libpam-google-authenticatorĢ – Restart the ssh service $ sudo restart sshģ – Run the google-authenticator command to generate a secret key for your account which you’ll store in your phone. I won’t walk through each step since this part varies from OS to OS – the rest of the steps are identical however. This is pretty well documented, examples at untrusted connection and How-To Geek. My first machine I’m going to install Google Authenticator and create a secret key – the exact flow I’d use normally.ġ – Install Google Authenticator. Here’s how I installed and configured Google Authenticator on each system First Machine Instead, I want to have one Google Authenticator token for multiple servers. Obviously, this quickly becomes unwieldy and untenable. The standard setup would have you run the google-authenticator command on each and have as many tokens as you have servers. ![]() The message Secret saved appears.What is a bit painful, though, is having to have a different Google Authenticator token for every one of my servers. In the Key field, enter the string of numbers and letters that you made a note of earlier.In the Account field, enter your Okta username.On your mobile device, launch Google Authenticator.In the field above the Next button, make a note of the string of numbers and letters. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |