- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Skeeve
@harkman: Publickey is better for SSH anyway. For
sudo, if you can live without the additional password – great. In my environment I can't switch it off. That's why I had to find a workaround.
- harkman
@Skeeve: Thanks for the link. I will try this eventually. For now we switched to public key based authorisation and disabled password auth. I think this way we can disable
requiretty without breaching security.
- Skeeve
Maybe this is a valid workaround for you?
WinSCP askpass tips please
WinSCP askpass tips please
- martin
Re: pseudo-tty option available in WinSCP?
- harkman
pseudo-tty option available in WinSCP?
Hello.
Unix
Can this be done with WinSCP too?
Background:
We use a CentOS 6 and have blocked root login with SSH
I try to setup the login with WinSCP with a unprivileged user and the doing
Problem now is that WinSCP cannot establish a connection because
As I really do not want to expose any passwords I'd like to keep the
Unix
ssh client has a option to create a pseudo-tty when establishing a new connection (ssh -t).
Can this be done with WinSCP too?
Background:
We use a CentOS 6 and have blocked root login with SSH
I try to setup the login with WinSCP with a unprivileged user and the doing
sudo like described here: How do I change user after login (e.g. su root)?
Problem now is that WinSCP cannot establish a connection because
sudo is only allowed if a proper shell is created. Sudo configuration explains:
#
# Disable "ssh hostname sudo <cmd>", because it will show the password in clear.
# You have to run "ssh -t hostname sudo <cmd>".
#
Defaults requiretty
As I really do not want to expose any passwords I'd like to keep the
sudo config this way.