Not yet. It's not really high-priority, sorry.
- martin
I posted WinSCP askpass tips please and found a workaround for me.
Background: On my targetserver I can only log in with my personal account. There I am only allowed to do asudo su - TARGETUSER
. This is then prompting me for the password.
sudo
this command without requiring a password?
su
/sudo
support (without any extra script {or other "hacking" to make it work}, that is)
su
& sudo
should be added: that is a major use-case...ALL "root" users should login as "someuser" & then su or sudo to root.
su
or sudo
to perform the change...but of course, there should also be a login/connection option "Immediately Switch Remote User after login"... like have two username fields on the Login/Connection Info box.
su
/sudo
detection above.
su
/sudo
support should be added, since that is a common security practice of "never login directly as root".
No comment at all?
sudo su - functionaluser
.ssh/authorized_keys
, but that's not wanted.
sudo
which calls a script reading from the fifo and thus getting my password.
#!/bin/sh
echo -n "sudo password:"
read pass
echo $pass
sudo su - TARGETUSER
. This is then prompting me for the password.
sudo
as SUDO_ASKPASS
. That script is connecting to a fifo where, on the other end, I have an open terminal session where I enter my password. This seems to work quite good, besides the small security risk that someone could read from my fifo while I'm thinking I'm communicating with my WinSCP-invoked script.
sudo
via stdout.