diff options
| author | Ruud van Asseldonk <dev@veniogames.com> | 2019-08-10 22:07:59 +0200 |
|---|---|---|
| committer | Ruud van Asseldonk <dev@veniogames.com> | 2019-08-10 22:21:57 +0200 |
| commit | 8b6a9202e7fb543d948efc20ff478d362665b945 (patch) | |
| tree | 3b7ebcf9d1bfb35d72be0330231833bf97e5cef1 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 809b38a784ea413b36d188688eb1d2318e6438da (diff) | |
libressl: build libcrypto with noexecstack
For some reasons, libcrypto would be built with the executable stack
flag set. I found out about this when Nginx failed to load the shared
library, because I was running it with MemoryDenyWriteExecute=true,
which does not permit executable stacks.
I am not sure why the stack ends up executable; the other shared
libraries which are part of LibreSSL do not have this flag set. You can
verify this with 'execstack -q'. Non-executable stacks should be the
default, and from checking some other files, that does appear to be the
case. The LibreSSL sources do not contain the string "execstack", so
I am not sure what causes the default to be overridden.
Adding '-z noexecstack' to the linker flags makes the linker unset the
flag. Now my Nginx can load the library, and so far I have not run into
other issues.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
