Changes between Version 1 and Version 2 of Ticket #12192, comment 3


Ignore:
Timestamp:
Jun 4, 2014, 4:08:03 PM (6 years ago)
Author:
strcat
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12192, comment 3

    v1 v2  
    11I'm the maintainer of linux-grsec in Arch Linux. Here's the downstream bug report: https://bugs.archlinux.org/task/40685
    22
    3 This isn't a bug in tor itself, so the issue here can be closed. At the moment, Arch Linux has a backported binutils patch causing every single PIE binary (even hello world) built with ld.bfd to conflict with the PaX MPROTECT mitigations. Passing `-fuse-ld=gold` in LDFLAGS is enough to work around this issue. Tor is one of the few packages going to the trouble of using PIE (which is great!) so that's why it occurred with this package.
     3This isn't a bug in tor itself, so the issue here can be closed. At the moment, Arch Linux has a backported binutils patch causing every single PIE binary (even hello world) built with ld.bfd to conflict with the PaX MPROTECT mitigations. Passing `-fuse-ld=gold` in LDFLAGS is enough to work around this issue. Tor is one of the few packages going to the trouble of using PIE (which is great!) so that's why it occurred with this package. Chromium is another project opting into PIE, but it already has an MPROTECT exception for the JavaScript VM and PNaCl.