On Thu, 2013-11-14 at 17:38 +0000, Thorsten Glaser wrote: > Dixi quod… > > >Ben Hutchings dixit: > > > >>> One’s to add back CONFIG_BRK which is apparently needed to run a > >>> popular ramdisk image used e.g. when testing the hardware or setting > >>> up a completely new system. > >> > >>You mean CONFIG_COMPAT_BRK. I don't like this but I doubt anyone cares > >>to write exploits for m68k any more. > > > >Oh sorry, yes I do. I understand why you’d not like it, but the > > We could set /proc/sys/kernel/randomize_va_space to 2 in the > Debian initrd (am I correct in assuming I have to file a wishlist > bug against initramfs-tools for that?) to mitigate the effects > of this while still keeping the desired compatibility with old > rootfs/initrd images that require this option? I am quite confident this would not be added to initramfs-tools. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth
Attachment:
signature.asc
Description: This is a digitally signed message part