Re: /tmp exploits

To: debian-devel@lists.debian.org
Subject: Re: /tmp exploits
From: Guy Maor <maor@ece.utexas.edu>
Date: 20 Apr 1998 23:47:20 -0700
Message-id: <[🔎] 87g1j7k6x3.fsf@1Cust14.max32.los-angeles.ca.ms.uu.net>
In-reply-to: Manoj Srivastava's message of "20 Apr 1998 16:44:13 -0500"
References: <[🔎] E0yRFYQ-0000Q7-00@chiark.greenend.org.uk> <[🔎] 87zphg9v69.fsf@tiamat.datasync.com> <[🔎] E0yRNP5-000069-00@chiark.greenend.org.uk> <[🔎] 87lnt09niq.fsf@tiamat.datasync.com>

I agree with Manoj here.

Modifying libc to catch common security goals is a laudable goal, but
such a libc should go to experimental.


Guy


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

Follow-Ups:
- Re: /tmp exploits
  - From: Riku Voipio <riku.voipio@iki.fi>

References:
- /tmp exploits
  - From: Ian Jackson <ijackson@chiark.greenend.org.uk>
- Re: /tmp exploits
  - From: Manoj Srivastava <srivasta@datasync.com>
- Re: /tmp exploits
  - From: Ian Jackson <ian@chiark.greenend.org.uk>
- Re: /tmp exploits
  - From: Manoj Srivastava <srivasta@datasync.com>

Prev by Date: weird utmp/perl problem
Next by Date: Re: [sara@ora.com: NPR show on open source]
Previous by thread: Re: /tmp exploits
Next by thread: Re: /tmp exploits
Index(es):
- Date
- Thread