atom feed21 messages in org.freebsd.freebsd-archRe: How much security should ldconfig...
FromSent OnAttachments
John PolstraJul 26, 2000 7:35 pm 
Chris CostelloJul 26, 2000 8:54 pm 
Nate WilliamsJul 26, 2000 10:54 pm 
Mark MurrayJul 26, 2000 11:15 pm 
Warner LoshJul 26, 2000 11:24 pm 
Adrian ChaddJul 27, 2000 12:03 am 
Poul-Henning KampJul 27, 2000 12:30 am 
Alfred PerlsteinJul 27, 2000 12:44 am 
Jacques A. VidrineJul 27, 2000 5:50 am 
Neil Blakey-MilnerJul 27, 2000 5:52 am 
Jacques A. VidrineJul 27, 2000 6:38 am 
Daniel O'ConnorJul 27, 2000 6:44 am 
Neil Blakey-MilnerJul 27, 2000 6:47 am 
Robert WatsonJul 27, 2000 8:14 am 
Alfred PerlsteinJul 27, 2000 9:39 am 
Jacques A. VidrineJul 27, 2000 11:03 am 
Ollivier RobertJul 27, 2000 12:32 pm 
John PolstraJul 27, 2000 9:28 pm 
John PolstraJul 27, 2000 9:38 pm 
Alexander LeidingerJul 28, 2000 5:09 am 
John PolstraJul 28, 2000 8:21 am 
Subject:Re: How much security should ldconfig enforce?
From:Ollivier Robert (robe@keltia.freenix.fr)
Date:Jul 27, 2000 12:32:39 pm
List:org.freebsd.freebsd-arch

According to John Polstra:

1. It could allow anything, just like it did before I made my commit.

2. It could strictly enforce secure ownerships, groups, and permissions -- i.e., keep last night's commit and add group writability checking too.

3. It could default to strictly secure but accept a command-line option to relax the constraints. And an rc.conf knob could be added to control whether or not it was strict at boot time.

#3 seems to me the Right Thing[tm].

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message