Re: [PATCH] Protection for exploiting null dereference using mmap

On Jun 6 2007 08:47, Stephen Smalley wrote:
>
>I'd be ok with having a different default for SELinux vs. non-SELinux,
>i.e. no restrictions by default under dummy/capability, but restrict it
>by default to 64k if selinux is enabled.  Then we can use policy to
>grant it as needed to the specific programs.

640k?



	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] Protection for exploiting null dereference using mmap
    • From: Eric Paris <[email protected]>
  • Re: [PATCH] Protection for exploiting null dereference using mmap
    • From: James Morris <[email protected]>
  • Re: [PATCH] Protection for exploiting null dereference using mmap
    • From: Alan Cox <[email protected]>
  • Re: [PATCH] Protection for exploiting null dereference using mmap
    • From: Eric Paris <[email protected]>
  • Re: [PATCH] Protection for exploiting null dereference using mmap
    • From: Stephen Smalley <[email protected]>

• Prev by Date: Re: Linux 2.6.22-rc4
• Next by Date: Re: Add INPUT support to toshiba_acpi
• Previous by thread: Re: [PATCH] Protection for exploiting null dereference using mmap
• Next by thread: Re: [PATCH] Protection for exploiting null dereference using mmap
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]