| 1 |
On Thu, 14 Jul 2022 09:37:45 -0600, Grant Taylor wrote: |
| 2 |
|
| 3 |
> > Is this user only used as a gateway to root access, or can you set |
| 4 |
> > up such a user? If so you could use key-based authentication for |
| 5 |
> > that user, with a passphrase, and add command="/bin/su --login" |
| 6 |
> > to the authorized_keys line. That way you still need three pieces |
| 7 |
> > of information, |
| 8 |
> |
| 9 |
> Be mindful that despite the fact that this protects things on the |
| 10 |
> surface, it is / can be a way to boot strap changing this. |
| 11 |
> |
| 12 |
> After all, nothing about this forced command prevents the user from |
| 13 |
> using the acquired root access to modify the ~/.ssh/authorized_keys |
| 14 |
> file enforcing the command. |
| 15 |
|
| 16 |
That is true, but it is also true about the current setup as that also |
| 17 |
gives root access. I get the impression that Joost is looking for a more |
| 18 |
convenient approach that does not reduce security, which is true here... |
| 19 |
|
| 20 |
> > replacing the user's password with the user's key passphrase. |
| 21 |
> |
| 22 |
> This is another slippery slope. SSH key pass phrases can be brute |
| 23 |
> forced in an offline fashion. Conversely, system passwords are more of |
| 24 |
> an online attack. |
| 25 |
|
| 26 |
Well, almost true. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Neil Bothwick |
| 31 |
|
| 32 |
Barth's Distinction: |
| 33 |
There are two types of people: those who divide people into two types, and |
| 34 |
those who don't. |
Archives