aboutsummaryrefslogtreecommitdiffstats
path: root/common/stringhelp.c
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>2015-02-25 15:34:19 +0000
committerWerner Koch <[email protected]>2015-02-25 15:34:19 +0000
commit2fc27c8696f5cf2ddf3212397ea49bff115d617b (patch)
tree33ab4c13994e0201999a1793fd529965da32ab36 /common/stringhelp.c
parentcommon: Allow requesting a specific certtype with get_dns_cert() (diff)
downloadgnupg-2fc27c8696f5cf2ddf3212397ea49bff115d617b.tar.gz
gnupg-2fc27c8696f5cf2ddf3212397ea49bff115d617b.zip
gpg: Switch to a hash and CERT record based PKA system.
* common/dns-cert.c (get_dns_cert): Make r_key optional. * common/pka.c: Rewrite for the new hash based lookup. * common/t-pka.c: New. * configure.ac: Remove option --disable-dns-pka. (USE_DNS_PKA): Remove ac_define. * g10/getkey.c (parse_auto_key_locate): Always include PKA. -- Note that although PKA is now always build, it will only work if support for looking up via DNS has not been disabled. The new PKA only works with the IPGP DNS certtype and shall be used only to retrieve the fingerprint and optional the key for the first time. Due to the security problems with DNSSEC the former assumption to validate the key using DNSSEC is not anymore justified. Instead an additional layer (e.g. Trust-On-First-Use) needs to be implemented to track change to the key. Having a solid way of getting a key matching a mail address is however a must have. More work needs to go into a redefinition of the --verify-options pka-lookups and pka-trust-increase. The auto-key-locate mechanism should also be able to continue key fetching with another methods once the fingerprint has been retrieved with PKA. Signed-off-by: Werner Koch <[email protected]>
Diffstat (limited to 'common/stringhelp.c')
0 files changed, 0 insertions, 0 deletions