[930] in linux-security and linux-alert archive

home help back first fref pref prev next nref lref last post

[linux-security] writing setuid programs safely

daemon@ATHENA.MIT.EDU (Lars Wirzenius)
Thu Jul 18 21:24:27 1996

From: Lars Wirzenius <liw@iki.fi>
To: linux-security@tarsier.cv.nrao.edu
In-Reply-To: Your message of "Tue, 16 Jul 1996 11:12:02 MDT."
             <Pine.LNX.3.91.960716110840.14386E-100000@cheetah.spots.ab.ca> 
Date: Thu, 18 Jul 1996 10:21:20 +0300

--==_Exmh_-1305269074P
Content-Type: text/plain; charset=us-ascii

[ NB: I read the list.  Don't CC replies to me.  I pay for my PPP.  Thanks ]

Jason Marshall:
> Is there a list somewhere of ALL the things that really should 
> be done or looked for when writing code segments that are seteuid(0)?

I saw a setuid(7) manual page in some newsgroup years ago.  Didn't save
it and can't remember whodunit, but someone with a better network connection
might want to look for it with the WWW search engines.  Hm, the name
Henry Spencer seems to be floating in my frontal lobe at the moment, but
I don't know if he had anything to do with it.



--==_Exmh_-1305269074P
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.2i

iQCVAwUBMe3l7YQRll5MupLRAQEslgQA0wcZRtu5NbWquzTKJemaEH3laEMB1jZ+
9Dp8v0aP+S5g+IH/OtL3qjlW2mrJNYsm2YsegOPSrrTI7DJc7oYBmiJYyGwk2kS7
xe4sP+CoekD0GS3u1NuRtg03Kh5OnvJkt31XxrjZJ71otOXsiW/F1esIx37Lyzsx
vsHQW3ZX7eg=
=KIBc
-----END PGP MESSAGE-----

--==_Exmh_-1305269074P--

home help back first fref pref prev next nref lref last post