Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
Subject: application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
Subject: X Windows problem (xauth)
Subject: Upgrading openoffice 1 1 rpm
Subject: FTP: connection refused
Subject: FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
Subject: broadcom network interface
make mrproper
Couldn 't open PID file /var/run/named/named pid Permission denied
sendmail configuration on redhat
kernel 2 6 and /dev/sound/mixer not found
Subject: Promise 378 controller
Subject: Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
Subject: Lotus Notes under Wine
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
/etc/security/limits conf question
Intel E/1000 driver
rpm database corrupt
Command stream end of file while reading
qla2300 modules
 
Sudo & su

Sudo & su

2007-11-03       - By Rik van Riel

 Back
Reply:     1     2     3     4     5     6     7     8  

On Sat, 3 Nov 2007 18:22:16 -0500 (CDT)
"Chris St. Pierre" <stpierre@(protected)> wrote:

> On Sat, 3 Nov 2007, Carville, Stephen wrote:

> > Do not give it all then try to deny certain commands.  Any reasonably smart
use
> > can defeat that.  Start with nothing and allow only what is necessary.
>
> This is _excellent_ advice.
>
> Let's say you give someone sudo but don't allow them to run 'su'.  I
> can think of half a dozen ways off the top of my head to get around
> that:
>
> 'sudo bash'; run su
> 'sudo screen'; run su
> 'sudo emacs'; M-x shell; run su
> 'sudo script su'
> Write a shell script that invokes su and run it with sudo
> 'true | sudo xargs su'
>
> That was after about 30 seconds of thought.  A dedicated attacker
> could find significantly more avenues of attack.

less, vi and a number of other innocent looking programs
can be used to invoke a shell.

Of course, if you can sudo vi, you could just edit the
sudoers file.

Stephen's advice is to be taken seriously.

--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list