Hello, guys, and welcome in this section, I'll show you how to configure SSX public key authentication
on Cisco, iOS and Linux.
B.K., or public key authentication is an authentication method that uses a key player for authentication
instead of a password, which is the default method.
This type of authentication is considered the more secure because the default password method suffers
from potential security vulnerabilities, like a brute force, login attempts or key loggers installed
on the client.
Another advantage of using public key authentication is that you are able to log in to servers from
within scripts or automation tools that run unattended.
For example, you can set up periodic updates for your servers using arsing, or you can use a configuration
management tool like Ansible, and you run these applications automatically from a current job without
any human intervention for entering the password.
In piqué, there are two types of keest generated a public and the private key.
In public authentication, a user creates a both a public and the private key and the then transfers
a copy of the public key to the SSA server to the user wants to secure access.
The private keys kept on the user's local machine and is used to verify the identity of the user when
the user attempts to connect to the server.
Anyone user or device that pays the public will be able to encrypt the data that can only be decrypted
by the user or the device that has the private key.
This means that you can share the public with anyone and they will have the ability to send encrypted
messages, messages that will be decrypted only by using the private key.
So in a nutshell, for SSA, the private keys stays on the client and the public keys stays on the server.
The private keys used to encrypt the messages that will be decrypted by the server using the public.
However, you need to protect the privacy of the private key.
Anyone who has it can decrypt the encrypted messages.
This can be accomplished by encrypting the private key with a passphrase which is similarly to a password.
Before the client can read the private key.
In order to perform the public authentication process, you'll be asked to supply the passphrase in
order to decrypt the private key one more secure systems.
You can simplify this process either by creating an unencrypted key, so a key with no for or by entering
your passphrase once and then cashing the key in memory for later use openness, which contains a tool
called essayistic agent, which simplifies this process.
I can honestly say that it's common to have an unencrypted private key, especially in cases where age
is used to automate different things in this section will generate a public and a private key both on
Windows and the Linux will then configure both Cisco, iOS and the Linux for SSL authentication.
So at the end of the section, you will have the knowledge to authenticate using PKK from both Windows
and Linux to both Cisco OS and Linux.
OK, that was just a short introduction to Piqué.
Let's take a short break and in the next lecture's I'll show you some Hentzen examples of how to configure
public key authentication.
See you in a minute.