[Autogenerated] actually talking about MF A Have you
have any problems with people?
Uh, you know, saying this is m f A when it's clearly not MF.
Yes, actually, the maybe the most common example of that is the use of SSH keys.
Right, Right.
So, uh, a lot of organizations, a lot of a lot of sort of UNIX error.
Linux savvy folks like using SSH CSS because they regard passwords is terrible.
And there's there's merit to that notion.
But they think that it's multi factor authentication, right?
And so I won't get into the SSH key exchange because that's not really relevant.
But the point is, when you connect over SSH using an SSH key,
the client prompts you as the administrator of the user for a password,
right?
And there's a key exchange right that uses some cryptographic
techniques to sort of verify your identity.
Uh, but the thing is,
that password does not go to the server does not go to the destination.
That password is just to decrypt the private key of that SSH!
Keep error that resides on your local machine,
right,
and you could configure your client to not require that or not have any
sort of parameters for that password to be any good,
right?
It's it's analogous to if I have, If I have a soft token,
a thin Decatur on my mobile device,
the lock screen pass code for my mobile device is that password for SSH,
right?
You know, when I log into my Gmail account and I use my Google authenticator,
Google doesn't know or care that I have a lock screen code on my phone.
It's not.
It's not on authenticating factor.
I still need a user name and password and then,
you know, my my Google authenticator, you know,
soft token.
Alright.
So you know,
I think in at least some cases you can configure SSH to
require a user name and password that goes to the server and
then also requires the SSH key.
But that's not how it comes out of the box.
And at that stage, I'm good because I've got I've got two factors.
I've got some, you know, and and key that you see that I have right?
Okay, right