On Thu, 14 Jul 2022 09:37:45 -0600, Grant Taylor wrote: > > Is this user only used as a gateway to root access, or can you set > > up such a user? If so you could use key-based authentication for > > that user, with a passphrase, and add command="/bin/su --login" > > to the authorized_keys line. That way you still need three pieces > > of information, > > Be mindful that despite the fact that this protects things on the > surface, it is / can be a way to boot strap changing this. > > After all, nothing about this forced command prevents the user from > using the acquired root access to modify the ~/.ssh/authorized_keys > file enforcing the command.
That is true, but it is also true about the current setup as that also gives root access. I get the impression that Joost is looking for a more convenient approach that does not reduce security, which is true here... > > replacing the user's password with the user's key passphrase. > > This is another slippery slope. SSH key pass phrases can be brute > forced in an offline fashion. Conversely, system passwords are more of > an online attack. Well, almost true. -- Neil Bothwick Barth's Distinction: There are two types of people: those who divide people into two types, and those who don't.
pgp0dpdmQYd4i.pgp
Description: OpenPGP digital signature
