lix -

Age	Commit message (Collapse)	Author
2022-09-22	Dodge "trusted" vs "trustworthy" by being explicit	John Ericson
	Hopefully this is best!
2022-09-22	"valid signature" -> "trustworthy signature"	John Ericson
	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.
2021-01-13	Rename 'nix store sign-paths' to 'nix store sign'	Eelco Dolstra

2020-12-03	Move most store-related commands to 'nix store'	Eelco Dolstra

2018-09-25	Add a test for signed content-addressed paths	Will Fancher

2017-12-07	Fix test	Eelco Dolstra

2017-11-20	Add tests for verifying/copying content-addressed paths	Eelco Dolstra
	These don't require signatures.
2017-11-20	Add tests for signature checking when copying between local stores	Eelco Dolstra

2017-11-20	binary-cache-public-keys -> trusted-public-keys	Eelco Dolstra
	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.
2017-11-14	nix sign-paths: Support binary caches	Eelco Dolstra

2017-11-14	Add tests for "nix verify", "nix sign-paths" etc.	Eelco Dolstra