On Fri, Apr 29, 2005 at 06:20:53AM -0700, Andrew Morton wrote:
> > application can only speak for itself so desabling should be on a per process
> > bias.
>
> You can disable randomization on a per-executable basis by setting an ELF
> personality. I forget the magic incantation. Arjan?
setarch -R
>
> > I can hardly imagine to publish a warning in the README such as:
> > This software only works if your Linux kernel is configured so that
> > /proc/sys/kernel/randomize_va_space = 0
> >
> > . second, my process restart succeeding roughly in 50% cases means that the
> > randomisation performed is just a toy. A virus assuming fixed memory layout
> > will still succeed 50% of times to install.
>
> Dunno.
It just means that half the time the old value was below the current
boundary, and half the time above. Eg half the time it was in free
space and you succeeded but left a gap, the other half there was a conflict.
Says nothing about the value of randomisation...
>
> > All in all, I'm not concerned about Linux kernel to randomise or not,
> > but I need to have a reliable way to request a memory region and be granted
> > that I can request the same one in a futur run.
> > What is the proper way to get such a memory area ?
>
> MAP_FIXED?
MAP_FIXED is generally a really bad idea though.
-
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/
[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]
