Date: | Fri, 3 Jan 2014 00:01:55 -0500 |
From: | Nalin Dahyabhai <nalin@redhat.com> |
To: | krb5-bugs@mit.edu |
Subject: | AES-NI support in 1.12 and executable stacks |
I just recently tweaked the build of 1.12 for our development branch to
take advantage of the new AES-NI support, but overlooked that by
default, the assembler-generated object files don't include an empty
.note.GNU-stack section.
When the linker goes to include them into the libk5crypto shared
library, the resulting library is marked as needing its stack to be set
executable, and that trips various protections implemented elsewhere.
Dhiru Kholia was kind enough to supply a candidate patch which adds the
section in a bug report [1]; I'm attaching it.
Thanks,
Nalin
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1045699
take advantage of the new AES-NI support, but overlooked that by
default, the assembler-generated object files don't include an empty
.note.GNU-stack section.
When the linker goes to include them into the libk5crypto shared
library, the resulting library is marked as needing its stack to be set
executable, and that trips various protections implemented elsewhere.
Dhiru Kholia was kind enough to supply a candidate patch which adds the
section in a bug report [1]; I'm attaching it.
Thanks,
Nalin
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1045699
Message body is not shown because sender requested not to inline it.