about summary refs log tree commit diff
path: root/src/librustdoc/markdown_pass.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-06-15 16:13:09 -0700
committerbors <bors@rust-lang.org>2013-06-15 16:13:09 -0700
commitc989b79127c5062df0a64d8c383de93c82a3d9b7 (patch)
tree3055673da5765574cac59582305a7b1aec37df3c /src/librustdoc/markdown_pass.rs
parent579c614e38303434bdb2926e192f69db041aec78 (diff)
parent708395d65d689080cc96dd091adab3fc4c5c3f27 (diff)
downloadrust-c989b79127c5062df0a64d8c383de93c82a3d9b7.tar.gz
rust-c989b79127c5062df0a64d8c383de93c82a3d9b7.zip
auto merge of #7132 : thestinger/rust/rpath, r=brson
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/librustdoc/markdown_pass.rs')
0 files changed, 0 insertions, 0 deletions