# # # patch "NEWS" # from [a552479773f4a0de26f6656074ba186228026bb3] # to [96c19509ba229e847b71ccf0c613d00fc433208f] # # patch "monotone.texi" # from [8504336b15f2b2d74fd2641960d073f537eec980] # to [3c3023cecc04d9c9ff4399d63fc81f51668e9f2b] # ============================================================ --- NEWS a552479773f4a0de26f6656074ba186228026bb3 +++ NEWS 96c19509ba229e847b71ccf0c613d00fc433208f @@ -1,3 +1,15 @@ +certs-by-keyhash branch: + 'trusted' requires the given keys to exist + 'ls certs' and 'ls tags' give the first part of the key hash + monotone can now handle multiple keys with the same name + 'automate keys' output has changed + 'automate certs' output lists keys by hash instead of by name + netsync version has been bumped + 'db migrate' is required. Everyone can do this themselved; there's no + need for a project leader to migrate and everyone else to pull + a fresh database + the automate major version needs to be bumped + ??? ?? ?? ??:??:?? UTC ???? 0.45 release. ============================================================ --- monotone.texi 8504336b15f2b2d74fd2641960d073f537eec980 +++ monotone.texi 3c3023cecc04d9c9ff4399d63fc81f51668e9f2b @@ -5586,7 +5586,7 @@ @section Informative @item Whether the signature on the certificate is @code{ok} or @code{bad} @item -The key ID of the signer of the certificate +The key used to sign the certificate @item The name of the certificate @item @@ -5603,22 +5603,22 @@ @section Informative mtn: expanding partial id '4a96' mtn: expanded to '4a96a230293456baa9c6e7167cafb3c5b52a8e7f' ----------------------------------------------------------------- -Key : graydon@@pobox.com +Key : graydon@@pobox.com (10b5b36b4a...) Sig : ok Name : author Value : graydon@@dub.venge.net ----------------------------------------------------------------- -Key : graydon@@pobox.com +Key : graydon@@pobox.com (10b5b36b4a...) Sig : ok Name : branch Value : monotone ----------------------------------------------------------------- -Key : graydon@@pobox.com +Key : graydon@@pobox.com (10b5b36b4a...) Sig : ok Name : date Value : 2003-10-17T03:20:27 ----------------------------------------------------------------- -Key : graydon@@pobox.com +Key : graydon@@pobox.com (10b5b36b4a...) Sig : ok Name : changelog Value : 2003-10-16 graydon hoare @@ -5818,10 +5818,12 @@ @section Key and Cert Trust This command lets you test your revision trust hook @code{get_revision_cert_trust} (see @ref{Hook Reference}). You pass it a revision ID, a certificate name, a certificate value, and one or more -key IDs, and it will tell you whether, under your current settings, +key IDs or key names, and it will tell you whether, under your current settings, Monotone would trust a cert on that revision with that value signed by those keys. +The specified keys mist exist either in your keystore or in the database. + @item mtn ssh_agent_add This command will add your monotone keys to your current ssh-agent session. @@ -7527,6 +7529,12 @@ @section Automation 1.0 address@hidden Changes: address@hidden address@hidden +FIXME -- Keys are now listed by hash instead of name. address@hidden itemize + @item Purpose: Prints all certificates associated with the given revision ID. @@ -7534,7 +7542,7 @@ @section Automation the following values are provided: @verbatim 'key' - a string indicating the key used to sign this certificate. + the hex-encoded hash of the key used to sign this certificate. 'signature' a string indicating the status of the signature. Possible values of this string are: @@ -7555,19 +7563,19 @@ @section Automation @item Sample output: @verbatim - key "address@hidden" + key [5cd3b3a7ad2e8645e8887af193ee522dc59112e4] signature "ok" name "author" value "address@hidden" trust "trusted" - key "address@hidden" + key [5cd3b3a7ad2e8645e8887af193ee522dc59112e4] signature "ok" name "branch" value "net.venge.monotone" trust "trusted" - key "address@hidden" + key [5cd3b3a7ad2e8645e8887af193ee522dc59112e4] signature "ok" name "changelog" value "propagate from branch 'net.venge.monotone.annotate' (head 76a886ef7c8ae12a4bba5fc2bd252557bf863aff) @@ -7575,7 +7583,7 @@ @section Automation " trust "trusted" - key "address@hidden" + key [5cd3b3a7ad2e8645e8887af193ee522dc59112e4] signature "ok" name "date" value "2005-05-20T20:19:25" @@ -8468,6 +8476,9 @@ @section Automation @itemize @item +FIXME -- Instead of having a "name" item, there are +"given_name" and "local_name" items. address@hidden 10.0 -- The separate hashes for the private half of a key really didn't make much sense; have one @code{hash [...]} line instead of separate @code{public_hash [...]} and @code{private_hash [...]} lines. @@ -8483,17 +8494,20 @@ @section Automation @item Sample output: @verbatim - name "address@hidden" hash [475055ec71ad48f5dfaf875b0fea597b5cbbee64] + given_name "address@hidden" + local_name "address@hidden" public_location "database" "keystore" private_location "keystore" - name "address@hidden" hash [3ac4afcd86af28413b0a23b7d22b9401e15027fc] + given_name "address@hidden" + local_name "address@hidden" public_location "database" - name "address@hidden" hash [115fdc73d87a5e9901d018462b21a1f53eca33a1] + given_name "address@hidden" + local_name "address@hidden" public_location "keystore" private_location "keystore" @@ -8502,10 +8516,14 @@ @section Automation @item Output format: For each key, a basic_io stanza is printed. The public_location and -private_location items may have multiple values as shown above for public_location, one value for each place that the key is stored. If the +private_location items may have multiple values as shown above for public_location, +one value for each place that the key is stored. If the private key does not exist, then the private_hash and private_location -items will be absent. The keys are ordered alphabetically by name. +items will be absent. given_name is the name provided when the key was created, +and local_name is the name returned by the @code{get_local_key_name} hook. +The keys are ordered by hash value. + @item Error conditions: None.