fab-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fab-user] sudo: sorry, you must have a tty to run sudo


From: Christian Vest Hansen
Subject: Re: [Fab-user] sudo: sorry, you must have a tty to run sudo
Date: Thu, 12 Feb 2009 13:52:00 +0100

If we are required to open a shell session, rather than a simple
"command" (or what it's called) session to the SSH server, then we run
into issues of determining whether the commands we execute complete
successfully or not.

The SSH protocol allow us to get the exit code back from any command
we run, and we use this to tell whether the commands we run are
successful or not. But when we open a shell session, this exit code
will always be that of the shell, and not whatever command we executed
through the shell. Also, I don't know of a stable way of telling which
shell we actually get, when we open such a session.

On Thu, Feb 12, 2009 at 12:44 AM, Jeff Forcier <address@hidden> wrote:
> I recall this coming up before, but not the final resolution. Might
> want to try searching the list archives in case I'm not misremembering
> :)
>
> Have you confirmed that this works with Capistrano and its tty option?
> Alternately, try doing "ssh my_rhel_server -t sudo some_command",
> which AFAIK would emulate the same behavior (forcing a pseudo-tty).
>
> I'm not positive that the tty-related option will actually work --
> given that the sudoers manpage says "a real tty" and I'm not sure what
> exactly they mean by that -- but a quick Google seems to imply that it
> will. In that case, yes, we can likely add an argument/option/whatever
> to enable that aspect of the protocol when desired.
>
> About to embark on a potential rewrite of our SSH code to use a
> different library, but once that settles out either way, it should be
> pretty simple to put such a change in place.
>
> Best,
> Jeff
>
> On Wed, Feb 11, 2009 at 6:21 PM, Alex Robbins
> <address@hidden> wrote:
>> Thanks for the quick answer to the last question.
>> This time the issue is running sudo on the remote hosts. I get this error:
>> sudo: sorry, you must have a tty to run sudo
>>
>> I know that I can take requiretty out of the sudoers file, but is that a
>> security issue? Some google searching showed that capistrano has an option
>> to make tty on connection. Is that an idea under consideration?
>> (Running RHEL5.)
>> Thanks,
>> Alex
>> _______________________________________________
>> Fab-user mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/fab-user
>>
>>
>
>
> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>



-- 
Venlig hilsen / Kind regards,
Christian Vest Hansen.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]