lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 11 May 2007 15:41:18 -0700
From:	"Ulrich Drepper" <>
To:	"Andrew Morton" <>
Cc:	"Jiri Kosina" <>, "Jan Kratochvil" <>,
	"Ingo Molnar" <>,
Subject: Re: [PATCH][RESEND] PIE randomization

On 5/11/07, Andrew Morton <> wrote:
> erm, I was being funny.  If you randomize a binary it won't run any more.
> cp /dev/random /bin/login.  Oh well.
> My point is, we're not being told what is being randomized here.  Is it the
> virtual starting address of the main executable mmap?  Of the shared
> libraries also?  Is it the stack location?  What?

PIE = Position Independent Executable, that's how I named them.

These are not regular executables, they are basically DSOs but usually
compiled with -fpie/-fPIE instead of -fpic/-fPIC and linked with -pie
instead of -shared to allow the compiled and linker perform more

See section 5 in

Jan unfortunately Ingo's document which doesn't really explain it.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists