From 7a2b64e55c7d57707f4d1ed54ee21bf69d0d0d16 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 20 Nov 2017 17:29:54 +0100 Subject: binary-cache-public-keys -> trusted-public-keys The name had become a misnomer since it's not only for substitution from binary caches, but when adding/copying any (non-content-addressed) path to a store. --- doc/manual/command-ref/conf-file.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/manual/command-ref/conf-file.xml b/doc/manual/command-ref/conf-file.xml index fb4d8cefc..a28f70899 100644 --- a/doc/manual/command-ref/conf-file.xml +++ b/doc/manual/command-ref/conf-file.xml @@ -406,17 +406,17 @@ false. If set to * (the default), Nix will only download binaries if they are signed using one of the - keys listed in . Set to + keys listed in . Set to the empty string to disable signature checking. - binary-cache-public-keys + trusted-public-keys - A whitespace-separated list of public keys - corresponding to the secret keys trusted to sign binary - caches. For example: + A whitespace-separated list of public keys. When + paths are copied from another Nix store (such as a binary cache), + they must be signed with one of these keys. For example: cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= hydra.nixos.org-1:CNHJZBh9K4tP3EKF6FkkgeVYsS3ohTl+oS0Qa8bezVs=. -- cgit v1.2.3