[sudo-users] Fwd: SUDO package for Sparc version 1.6.8p12
Manochehri, Tim
Tim.Manochehri at blueshieldca.com
Thu Jun 28 11:31:45 EDT 2007
Hi all,
I am not running vim.
I've done the ldd to both sudo and vi.
# ldd `which sudo`
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1
# ldd `which vi`
libmapmalloc.so.1 => /usr/lib/libmapmalloc.so.1
libcurses.so.1 => /usr/lib/libcurses.so.1
libcrypt_i.so.1 => /usr/lib/libcrypt_i.so.1
libgen.so.1 => /usr/lib/libgen.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1
So I too was stumped.
BTW: I managed to remove the NOEXEC piece and replaced it
with sudoedit.
-----Original Message-----
From: Chris Jepeway [mailto:jepeway at blasted-heath.com]
Sent: Thursday, June 28, 2007 5:04 AM
To: Paul Stepowski
Cc: Manochehri, Tim; sudo-users at sudo.ws
Subject: Re: [sudo-users] Fwd: SUDO package for Sparc version 1.6.8p12
> If the problem is a non (Solaris) standard vi linked to GCC:
>
> vi <filename>
>
> Would fail too with the same error, no? Easy enough to confirm.
Well, if Tim's environment kept LD_LIBRARY_PATH in place
to run vim--installed as /usr/bin/vi--and vim used libgcc_s, then there
*would* be a difference between running with a
(mostly) empty environment and not.
>
> NOTE: If you compile sudo against GCC and the libgcc_s.so.1, is not
> present,
> sudo will still run fine, unless you try to run a command using the
> NOEXEC
> feature. Then you'll see the linking error.
Aha. That's the part I *didn't* know about NOEXEC,
and why I fwd'ed his msg along to y'all.
> Paul
Chris.
More information about the sudo-users
mailing list