--
\ Real name : Juergen Heinzl \ no flames /
--
Manfred
----------------------------------------------------------------
NetfilterLogAnalyzer, NetCalc, whois at: <http://logi.cc/linux/>
> --
> \ Real name : Juergen Heinzl \ no flames /
I suggest "sudo", you can control which users can do what
as root (or as other personae). You can find it via
http://freshmeat.net/
hth
t
--
Just reach into these holes. I use a carrot.
I haven't installed it since I'm the only one with access to this machine
and so didn't even think of it, but perhaps it's just the right thing for
what you need for the given task(s) ? It'd be less "all or nothing" as
a full su access. You know -- rm -rf * ... oops 8-}
Cheers,
Juergen
--
\ Real name : Juergen Heinzl \ no flames /
With sudo you can also paper the trail with an auditable log of activity,Quote:> > Or I could edit he passwd file and change the :500:500:
> > to:0:0: for that particular user?
> Bad idea. Then that user *is* effectively root, always.
> I suggest "sudo", you can control which users can do what
> as root (or as other personae). You can find it via
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: Making the world safe for geeks.
iQA/AwUBOxWwfsAVSpfzXItKEQJargCg7dsX2O08cWKU53uPuUiT8fSySeUAnRs6
gZBE4oBvc9qpM8A7/u7DX4ma
=DVyM
-----END PGP SIGNATURE-----
--
Regards
Luke
------
ego.sh comes with a self installer. It is a single threaded multi
process daemon application thats facilitates access to the infamous
game "rat race". Warning uninstalling may enhance system performance.
------
PLEASE NOTE: Spamgard (tm) installed.
------
1. "su <user>" gives error, but works.
Hello,
when I do:
su <user>
I get an error:
/dev/ttyp3: Operation not permitted
(of course...)
I can understand this, but what can I do against it?
Or should I just let it be?
Thomer
2. Object-Oriented Network Programming tools now available
3. Forcing users to use su for shell access to shared system accounts
4. Linksys NAT/firewall--good or bad?
5. How to tell if user can access a file w/o su'ing.
8. files that begin with a "." (dot)
9. restricting user account to console or su access
10. su to a user then su to root in startup script
11. users have su priv's but su fails
12. su: allow all users to su to a login with their own password
13. Could su but says BAD SU from normal user to root