(and doesn't affect any non-linux platform anyway).
How come it turns from unsure "should be portable" to definitive
"doesn't affect" so easily:-)
Do mind smilies in my previous post:-)
What I tried to say was that the extra section is ignored on platforms that do
not use a recent binutils toolchain, which interpret this section
"magically".
I wouldn't hold my breath for this, as I'm rather concerned about
non-GNU tools failing to compile, than OS ELF image loader to ignore an
additional header. And indeed, Solaris 'as' for one miserably fails to
compile suggested .section directive...
But anyway. My vote goes to alternative method, which can be deployed as
easily as './config -Wa,--noexecstack' prior make. Because it can be
taylored to various needs/environments as easy as it can be deployed and
without headaches of cross-platform verification or running into subtle
bugs.
Works for me as well, its kind of a brute force hammer though. In any case the
real intention is to document that libcrypto *should* work fine without
executable stack
So one can as well call it "a distinguished way to make this statement
and document it," as the line will even appear in 'openssl version -a'
output and not some place nobody looks into:-)
and IMHO it should configure with non-executable stack by
default if the preconditions are met.
One can drop it into ./config... A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
