You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/03/05 00:23:40 UTC
[jira] [Commented] (TS-3938) Add hardening (fortify) as an option
to configure
[ https://issues.apache.org/jira/browse/TS-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180734#comment-15180734 ]
ASF subversion and git services commented on TS-3938:
-----------------------------------------------------
Commit 95b6f4750909fa6f770b22559d14c16e29f00ac1 in trafficserver's branch refs/heads/master from [~bcall]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=95b6f47 ]
TS-3938: Minor update to not echo the commands and added force to mv
> Add hardening (fortify) as an option to configure
> -------------------------------------------------
>
> Key: TS-3938
> URL: https://issues.apache.org/jira/browse/TS-3938
> Project: Traffic Server
> Issue Type: New Feature
> Components: Build
> Reporter: Leif Hedstrom
> Assignee: Bryan Call
> Fix For: sometime
>
>
> It might be useful to add an option, e.g. --with-hardening, such that we can build with various hardening compiler options. For example. I've used
> {code}
> CC="/opt/gcc5/bin/gcc"; export CC
> CXX="/opt/gcc5/bin/g++"; export CXX
> CFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CFLAGS
> CXXFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CXXFLAGS
> CPPFLAGS="-D_FORTIFY_SOURCE=2"; export CPPFLAGS
> LDFLAGS="-Wl,-z,relro -Wl,-z,now"; export LDFLAGS
> "./configure" \
> "--enable-experimental-plugins" \
> "--prefix=/opt/ats" \
> "CC=/opt/gcc5/bin/gcc" \
> "CXX=/opt/gcc5/bin/g++" \
> "CFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CXXFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CPPFLAGS=-D_FORTIFY_SOURCE=2" \
> "LDFLAGS=-Wl,-z,relro -Wl,-z,now" \
> "$@"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)