Protecting against kernel NULL-pointer derefs

[István]

the question is how much percent of the user are using wine and dosbox which
are going to break with this setting, i guess 10% or less. So those guys
could use _NO_VM_MIN kernel or something while the rest of the world would
fly high with secured kernel.

to quote a security friend:

the freebsd was the last target platform for this bugclass :))

regards,
Istvan


On Fri, Sep 18, 2009 at 4:13 PM, Hideki EIRAKU <hdk_2 at yahoo.co.jp> wrote:

> From: Pieter de Boer <pieter at thedarkside.nl>
> Subject: Protecting against kernel NULL-pointer derefs
> Date: Tue, 15 Sep 2009 10:03:48 +0200
>
> > - Are there unwanted side-effects of raising VM_MIN_ADDRESS?
>
> Mapping at address 0x0 is needed by some softwares using vm86 mode.
> For example, emulators/doscmd uses vm86 mode to emulate an old DOS
> environment. In this case, the address 0x0 - 0x3ff is used for an
> interrupt vector of emulated DOS world. If VM_MIN_ADDRESS is not zero,
> doscmd doesn't work. vm86 mode is in 32bit i386 architecture only, not
> in amd64 or other architectures.
>
> --
> Hideki EIRAKU
> --------------------------------------
> Thanks 10 years!  Yahoo! Shopping and Yahoo! Auctions
> http://pr.mail.yahoo.co.jp/ec10years/
> _______________________________________________
> freebsd-security at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-security
> To unsubscribe, send any mail to "freebsd-security-unsubscribe at freebsd.org
> "
>



-- 
the sun shines for all