about summary refs log tree commit diff
path: root/src/rt/rust_task.cpp
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2013-06-14 15:43:02 -0400
committerDaniel Micay <danielmicay@gmail.com>2013-06-15 18:17:24 -0400
commit708395d65d689080cc96dd091adab3fc4c5c3f27 (patch)
tree1533da55ac8f95dfcdbddb2ff9f8893df5edbbb7 /src/rt/rust_task.cpp
parenteadd83da8b9abc821b141195503836b2094a9ea3 (diff)
downloadrust-708395d65d689080cc96dd091adab3fc4c5c3f27.tar.gz
rust-708395d65d689080cc96dd091adab3fc4c5c3f27.zip
stop using an absolute rpath
This is a bad default, because the binaries will point at an absolute
path regardless of where they are moved. This opens up a security issue
for packages, because they will attempt to load libraries from a path
that's often owned by a regular user.

Every Rust binary is currently flagged by Debian, Fedora and Arch lint
checkers as having dangerous rpaths. They don't meet the requirements to
be placed in the repositories without manually stripping this from each
binary.

The relative rpath is still enough to keep the binaries working until
they are moved relative to the crates they're linked against.

http://wiki.debian.org/RpathIssue
https://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath
Diffstat (limited to 'src/rt/rust_task.cpp')
0 files changed, 0 insertions, 0 deletions