2011-10-11 00:11:08 +03:00
|
|
|
|
package Nix::Config;
|
|
|
|
|
|
2013-11-25 18:38:33 +02:00
|
|
|
|
$version = "@PACKAGE_VERSION@";
|
2012-07-12 01:05:30 +03:00
|
|
|
|
|
2011-10-11 00:11:08 +03:00
|
|
|
|
$binDir = $ENV{"NIX_BIN_DIR"} || "@bindir@";
|
|
|
|
|
$libexecDir = $ENV{"NIX_LIBEXEC_DIR"} || "@libexecdir@";
|
2012-01-03 03:51:38 +02:00
|
|
|
|
$stateDir = $ENV{"NIX_STATE_DIR"} || "@localstatedir@/nix";
|
2011-10-11 00:11:08 +03:00
|
|
|
|
$manifestDir = $ENV{"NIX_MANIFESTS_DIR"} || "@localstatedir@/nix/manifests";
|
|
|
|
|
$logDir = $ENV{"NIX_LOG_DIR"} || "@localstatedir@/log/nix";
|
2011-11-23 14:21:35 +02:00
|
|
|
|
$confDir = $ENV{"NIX_CONF_DIR"} || "@sysconfdir@/nix";
|
2012-06-30 01:28:52 +03:00
|
|
|
|
$storeDir = $ENV{"NIX_STORE_DIR"} || "@storedir@";
|
2011-10-11 00:11:08 +03:00
|
|
|
|
|
2012-06-29 21:26:31 +03:00
|
|
|
|
$bzip2 = "@bzip2@";
|
|
|
|
|
$xz = "@xz@";
|
2011-10-11 00:11:08 +03:00
|
|
|
|
$curl = "@curl@";
|
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
|
|
|
|
$openssl = "@openssl@";
|
2006-05-31 12:24:54 +03:00
|
|
|
|
|
2012-05-11 02:03:23 +03:00
|
|
|
|
$useBindings = "@perlbindings@" eq "yes";
|
|
|
|
|
|
2012-07-09 17:57:28 +03:00
|
|
|
|
%config = ();
|
|
|
|
|
|
2006-05-31 12:24:54 +03:00
|
|
|
|
sub readConfig {
|
2012-07-30 23:09:54 +03:00
|
|
|
|
if (defined $ENV{'_NIX_OPTIONS'}) {
|
|
|
|
|
foreach my $s (split '\n', $ENV{'_NIX_OPTIONS'}) {
|
|
|
|
|
my ($n, $v) = split '=', $s, 2;
|
|
|
|
|
$config{$n} = $v;
|
|
|
|
|
}
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-09 17:57:28 +03:00
|
|
|
|
my $config = "$confDir/nix.conf";
|
2006-05-31 12:24:54 +03:00
|
|
|
|
return unless -f $config;
|
2012-07-30 23:09:54 +03:00
|
|
|
|
|
2014-08-20 18:00:17 +03:00
|
|
|
|
open CONFIG, "<$config" or die "cannot open ‘$config’";
|
2006-05-31 12:24:54 +03:00
|
|
|
|
while (<CONFIG>) {
|
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
|
|
|
|
/^\s*([\w\-\.]+)\s*=\s*(.*)$/ or next;
|
2006-05-31 12:24:54 +03:00
|
|
|
|
$config{$1} = $2;
|
|
|
|
|
}
|
|
|
|
|
close CONFIG;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return 1;
|