Become for chroot connection plugin #49509
Add chroot_become variable to chroot plugin.
This feature useful when user have root permissions only for
bcoca left a comment
So 'become' is a misuse of the term here, first you are hardcoding to sudo, become is method agnostic, so su/dzdo/doas/etc .
Also become is meant for privilege escalation at the endpoint, not at the controller to execute the 'connection' itself, as such this will create much confusion on what the system does. There will also be a mismatch with other systems trying to compensate for 'user change' on the target while you are really changing the user 'at controller'.
I almost recommend creating an alternate connection plugin 'sudo_chroot' which will be a lot less confusing and not overload systems for different uses.
Which way is more preferable?
I want to use the