diff options
| author | John Ericson <John.Ericson@Obsidian.Systems> | 2022-09-22 10:43:48 -0400 |
|---|---|---|
| committer | John Ericson <John.Ericson@Obsidian.Systems> | 2022-09-22 10:49:31 -0400 |
| commit | 752f967c0fe2489fe13d8c2c65c3ecba72064adc (patch) | |
| tree | bb0d0b462040fc6af61a90d41b3f48e04c21fd30 /src/nix/make-content-addressed.md | |
| parent | f704c2720f136a6bb73a2e91d4a85e0e9a42ff6f (diff) | |
"valid signature" -> "trustworthy signature"
I just had a colleague get confused by the previous phrase for good
reason. "valid" sounds like an *objective* criterion, e.g. and *invalid
signature* would be one that would be trusted by no one, e.g. because it
misformatted or something.
What is actually going is that there might be a signature which is
perfectly valid to *someone else*, but not to the user, because they
don't trust the corresponding public key. This is a *subjective*
criterion, because it depends on the arbitrary and personal choice of
which public keys to trust.
I therefore think "trustworthy" is a better adjective to use. Whether
something is worthy of trust is clearly subjective, and then "trust"
within that word nicely evokes `trusted-public-keys` and friends.
Diffstat (limited to 'src/nix/make-content-addressed.md')
| -rw-r--r-- | src/nix/make-content-addressed.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/nix/make-content-addressed.md b/src/nix/make-content-addressed.md index 215683e6d..b0685bb6c 100644 --- a/src/nix/make-content-addressed.md +++ b/src/nix/make-content-addressed.md @@ -22,7 +22,7 @@ R""( ```console # nix copy --to /tmp/nix --trusted-public-keys '' nixpkgs#hello - cannot add path '/nix/store/zy9wbxwcygrwnh8n2w9qbbcr6zk87m26-libunistring-0.9.10' because it lacks a valid signature + cannot add path '/nix/store/zy9wbxwcygrwnh8n2w9qbbcr6zk87m26-libunistring-0.9.10' because it lacks a trustworthy signature ``` * Create a content-addressed representation of the current NixOS |