If we're talking about a userland.<applicationname> and having
applications decide wether or not they want to use the new random
malloc, maybe looking into setting up something like Darwin's
'defaults' would be a good way to go.

-zach

On Mon, Dec 03, 2001 at 07:44:24AM -0500, Robert Watson wrote:
>
> On Mon, 3 Dec 2001, Alfred Perlstein wrote:
>
> > * Oleg Cherkasov <Oleg.Cherkasovmail.com> [011203 03:16] wrote:
> > >
> > > Think a new key 'malloc.random' for sysctl could be more useful, protected
> > > with 'kern.securelevel' > 1.
> >
> > However, malloc(3) has nothing to do with the kernel.
>
> Yeah, I'm not sure why it would be keyed off of 'securelevel'. Seems to
> me that we should avoid any more userland cruft being associated
> unnecessarily with securelevels, actually :-).
>
> And if we do stuff this in a securelevel, it sounds like we need a
> userland.<applicationname> sysctl namespace. More likely, we just need
> this to be a flag on /etc/malloc.conf.
>
> Robert N M Watson FreeBSD Core Team, TrustedBSD Project
> robertfledge.watson.org NAI Labs, Safeport Network Services
>
>
> To Unsubscribe: send mail to majordomoFreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message

-- 

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org

iD8DBQE8C7e3M6FaXlC3H6ARApJPAJ9nixMqxizD8dLQpykXhlVt+XVJ5QCfScJ5 rFoPNK3UiADaAUPNHI17kbk= =g+Dv -----END PGP SIGNATURE-----

To Unsubscribe: send mail to majordomoFreeBSD.org with "unsubscribe freebsd-security" in the body of the message

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]