On Wed, Jan 02, 2008 at 06:26:07PM +0100, Jan Engelhardt wrote:
>
> On Jan 2 2008 12:09, Eric Paris wrote:
> >
> >So in the end we are all happy with the original patch I sent?
> >
> No objections at least :)
I agree too. BTW, I've intentionally not merged it into 2.4, I
prefer that admins
On Jan 2 2008 12:09, Eric Paris wrote:
>
>So in the end we are all happy with the original patch I sent?
>
No objections at least :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Fri, 2007-12-21 at 23:59 +0100, Jan Engelhardt wrote:
> On Dec 21 2007 14:35, Greg KH wrote:
> >> >> >I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
> >> >> >base 10 as well
> >> >>
> >> >> sysfs is autobase, i.e. echo "0xb000" >/sys/foo will Do The Right Thing.
> >> >
>
On Fri, 2007-12-21 at 23:59 +0100, Jan Engelhardt wrote:
On Dec 21 2007 14:35, Greg KH wrote:
I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
base 10 as well
sysfs is autobase, i.e. echo 0xb000 /sys/foo will Do The Right Thing.
yes but if you cat
On Jan 2 2008 12:09, Eric Paris wrote:
So in the end we are all happy with the original patch I sent?
No objections at least :)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Wed, Jan 02, 2008 at 06:26:07PM +0100, Jan Engelhardt wrote:
On Jan 2 2008 12:09, Eric Paris wrote:
So in the end we are all happy with the original patch I sent?
No objections at least :)
I agree too. BTW, I've intentionally not merged it into 2.4, I
prefer that admins deliberately
On Dec 21 2007 14:35, Greg KH wrote:
>> >> >I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
>> >> >base 10 as well
>> >>
>> >> sysfs is autobase, i.e. echo "0xb000" >/sys/foo will Do The Right Thing.
>> >
>> >yes but if you cat /proc/sys/vm/mmap_min_addr, it returns in base
On Fri, Dec 21, 2007 at 11:04:19PM +0100, Jan Engelhardt wrote:
>
> On Dec 21 2007 22:16, Willy Tarreau wrote:
> >Hi Jan,
> >
> >> >> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
> >> >> >+int "Low address space to protect from user allocation"
> >> >>
> >> >> Hm, should not this be 'hex'?
>
On Fri, Dec 21, 2007 at 10:10:24PM +0100, Jan Engelhardt wrote:
>
> On Dec 21 2007 15:31, Eric Paris wrote:
> >On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
> >> On Dec 19 2007 16:59, Eric Paris wrote:
> >> >
> >> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
> >> >+int "Low address
On Dec 21 2007 22:16, Willy Tarreau wrote:
>Hi Jan,
>
>> >> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
>> >> >+int "Low address space to protect from user allocation"
>> >>
>> >> Hm, should not this be 'hex'?
>> >
>> >I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
>>
Hi Jan,
On Fri, Dec 21, 2007 at 10:10:24PM +0100, Jan Engelhardt wrote:
>
> On Dec 21 2007 15:31, Eric Paris wrote:
> >On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
> >> On Dec 19 2007 16:59, Eric Paris wrote:
> >> >
> >> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
> >> >+int "Low
On Dec 21 2007 15:31, Eric Paris wrote:
>On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
>> On Dec 19 2007 16:59, Eric Paris wrote:
>> >
>> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
>> >+int "Low address space to protect from user allocation"
>>
>> Hm, should not this be 'hex'?
>
On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
> On Dec 19 2007 16:59, Eric Paris wrote:
> >
> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
> >+int "Low address space to protect from user allocation"
>
> Hm, should not this be 'hex'?
I guess it could be, but the input for
On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
On Dec 19 2007 16:59, Eric Paris wrote:
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to protect from user allocation
Hm, should not this be 'hex'?
I guess it could be, but the input for
On Dec 21 2007 15:31, Eric Paris wrote:
On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
On Dec 19 2007 16:59, Eric Paris wrote:
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to protect from user allocation
Hm, should not this be 'hex'?
I guess it could
Hi Jan,
On Fri, Dec 21, 2007 at 10:10:24PM +0100, Jan Engelhardt wrote:
On Dec 21 2007 15:31, Eric Paris wrote:
On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
On Dec 19 2007 16:59, Eric Paris wrote:
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to
On Dec 21 2007 14:35, Greg KH wrote:
I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
base 10 as well
sysfs is autobase, i.e. echo 0xb000 /sys/foo will Do The Right Thing.
yes but if you cat /proc/sys/vm/mmap_min_addr, it returns in base 10.
sysfs should
On Fri, Dec 21, 2007 at 10:10:24PM +0100, Jan Engelhardt wrote:
On Dec 21 2007 15:31, Eric Paris wrote:
On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
On Dec 19 2007 16:59, Eric Paris wrote:
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to protect
On Dec 21 2007 22:16, Willy Tarreau wrote:
Hi Jan,
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to protect from user allocation
Hm, should not this be 'hex'?
I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
base 10 as well
sysfs is
On Fri, Dec 21, 2007 at 11:04:19PM +0100, Jan Engelhardt wrote:
On Dec 21 2007 22:16, Willy Tarreau wrote:
Hi Jan,
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to protect from user allocation
Hm, should not this be 'hex'?
I guess it could be, but
On Dec 19 2007 16:59, Eric Paris wrote:
>
>+config SECURITY_DEFAULT_MMAP_MIN_ADDR
>+int "Low address space to protect from user allocation"
Hm, should not this be 'hex'?
>+depends on SECURITY
>+default 0
>+help
--
To unsubscribe from this list: send the line
Since it was decided that low memory protection from userspace couldn't
be turned on by default add a Kconfig option to allow users/distros to
set a default at compile time. This value is still tunable after boot
in /proc/sys/vm/mmap_min_addr
Signed-off-by: Eric Paris <[EMAIL PROTECTED]>
---
Since it was decided that low memory protection from userspace couldn't
be turned on by default add a Kconfig option to allow users/distros to
set a default at compile time. This value is still tunable after boot
in /proc/sys/vm/mmap_min_addr
Signed-off-by: Eric Paris [EMAIL PROTECTED]
---
On Dec 19 2007 16:59, Eric Paris wrote:
+config SECURITY_DEFAULT_MMAP_MIN_ADDR
+int Low address space to protect from user allocation
Hm, should not this be 'hex'?
+depends on SECURITY
+default 0
+help
--
To unsubscribe from this list: send the line unsubscribe
24 matches
Mail list logo