[20440] in bugtraq

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

Re: Linux patches to solve /tmp race problem

daemon@ATHENA.MIT.EDU (Valdis Kletnieks)
Wed Apr 25 21:13:00 2001

Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1888239262P";
              micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Message-ID:  <200104251405.f3PE5wN09408@foo-bar-baz.cc.vt.edu>
Date:         Wed, 25 Apr 2001 10:05:58 -0400
Reply-To: Valdis.Kletnieks@VT.EDU
From: Valdis Kletnieks <Valdis.Kletnieks@VT.EDU>
X-To:         matthew@DATADELIVERANCE.COM
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  Your message of "Tue, 24 Apr 2001 20:13:30 +0930." 
              <15077.22738.538531.577231@localhost.localdomain>

--==_Exmh_1888239262P
Content-Type: text/plain; charset=us-ascii

On Tue, 24 Apr 2001 20:13:30 +0930, "Donaldson, Matthew" <matthew@DATADELIVERANCE.COM>  said:
> (e.g. because it's non open-source).  Having something like this gives them
> the security that even if someone is doing the Wrong Thing(tm), it does not
> put them at risk.

Puts them at much less risk.  The risk is still non-zero.  (Consider - does
the patch fix race conditions that happen to involve both /tmp *and* '..'
in the pathname?  What *other* end conditions are there?  Remember that
"non executable stack" patches don't stop all buffer overflows, they just
make them a LOT harder to exploit.....
--
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



--==_Exmh_1888239262P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOubZxnAt5Vm009ewEQLaXgCeI9yGP9CZJwFjEfX2XsJ7jc3XAp0AoKEN
oTlf6I78EWlIUKU+coM2liXP
=CIrY
-----END PGP SIGNATURE-----

--==_Exmh_1888239262P--

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