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.

Tip: Styles can be applied quickly to selected text.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Skeeve

harkman wrote:

@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.


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.
harkman

pseudo-tty option available in WinSCP?

Hello.

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 sodo like described here: https://winscp.net/eng/docs/faq_su
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.