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:John Polstra (jd@polstra.com)
Date:Jul 27, 2000 9:38:47 pm
List:org.freebsd.freebsd-arch

In article <Pine@fledge.watson.org>, Robert Watson <rwat@FreeBSD.ORG> wrote:

I would support either the "revert" or (3) option, but definitely not support this being a compile-time flag.

Don't worry, it isn't going to be a compile-time flag. :-)

So my preference here is: permissions and ownership in the base install are fine. The default compile (and preferably install) should allow users to include group-writable shared library paths, if not world-writable paths.

One thing to consider is that the hints file is only writable by root. In fact, ldconfig sets it to mode 444 every time it updates it. So your average user can't even _run_ ldconfig in any mode except to list the existing hints file. Allowing group-writable shared library directories is useless for adding new directories because you still have to persuade root to run the ldconfig command for you. OTOH, if ldconfig has already been run then you can add new files to an existing directory without rerunning ldconfig. (That's specific to ELF. It won't work for a.out.) Does this change your opinion?

John

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