pkgsrc/mk/repro/ar

#!/bin/sh

PATH="$_PATH_ORIG"

if [ $# -ge 2 ]; then
	args="$1"
	mod="$2"
	shift 2

	exec ar "$mod$args" "$@"
else
	exec ar "$@"
fi
Add initial support for building packages reproducibly It currently tackles two problems: - gcc(1) hard-coding full paths in debugging information (with one caveat at the moment) - ar(1) hard-coding user IDs in archive headers This allows packages built from the same tree and options to produce identical results bit by bit. This option should be combined with ASLR and PKGSRC_MKPIE to avoid predictable address offsets for attackers attempting to exploit security vulnerabilities. This is still disabled by default, and only supports NetBSD so far. As discussed on tech-pkg@ 2017-11-12 14:34:14 +01:00			`#!/bin/sh`

Look for ar(1) in $_ORIG_PATH with PKGSRC_MKREPRO This no longer hard-codes the path to ar(1) as /usr/bin/ar. It is not possible to use the original value of $TOOLS_PATH.ar as it is usually not set. 2017-11-12 17:41:40 +01:00			`PATH="$_PATH_ORIG"`

Add initial support for building packages reproducibly It currently tackles two problems: - gcc(1) hard-coding full paths in debugging information (with one caveat at the moment) - ar(1) hard-coding user IDs in archive headers This allows packages built from the same tree and options to produce identical results bit by bit. This option should be combined with ASLR and PKGSRC_MKPIE to avoid predictable address offsets for attackers attempting to exploit security vulnerabilities. This is still disabled by default, and only supports NetBSD so far. As discussed on tech-pkg@ 2017-11-12 14:34:14 +01:00			`if [ $# -ge 2 ]; then`
			`args="$1"`
			`mod="$2"`
			`shift 2`

Look for ar(1) in $_ORIG_PATH with PKGSRC_MKREPRO This no longer hard-codes the path to ar(1) as /usr/bin/ar. It is not possible to use the original value of $TOOLS_PATH.ar as it is usually not set. 2017-11-12 17:41:40 +01:00			`exec ar "$mod$args" "$@"`
Add initial support for building packages reproducibly It currently tackles two problems: - gcc(1) hard-coding full paths in debugging information (with one caveat at the moment) - ar(1) hard-coding user IDs in archive headers This allows packages built from the same tree and options to produce identical results bit by bit. This option should be combined with ASLR and PKGSRC_MKPIE to avoid predictable address offsets for attackers attempting to exploit security vulnerabilities. This is still disabled by default, and only supports NetBSD so far. As discussed on tech-pkg@ 2017-11-12 14:34:14 +01:00			`else`
Look for ar(1) in $_ORIG_PATH with PKGSRC_MKREPRO This no longer hard-codes the path to ar(1) as /usr/bin/ar. It is not possible to use the original value of $TOOLS_PATH.ar as it is usually not set. 2017-11-12 17:41:40 +01:00			`exec ar "$@"`
Add initial support for building packages reproducibly It currently tackles two problems: - gcc(1) hard-coding full paths in debugging information (with one caveat at the moment) - ar(1) hard-coding user IDs in archive headers This allows packages built from the same tree and options to produce identical results bit by bit. This option should be combined with ASLR and PKGSRC_MKPIE to avoid predictable address offsets for attackers attempting to exploit security vulnerabilities. This is still disabled by default, and only supports NetBSD so far. As discussed on tech-pkg@ 2017-11-12 14:34:14 +01:00			`fi`