diff options
author | Werner Koch <wk@gnupg.org> | 2019-11-28 09:39:35 +0100 |
---|---|---|
committer | Werner Koch <wk@gnupg.org> | 2019-11-28 11:16:13 +0100 |
commit | 915297705af6f1db74dacf0d6665b83eb0a58459 (patch) | |
tree | 7e7cdc2f55f3d7d218a90f9eada3327a4dc534ff /doc | |
parent | dirmngr: Replace no-strict-overflow pragma by wrapv pragma. (diff) | |
download | gnupg2-915297705af6f1db74dacf0d6665b83eb0a58459.tar.xz gnupg2-915297705af6f1db74dacf0d6665b83eb0a58459.zip |
kbx: Redefine the UBID which is now the primary fingerprint.
* common/util.h (UBID_LEN): New. Use it at all places.
* kbx/keybox-blob.c (create_blob_finish): Do not write the UBID item.
* kbx/keybox-dump.c (print_ubib): Remove.
(_keybox_dump_blob): Do not print the now removed ubid flag.
* kbx/keybox-search-desc.h (struct keydb_search_desc): Use constants
for the size of the ubid and grip.
* kbx/keybox-search.c (blob_cmp_ubid): New.
(has_ubid): Make it a simple wrapper around blob_cmp_ubid.
(keybox_get_data): Add arg 'r_ubid'.
* kbx/frontend.h (enum kbxd_store_modes): New.
* kbx/kbxserver.c (cmd_store): Add new option --insert.
* kbx/backend-cache.c (be_cache_initialize): New.
(be_cache_add_resource): Call it here.
* kbx/backend-kbx.c (be_kbx_seek): Remove args 'fpr' and 'fprlen'.
(be_kbx_search): Get the UBID from keybox_get_data.
* kbx/backend-support.c (be_fingerprint_from_blob): Replace by ...
(be_ubid_from_blob): new. Change all callers.
* kbx/frontend.c (kbxd_add_resource): Temporary disable the cache but
use the new cache init function.
(kbxd_store): Replace arg 'only_update' by 'mode'. Seek using the
ubid. Take care of the mode.
--
It turned out that using the hash of the entire blob was not helpful.
Thus we redefine the Unique-Blob-ID (UBID) as the primary fingerprint
of the blob. In case this is a v5 OpenPGP key a left truncated
version of the SHA-256 hash is used; in all other cases the full SHA-1
hash. Using a SHA-256 hash does not make sense because v4 keys are
and will for some time be the majority of keys and thus padding them
with zeroes won't make any difference. Even if fingerprint collisions
can eventually be created we will assume that the keys are bogus and
that it does not make sense to store its twin also in our key storage.
We can also easily extend the update code to detect a collision and
reject the update.
Signed-off-by: Werner Koch <wk@gnupg.org>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/DETAILS | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/DETAILS b/doc/DETAILS index 6ce340e8c..bd00006e9 100644 --- a/doc/DETAILS +++ b/doc/DETAILS @@ -1152,11 +1152,10 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB: *** PUBKEY_INFO <n> <ubid> The type of the public key in the following D-lines or communicated via a pipe. <n> is the value of =enum pubkey_types= - and <ubid> the Unique Blob ID (UBID) which is a SHA-1 digest the - entire blob here formatted in hex. The consumer of this status - line should be prepared to see a <ubid> of up to 64 characters. - Note that the keyboxd SEARCH command can be used to lookup the - public key using the <ubid> prefixed with a caret (^). + and <ubid> the Unique Blob ID (UBID) which is the fingerprint of + the primary key truncated to 20 octets and formatted in hex. Note + that the keyboxd SEARCH command can be used to lookup the public + key using the <ubid> prefixed with a caret (^). * Format of the --attribute-fd output |