2023-06-25 13:35:59 +02:00
|
|
|
|
# SPDX-FileCopyrightText: 1998 Free Software Foundation, Inc.
|
|
|
|
|
#
|
|
|
|
|
# SPDX-License-Identifier: GPL-3.0-or-later
|
|
|
|
|
#
|
2012-12-21 13:50:51 +01:00
|
|
|
|
# Options for GnuPG
|
|
|
|
|
# Copyright 1998, 1999, 2000, 2001, 2002, 2003,
|
|
|
|
|
# 2010 Free Software Foundation, Inc.
|
|
|
|
|
# This file is free software; as a special exception the author gives
|
|
|
|
|
# unlimited permission to copy and/or distribute it, with or without
|
|
|
|
|
# modifications, as long as this notice is preserved.
|
2023-02-21 18:08:54 +01:00
|
|
|
|
#
|
2012-12-21 13:50:51 +01:00
|
|
|
|
# This file is distributed in the hope that it will be useful, but
|
|
|
|
|
# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
|
|
|
|
|
# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
|
|
|
#
|
|
|
|
|
# Unless you specify which option file to use (with the command line
|
|
|
|
|
# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf
|
|
|
|
|
# by default.
|
|
|
|
|
#
|
|
|
|
|
# An options file can contain any long options which are available in
|
|
|
|
|
# GnuPG. If the first non white space character of a line is a '#',
|
|
|
|
|
# this line is ignored. Empty lines are also ignored.
|
|
|
|
|
#
|
|
|
|
|
# See the man page for a list of options.
|
|
|
|
|
|
2019-12-11 11:46:06 +01:00
|
|
|
|
# Use my key by default, trusted-key puts it to ultimate trust even if the
|
|
|
|
|
# private key is not present and default-recepient-self is not enough for
|
|
|
|
|
# gpg --encrypt -r
|
2020-03-13 18:25:17 +01:00
|
|
|
|
# default-key/encrypt-to take name according to `man gpg`
|
|
|
|
|
# NOTE! default-key is used instead of local-user as the latter cannot be
|
|
|
|
|
# overridden with flags (causing WTOP test to be signed with personal and
|
|
|
|
|
# WTOP keys)
|
2023-06-18 11:29:26 +02:00
|
|
|
|
default-key suomalainen@mikaela.info
|
2020-02-26 13:53:52 +01:00
|
|
|
|
# Has to be LONG key instead of fingerprint https://dev.gnupg.org/T4855
|
2023-06-18 11:29:26 +02:00
|
|
|
|
#trusted-key 0x99392F62BAE30723
|
|
|
|
|
# The above issue is resolved in 2.2.20
|
|
|
|
|
trusted-key 69FF455A869F9031A691E0F199392F62BAE30723
|
|
|
|
|
encrypt-to suomalainen@mikaela.info
|
2020-02-26 14:02:27 +01:00
|
|
|
|
# WTOP (see comments above)
|
2021-09-28 10:49:11 +02:00
|
|
|
|
#default-key mikaela+digitalents@mikaela.info
|
|
|
|
|
#trusted-key 0xDF046339D69EB8C9
|
|
|
|
|
#encrypt-to mikaela+digitalents@mikaela.info
|
2019-12-06 18:41:24 +01:00
|
|
|
|
|
2019-12-10 12:56:55 +01:00
|
|
|
|
# Ignore preferred keyserver and also import non-self-sigs
|
2023-06-18 11:43:18 +02:00
|
|
|
|
# WARNING! DoS hole!
|
|
|
|
|
keyserver-options no-honor-keyserver-url,no-self-sigs-only,no-import-clean,no-import-minimal
|
|
|
|
|
import-options no-self-sigs-only,no-import-clean,no-import-minimal
|
|
|
|
|
|
2019-12-06 19:22:32 +01:00
|
|
|
|
# The defaults are apparently self-sigs-only,import-clean starting from
|
2019-12-10 12:56:55 +01:00
|
|
|
|
# gpg 2.2.17, but there seem to be controversial views on them and I need
|
|
|
|
|
# some not-self-sigs with `--fetch-keys`
|
2019-12-06 19:22:32 +01:00
|
|
|
|
# Debian uses self-sigs-only (while I would be fine with import-clean)
|
|
|
|
|
# * https://dev.gnupg.org/T4628#128513
|
|
|
|
|
# Arch Linux reverts the change going by no-self-sigs-only,no-import-clean
|
|
|
|
|
# * https://bugs.archlinux.org/task/63147
|
2012-12-21 13:50:51 +01:00
|
|
|
|
|
2019-12-02 23:48:35 +01:00
|
|
|
|
# Try to automatically find keys from local/wkd if key for email address isn't found, but we are encrypting to email address.
|
2019-12-05 13:51:13 +01:00
|
|
|
|
auto-key-retrieve
|
2019-12-08 10:53:16 +01:00
|
|
|
|
auto-key-locate local,wkd,dane
|
2012-12-21 18:50:44 +01:00
|
|
|
|
|
2012-12-21 13:50:51 +01:00
|
|
|
|
# Encrypt to sender's key by default
|
|
|
|
|
default-recipient-self
|
|
|
|
|
|
|
|
|
|
# Use UTF-8 charset
|
|
|
|
|
charset UTF-8
|
2012-12-21 18:50:44 +01:00
|
|
|
|
display-charset utf-8
|
2012-12-21 13:50:51 +01:00
|
|
|
|
|
2018-09-18 20:37:28 +02:00
|
|
|
|
# use GPG Agent to avoid retyping passphrase very often.
|
2012-12-21 13:50:51 +01:00
|
|
|
|
use-agent
|
|
|
|
|
|
|
|
|
|
# Do everything in ASCII format by default instead of binary
|
|
|
|
|
armor
|
|
|
|
|
|
2012-12-22 15:43:34 +01:00
|
|
|
|
# Show the LONG KEYID and fingerprint by default and tell that it's hexadecimal string.
|
2012-12-21 13:50:51 +01:00
|
|
|
|
keyid-format 0xLONG
|
2012-12-22 15:43:34 +01:00
|
|
|
|
with-fingerprint
|
2019-12-06 19:55:58 +01:00
|
|
|
|
with-wkd-hash
|
2020-02-18 00:55:29 +01:00
|
|
|
|
with-keygrip
|
2012-12-21 13:50:51 +01:00
|
|
|
|
|
2019-12-07 18:02:23 +01:00
|
|
|
|
# I refuse to comment on GPG's weird scale how I have verified keys as
|
|
|
|
|
# I appear to disagree on the official meanings of 1-3.
|
|
|
|
|
# If I sign a key, I have verified it to best of my ability. Also
|
|
|
|
|
# apparently it doesn't have much meaning anyway https://debian-administration.org/users/dkg/weblog/98
|
|
|
|
|
no-ask-cert-level
|
|
|
|
|
default-cert-level 0
|
|
|
|
|
# Count also the persona signatures for WoT if someone has those.
|
|
|
|
|
min-cert-level 1
|
|
|
|
|
|
|
|
|
|
# Ask when signatures expire.
|
2013-01-17 15:48:48 +01:00
|
|
|
|
ask-cert-expire
|
2019-12-07 18:02:23 +01:00
|
|
|
|
default-cert-expire 2y
|
2013-01-17 15:48:48 +01:00
|
|
|
|
|
2013-02-26 11:18:20 +01:00
|
|
|
|
# Copying https://we.riseup.net/riseuplabs+paow/openpgp-best-practices#update-your-gpg-defaults
|
|
|
|
|
# when outputting certificates, view user IDs distinctly from keys:
|
|
|
|
|
fixed-list-mode
|
|
|
|
|
# You should always know at a glance which User IDs gpg thinks are legitimately bound to the keys in your keyring:
|
|
|
|
|
verify-options show-uid-validity
|
2020-02-10 22:29:03 +01:00
|
|
|
|
# Display calculated validity, which keyring the keys are from and when
|
|
|
|
|
# signatures expire
|
2020-03-11 13:57:22 +01:00
|
|
|
|
# Show URLs of signing policies when they exist
|
|
|
|
|
list-options show-uid-validity,show-keyring,show-sig-expire,show-policy-urls
|
2013-02-26 11:18:20 +01:00
|
|
|
|
|
2019-08-01 11:19:44 +02:00
|
|
|
|
# Disable comments
|
|
|
|
|
no-comments
|
2019-08-26 19:35:43 +02:00
|
|
|
|
|
|
|
|
|
# Don't output version, small chance of having people put same keys on IPFS
|
|
|
|
|
no-emit-version
|
|
|
|
|
|
2019-12-06 22:23:36 +01:00
|
|
|
|
# Trust On First Use (marginal trust) with WoT being full trust. I find this
|
|
|
|
|
# less annoying in KMail than only WoT or the comment below, and I think it
|
|
|
|
|
# may be additional motivation for me to actually sign the keys I trust with
|
|
|
|
|
# all keyservers hiding signatures and gpg not importing them.
|
|
|
|
|
# I think `keybase pgp pull` also helps here as the people I am tracking
|
|
|
|
|
# there are going to be in my keyring, however it's still a centralized
|
|
|
|
|
# service.
|
|
|
|
|
trust-model tofu+pgp
|
2020-01-30 19:21:31 +01:00
|
|
|
|
# WoT with TOFU’s conflict detection, but without positive trust. This may
|
|
|
|
|
# be better due to https://gitea.blesmrt.net/mikaela/pgp-alt-wot/ and lsign.
|
|
|
|
|
tofu-default-policy unknown
|