21 messages in org.freebsd.freebsd-archRe: How much security should ldconfig...| From | Sent On | Attachments |
|---|---|---|
| John Polstra | Jul 26, 2000 7:35 pm | |
| Chris Costello | Jul 26, 2000 8:54 pm | |
| Nate Williams | Jul 26, 2000 10:54 pm | |
| Mark Murray | Jul 26, 2000 11:15 pm | |
| Warner Losh | Jul 26, 2000 11:24 pm | |
| Adrian Chadd | Jul 27, 2000 12:03 am | |
| Poul-Henning Kamp | Jul 27, 2000 12:30 am | |
| Alfred Perlstein | Jul 27, 2000 12:44 am | |
| Jacques A. Vidrine | Jul 27, 2000 5:50 am | |
| Neil Blakey-Milner | Jul 27, 2000 5:52 am | |
| Jacques A. Vidrine | Jul 27, 2000 6:38 am | |
| Daniel O'Connor | Jul 27, 2000 6:44 am | |
| Neil Blakey-Milner | Jul 27, 2000 6:47 am | |
| Robert Watson | Jul 27, 2000 8:14 am | |
| Alfred Perlstein | Jul 27, 2000 9:39 am | |
| Jacques A. Vidrine | Jul 27, 2000 11:03 am | |
| Ollivier Robert | Jul 27, 2000 12:32 pm | |
| John Polstra | Jul 27, 2000 9:28 pm | |
| John Polstra | Jul 27, 2000 9:38 pm | |
| Alexander Leidinger | Jul 28, 2000 5:09 am | |
| John Polstra | Jul 28, 2000 8:21 am |
| Subject: | Re: How much security should ldconfig enforce? | |
|---|---|---|
| From: | Mark Murray (ma...@grondar.za) | |
| Date: | Jul 26, 2000 11:15:26 pm | |
| List: | org.freebsd.freebsd-arch | |
Just kidding -- this is about ldconfig. Last night I committed some security-related changes that somebody submitted to me. The changes make ldconfig refuse to pay attention to directories which are world-writable or not owned by root. In the commit message I also stated a desire to strengthen it further by disallowing group-writable directories.
I thought that was good :-)
1. It could allow anything, just like it did before I made my commit.
Not a good idea, but...
2. It could strictly enforce secure ownerships, groups, and permissions -- i.e., keep last night's commit and add group writability checking too.
...your correspondent had a point, however.
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.
Could it relax constraints on a per-directory basis, so that folk who want a shared lib dir with *this* privelige *here* can do that?
M
-- Mark Murray Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message