ssh and tty and sudoers file.
Knapp
magick.crow at gmail.com
Wed Aug 20 17:10:40 UTC 2008
On Wed, Aug 20, 2008 at 3:46 PM, Brian McKee <brian.mckee at gmail.com> wrote:
> On Wed, Aug 20, 2008 at 1:38 AM, Knapp <magick.crow at gmail.com> wrote:
>> On Wed, Aug 20, 2008 at 1:56 AM, Brian McKee <brian.mckee at gmail.com> wrote:
>>> On Tue, Aug 19, 2008 at 4:04 PM, Knapp <magick.crow at gmail.com> wrote:
>>> > Thus, when I am at home with my computer I want to use sudo but when I
>>> > am at
>>> > work I really don't need it or does anyone else that might hack into my
>>> > my
>>> > computer from a remote place thus blocking all people that are not at my
>>> > keyboard is a good idea.
>>> blocking the users in the sudo group from using the ssh server does
>>> not fufill your needs? That restricts sudo to the console which I
>>> thought was the goal. Or are you trying to make it 'location aware?'
>>> e.g. you can only sudo when your computer is on a certain network?
>> I like your suggestion and it would work but it would mean that I would need
>> 2 accounts as would all the other people that might need to use sudo.
>
> The light dawned on me last night eventually. You want the same
> people to be able to sudo at the console, ssh in, but not sudo when
> using ssh! Doing it my way as you point out they need two user
> accounts and part of the advantage of sudo is negated.
> I don't have a solution for that :-(
>
> Brian
Yes! Sorry could not explain it better to you.
I am sure that the sudoer file can do it but it is so complex and the
risk of loosing sudo for exeryone is high so I don't want to just play
with it.
If I do X the sudoer file could I go into the HD with Damn Small Linux
and fix it? Or is it coded somehow? I would think I could but want to
be sure.
--
Douglas E Knapp
http://sf-journey-creations.wikispot.org/Front_Page
More information about the ubuntu-users
mailing list