aboutsummaryrefslogtreecommitdiff
path: root/gnupg/gpg.conf.mi5
Commit message (Collapse)AuthorAgeFilesLines
* Allow specifying GnuPG --keyid-format at buildTom Ryder2017-12-291-1/+1
| | | | | Old versions of gpg(1) don't support "none" as a --keyid-format; allow specifying it as a Makefile variable KEYID_FORMAT.
* Use only fingerprints for GnuPG keysTom Ryder2017-12-291-2/+2
| | | | The manual page for gpg(1) says this is the safest way to do it.
* Remove --batch option and wrapper for gpg(1)Tom Ryder2017-12-291-5/+0
| | | | | | | | This was originally added to cut the decryption boilerplate, which no longer seems to be an issue; I think that --quiet may be correctly blocking it now. Even without this, it caused more problems than it solved when gpg(1) genuinely did need user interaction from me, for example for --update-trustdb.
* Remove deprecated keyserver optionsTom Ryder2017-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | > gpg: keyserver option 'check-cert' is obsolete > gpg: keyserver option 'ca-certfile' is unknown > gpg (GnuPG) 2.1.18 > libgcrypt 1.7.6-beta > Copyright (C) 2017 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > > Home: /home/tom/.gnupg > Supported algorithms: > Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA > Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, > CAMELLIA128, CAMELLIA192, CAMELLIA256 > Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 > Compression: Uncompressed, ZIP, ZLIB, BZIP2
* Refactor m4 macro namesTom Ryder2017-06-131-2/+2
| | | | mi5(1df) means I can simplify these quite a bit now
* Use mi5 to make templated shell scriptsTom Ryder2017-06-021-0/+52