From 78b3e38915bbca43c0ff66d1d20c87e08ad0a8cb Mon Sep 17 00:00:00 2001 From: Tom Ryder Date: Fri, 29 Dec 2017 13:52:30 +1300 Subject: Use only fingerprints for GnuPG keys The manual page for gpg(1) says this is the safest way to do it. --- Makefile | 2 +- gnupg/gpg.conf.mi5 | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index d6f025b9..f5e78396 100644 --- a/Makefile +++ b/Makefile @@ -92,7 +92,7 @@ NAME = 'Tom Ryder' EMAIL = tom@sanctum.geek.nz -KEY = 0xC14286EA77BB8872 +KEY = FA09C06E1B670CD0B2F5DE60C14286EA77BB8872 SENDMAIL = msmtp BINS = bin/ap \ diff --git a/gnupg/gpg.conf.mi5 b/gnupg/gpg.conf.mi5 index 74363441..c3f80b7e 100644 --- a/gnupg/gpg.conf.mi5 +++ b/gnupg/gpg.conf.mi5 @@ -13,8 +13,8 @@ default-recipient-self # Show complete dates and use proper column separation for --with-colon listing mode fixed-list-mode -# Use 16-character key IDs as the default 8-character key IDs can be forged -keyid-format 0xlong +# Use only fingerprints as key IDs +keyid-format none # Use a pool of servers which support HKPS (encrypted key retrieval) keyserver <% KEYSERVER %> -- cgit v1.2.3