From: Eduardo M KALINOWSKI on
On Qui, 29 Jul 2010, "Boyd Stephen Smith Jr." wrote:
> See my reply to Eduardo. In short, having (sudo su) available does not mean
> that (sudo -i) will work.

Well, if you wanna give a full root shell to someone, then do it in
the correct way (allowing sudo -i to work), instead of allowing "su"
via sudo.


--
BOFH excuse #233:

TCP/IP UDP alarm threshold is set too low.

Eduardo M KALINOWSKI
eduardo(a)kalinowski.com.br


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100729135645.164536wnehed0iio(a)mail.kalinowski.com.br
From: Jordon Bedwell on
On 7/29/10 11:31 AM, Jordan Metzmeier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
>>
>> I understand your issues with all but the last one. A user may need
>> to "sudo su" due to configuration outside of their control. A system
>> that requires you to "sudo su" for some task is likely misconfigured,
>> but it is a useful tool to have around, as a user.
>>
>> The rest are less useful, and generally imply a limited, incomplete,
>> or flawed understanding of one or more of the tools you are using.
>
> I no longer configure my machines in a way that it allows a user to gain
> full root via sudo. However, when I did, I found "sudo -i" to be more
> appropriate than "sudo su" which seems to be more like "su -l". Of
> course, you could always do "sudo su -l".
>
> - From the manpage:
>
> - -i The -i (simulate initial login) option runs the shell specified in
> the passwd(5) entry of the user that the command is being run as.
> The command name argument given to the shell begins with a '-' to
> tell the shell to run as a login shell. sudo attempts to change to
> that user's home directory before running the shell. It also ini‐
> tializes the environment, leaving TERM unchanged, setting HOME,
> SHELL, USER, LOGNAME, and PATH, and unsetting all other environment
> variables. Note that because the shell to use is determined before
> the sudoers file is parsed, a runas_default setting in sudoers will
> specify the user to run the shell as but will not affect which
> shell is actually run.
>

I think the irony is still hitting from: "generally imply a limited,
incomplete, or flawed understanding of one or more of the tools you are
using"



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C51B1AB.8000507(a)envygeeks.com
From: Boyd Stephen Smith Jr. on
On Thursday 29 July 2010 11:31:05 Jordan Metzmeier wrote:
> On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
> > I understand your issues with all but the last one. A user may need
> > to "sudo su" due to configuration outside of their control. A system
> > that requires you to "sudo su" for some task is likely misconfigured,
> > but it is a useful tool to have around, as a user.
> >
> > The rest are less useful, and generally imply a limited, incomplete,
> > or flawed understanding of one or more of the tools you are using.
>
> I no longer configure my machines in a way that it allows a user to gain
> full root via sudo. However, when I did, I found "sudo -i" to be more
> appropriate than "sudo su" which seems to be more like "su -l". Of
> course, you could always do "sudo su -l".

See my reply to Eduardo. In short, having (sudo su) available does not mean
that (sudo -i) will work.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss(a)iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
From: Jordon Bedwell on
On 7/29/10 11:51 AM, Boyd Stephen Smith Jr. wrote:
> On Thursday 29 July 2010 11:31:05 Jordan Metzmeier wrote:
>> On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
>>> I understand your issues with all but the last one. A user may need
>>> to "sudo su" due to configuration outside of their control. A system
>>> that requires you to "sudo su" for some task is likely misconfigured,
>>> but it is a useful tool to have around, as a user.
>>>
>>> The rest are less useful, and generally imply a limited, incomplete,
>>> or flawed understanding of one or more of the tools you are using.
>>
>> I no longer configure my machines in a way that it allows a user to gain
>> full root via sudo. However, when I did, I found "sudo -i" to be more
>> appropriate than "sudo su" which seems to be more like "su -l". Of
>> course, you could always do "sudo su -l".
>
> See my reply to Eduardo. In short, having (sudo su) available does not mean
> that (sudo -i) will work.

I miss the logic here, as the logic is flawed. If you have the ability
to sudo su, you certainly have the ability to sudo -i otherwise you
would do "sudo su /u/" would you not?


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C51B276.4020607(a)envygeeks.com
From: Eduardo M KALINOWSKI on
On Qui, 29 Jul 2010, Andrei Popescu wrote:
> add
>
> dpkg -l | grep <packagename>

At least here (a somewhat old 8.04 Ubuntu), dpkg -l still requires grep:

$ dpkg -l gnome
No packages found matching gnome.
$ dpkg -l | grep gnome
$ LANG=C dpkg -l | grep gnome
ii bluez-gnome 0.25-0ubuntu1
Bluetooth utilities for [... Several
lines of packages]
ii xulrunner-1.9-gnome-support
1.9.0.9+nobinonly-0ubuntu0.8.04.1 Support for Gnome
in xulrunner-1.9 applications




--
War hath no fury like a non-combatant.
-- Charles Edward Montague

Eduardo M KALINOWSKI
eduardo(a)kalinowski.com.br


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100729135929.136823m6b4updpj4(a)mail.kalinowski.com.br