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

On Tue, 5 Jun 2007, Eric Paris wrote:

> +extern int mmap_protect_memory;

This should be an unsigned long.

I wonder if the default should be for this value to be zero (i.e. preserve 
existing behavior).  It could break binaries, albeit potentially insecure 
ones.


- James
-- 
James Morris
<[email protected]>
-
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/

Follow-Ups:
- Re: [PATCH] Protection for exploiting null dereference using mmap
  - From: Alan Cox <[email protected]>

References:
- [PATCH] Protection for exploiting null dereference using mmap
  - From: Eric Paris <[email protected]>

Prev by Date: [PATCH] lib: Replace calls to __get_free_pages() with __get_dma_pages().
Next by Date: Re: [RFC][PATCH] muptiple bugs in PI futexes
Previous by thread: [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]