Using Open Secure Shell w/SUDO

[Paul M . Lambert]

This sort of question is often a sign of a misunderstanding of the nature
of one or both of the products in question.

SSH is a protocol for secure communications over a network.  It allows
a user on one machine to log into another machine, typically to run
an interactive shell, without the data in between being sent in the
clear.  This provides significant barriers to any interlopers trying
to intercept the traffic.

SUDO is a program used to give a user the ability to run certain
specific commands with privileges that the user normally does not have.
It has nothing to do with networks, and is typically (although not
exclusively) used interactively from a user's shell.

The two have little or nothing to do with each other, and as long
as each's own requirements are met, they will do what they are designed
to do.

That's the theoretical answer.

The one question that sometimes does come up in using both OpenSSH (or
any other SSH, or any other network shell protocol, such as rsh, rexec,
etc.) is to understand the meaning of 'tty' and the purpose of the -t
option to the ssh client command.  Essentially, if you try something
like: ssh remotehost sudo /path/to/remote/command

And it fails at the Password: prompt, you want to give the -t option to
ssh.  Don't give the option unless it's needed.

If you have any specific questions or problems, please don't hesitate to
share.  But please read the documentation of both products, as it will
really help you to understand what it is that they really do.

--Paul M. Lambert

On Tue, 07 Aug 2001, DAPILMOTO.RODNEY at heb.com wrote:

> Will SUDO work if we try using Open Secure Shell (SSH2) with it?
>