2012-07-27 00:13:14 +03:00
|
|
|
source common.sh
|
|
|
|
|
|
|
|
|
|
clearStore
|
2012-09-12 18:29:10 +03:00
|
|
|
clearManifests
|
2014-02-17 13:22:50 +02:00
|
|
|
clearCache
|
2012-07-27 00:13:14 +03:00
|
|
|
|
2012-07-27 21:15:03 +03:00
|
|
|
# Create the binary cache.
|
2012-07-27 00:13:14 +03:00
|
|
|
outPath=$(nix-build dependencies.nix --no-out-link)
|
|
|
|
|
|
|
|
|
|
nix-push --dest $cacheDir $outPath
|
|
|
|
|
|
2012-07-28 01:16:05 +03:00
|
|
|
|
|
|
|
|
# By default, a binary cache doesn't support "nix-env -qas", but does
|
|
|
|
|
# support installation.
|
2012-07-27 00:13:14 +03:00
|
|
|
clearStore
|
|
|
|
|
rm -f $NIX_STATE_DIR/binary-cache*
|
|
|
|
|
|
2013-04-23 13:43:28 +03:00
|
|
|
export _NIX_CACHE_FILE_URLS=1
|
|
|
|
|
|
2012-07-31 00:09:13 +03:00
|
|
|
nix-env --option binary-caches "file://$cacheDir" -f dependencies.nix -qas \* | grep -- "---"
|
2012-07-28 01:16:05 +03:00
|
|
|
|
2012-07-31 00:09:13 +03:00
|
|
|
nix-store --option binary-caches "file://$cacheDir" -r $outPath
|
2012-07-28 01:16:05 +03:00
|
|
|
|
2014-02-26 19:59:01 +02:00
|
|
|
[ -x $outPath/program ]
|
|
|
|
|
|
2012-07-28 01:16:05 +03:00
|
|
|
|
|
|
|
|
# But with the right configuration, "nix-env -qas" should also work.
|
|
|
|
|
clearStore
|
|
|
|
|
rm -f $NIX_STATE_DIR/binary-cache*
|
|
|
|
|
echo "WantMassQuery: 1" >> $cacheDir/nix-cache-info
|
|
|
|
|
|
2012-07-31 00:09:13 +03:00
|
|
|
nix-env --option binary-caches "file://$cacheDir" -f dependencies.nix -qas \* | grep -- "--S"
|
2012-07-27 21:15:03 +03:00
|
|
|
|
2012-12-03 22:02:06 +02:00
|
|
|
x=$(nix-env -f dependencies.nix -qas \* --prebuilt-only)
|
|
|
|
|
[ -z "$x" ]
|
|
|
|
|
|
2012-07-31 00:09:13 +03:00
|
|
|
nix-store --option binary-caches "file://$cacheDir" -r $outPath
|
2012-07-27 00:13:14 +03:00
|
|
|
|
|
|
|
|
nix-store --check-validity $outPath
|
|
|
|
|
nix-store -qR $outPath | grep input-2
|
2012-07-28 01:16:05 +03:00
|
|
|
|
2013-01-02 12:45:23 +02:00
|
|
|
|
2014-01-08 18:56:30 +02:00
|
|
|
# Test whether Nix notices if the NAR doesn't match the hash in the NAR info.
|
|
|
|
|
clearStore
|
|
|
|
|
|
|
|
|
|
nar=$(ls $cacheDir/*.nar.xz | head -n1)
|
|
|
|
|
mv $nar $nar.good
|
|
|
|
|
mkdir -p $TEST_ROOT/empty
|
|
|
|
|
nix-store --dump $TEST_ROOT/empty | xz > $nar
|
|
|
|
|
|
|
|
|
|
nix-build --option binary-caches "file://$cacheDir" dependencies.nix -o $TEST_ROOT/result 2>&1 | tee $TEST_ROOT/log
|
|
|
|
|
grep -q "hash mismatch in downloaded path" $TEST_ROOT/log
|
|
|
|
|
|
|
|
|
|
mv $nar.good $nar
|
|
|
|
|
|
|
|
|
|
|
Support cryptographically signed binary caches
NAR info files in binary caches can now have a cryptographic signature
that Nix will verify before using the corresponding NAR file.
To create a private/public key pair for signing and verifying a binary
cache, do:
$ openssl genrsa -out ./cache-key.sec 2048
$ openssl rsa -in ./cache-key.sec -pubout > ./cache-key.pub
You should also come up with a symbolic name for the key, such as
"cache.example.org-1". This will be used by clients to look up the
public key. (It's a good idea to number keys, in case you ever need
to revoke/replace one.)
To create a binary cache signed with the private key:
$ nix-push --dest /path/to/binary-cache --key ./cache-key.sec --key-name cache.example.org-1
The public key (cache-key.pub) should be distributed to the clients.
They should have a nix.conf should contain something like:
signed-binary-caches = *
binary-cache-public-key-cache.example.org-1 = /path/to/cache-key.pub
If all works well, then if Nix fetches something from the signed
binary cache, you will see a message like:
*** Downloading ‘http://cache.example.org/nar/7dppcj5sc1nda7l54rjc0g5l1hamj09j-subversion-1.7.11’ (signed by ‘cache.example.org-1’) to ‘/nix/store/7dppcj5sc1nda7l54rjc0g5l1hamj09j-subversion-1.7.11’...
On the other hand, if the signature is wrong, you get a message like
NAR info file `http://cache.example.org/7dppcj5sc1nda7l54rjc0g5l1hamj09j.narinfo' has an invalid signature; ignoring
Signatures are implemented as a single line appended to the NAR info
file, which looks like this:
Signature: 1;cache.example.org-1;HQ9Xzyanq9iV...muQ==
Thus the signature has 3 fields: a version (currently "1"), the ID of
key, and the base64-encoded signature of the SHA-256 hash of the
contents of the NAR info file up to but not including the Signature
line.
Issue #75.
2014-01-08 16:23:41 +02:00
|
|
|
# Test whether this unsigned cache is rejected if the user requires signed caches.
|
|
|
|
|
clearStore
|
|
|
|
|
|
|
|
|
|
rm -f $NIX_STATE_DIR/binary-cache*
|
|
|
|
|
|
2014-01-08 18:56:58 +02:00
|
|
|
if nix-store --option binary-caches "file://$cacheDir" --option signed-binary-caches '*' -r $outPath; then
|
|
|
|
|
echo "unsigned binary cache incorrectly accepted"
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
Support cryptographically signed binary caches
NAR info files in binary caches can now have a cryptographic signature
that Nix will verify before using the corresponding NAR file.
To create a private/public key pair for signing and verifying a binary
cache, do:
$ openssl genrsa -out ./cache-key.sec 2048
$ openssl rsa -in ./cache-key.sec -pubout > ./cache-key.pub
You should also come up with a symbolic name for the key, such as
"cache.example.org-1". This will be used by clients to look up the
public key. (It's a good idea to number keys, in case you ever need
to revoke/replace one.)
To create a binary cache signed with the private key:
$ nix-push --dest /path/to/binary-cache --key ./cache-key.sec --key-name cache.example.org-1
The public key (cache-key.pub) should be distributed to the clients.
They should have a nix.conf should contain something like:
signed-binary-caches = *
binary-cache-public-key-cache.example.org-1 = /path/to/cache-key.pub
If all works well, then if Nix fetches something from the signed
binary cache, you will see a message like:
*** Downloading ‘http://cache.example.org/nar/7dppcj5sc1nda7l54rjc0g5l1hamj09j-subversion-1.7.11’ (signed by ‘cache.example.org-1’) to ‘/nix/store/7dppcj5sc1nda7l54rjc0g5l1hamj09j-subversion-1.7.11’...
On the other hand, if the signature is wrong, you get a message like
NAR info file `http://cache.example.org/7dppcj5sc1nda7l54rjc0g5l1hamj09j.narinfo' has an invalid signature; ignoring
Signatures are implemented as a single line appended to the NAR info
file, which looks like this:
Signature: 1;cache.example.org-1;HQ9Xzyanq9iV...muQ==
Thus the signature has 3 fields: a version (currently "1"), the ID of
key, and the base64-encoded signature of the SHA-256 hash of the
contents of the NAR info file up to but not including the Signature
line.
Issue #75.
2014-01-08 16:23:41 +02:00
|
|
|
|
|
|
|
|
|
2013-04-23 13:44:01 +03:00
|
|
|
# Test whether fallback works if we have cached info but the
|
|
|
|
|
# corresponding NAR has disappeared.
|
|
|
|
|
clearStore
|
|
|
|
|
|
|
|
|
|
nix-build --option binary-caches "file://$cacheDir" dependencies.nix --dry-run # get info
|
|
|
|
|
|
|
|
|
|
mkdir $cacheDir/tmp
|
2013-07-01 22:02:36 +03:00
|
|
|
mv $cacheDir/*.nar* $cacheDir/tmp/
|
2013-04-23 13:44:01 +03:00
|
|
|
|
|
|
|
|
NIX_DEBUG_SUBST=1 nix-build --option binary-caches "file://$cacheDir" dependencies.nix -o $TEST_ROOT/result --fallback
|
|
|
|
|
|
|
|
|
|
mv $cacheDir/tmp/* $cacheDir/
|
|
|
|
|
|
|
|
|
|
|
2013-01-02 12:45:23 +02:00
|
|
|
# Test whether building works if the binary cache contains an
|
|
|
|
|
# incomplete closure.
|
|
|
|
|
clearStore
|
|
|
|
|
|
|
|
|
|
rm $(grep -l "StorePath:.*dependencies-input-2" $cacheDir/*.narinfo)
|
|
|
|
|
|
2013-01-02 13:38:28 +02:00
|
|
|
nix-build --option binary-caches "file://$cacheDir" dependencies.nix -o $TEST_ROOT/result 2>&1 | tee $TEST_ROOT/log
|
|
|
|
|
grep -q "Downloading" $TEST_ROOT/log
|