qubes-mirage-firewall/build-with-docker.sh

#!/bin/sh
set -eu
echo Building Docker image with dependencies..
docker build -t qubes-mirage-firewall .
echo Building Firewall...
docker run --rm -i -v `pwd`:/home/opam/qubes-mirage-firewall qubes-mirage-firewall
echo "SHA2 of build:   $(sha256sum qubes_firewall.xen)"
echo "SHA2 last known: 5ee982b12fb3964e7d9e32ca74ce377ec068b3bbef2b6c86c131f8bb422a3134"
echo "(hashes should match for released versions)"
Add option to build with Docker 2017-01-09 11:45:16 -05:00			`#!/bin/sh`
Fix opam-repository commit for reproducible builds Also, display the actual and expected SHA hashes after building. 2017-01-28 08:44:21 -05:00			`set -eu`
			`echo Building Docker image with dependencies..`
Add option to build with Docker 2017-01-09 11:45:16 -05:00			`docker build -t qubes-mirage-firewall .`
Fix opam-repository commit for reproducible builds Also, display the actual and expected SHA hashes after building. 2017-01-28 08:44:21 -05:00			`echo Building Firewall...`
Add option to build with Docker 2017-01-09 11:45:16 -05:00			docker run --rm -i -v `pwd`:/home/opam/qubes-mirage-firewall qubes-mirage-firewall
Update to new mirage-nat API 2017-03-05 11:31:04 -05:00			`echo "SHA2 of build: $(sha256sum qubes_firewall.xen)"`
Combine Client_gateway and Firewall_uplink Before, we used Client_gateway for the IP address of the firewall on the client network and Firewall_uplink for its address on the uplink network. However, Qubes 4 uses the same IP address for both, so we can't separate these any longer, and there doesn't seem to be any advantage to keeping them separate anyway. 2019-05-16 14:18:31 -04:00			`echo "SHA2 last known: 5ee982b12fb3964e7d9e32ca74ce377ec068b3bbef2b6c86c131f8bb422a3134"`
Note that Git versions might have different hashes 2019-01-19 05:32:27 -05:00			`echo "(hashes should match for released versions)"`