GPG with mutt not working
Is anybody using Gentoo? I cannot get GPG to work with mutt. It used to work not I don't see any menu to sign / view/ decrypt/ encrypt the message GPG is compiled IN mail-client/mutt-1.5.21-r1 USE=crypt gdbm gpg nls pop sidebar ssl -berkdb -debug -doc -gnutls -idn -imap -mbox -nntp -qdbm -sasl -smime -smtp -tokyocabinet 0 kB -- Joseph
Re: GPG with mutt not working
* On 25 May 2011, Joseph wrote: Is anybody using Gentoo? I cannot get GPG to work with mutt. It used to work not I don't see any menu to sign / view/ decrypt/ encrypt the message GPG is compiled IN mail-client/mutt-1.5.21-r1 USE=crypt gdbm gpg nls pop sidebar ssl -berkdb -debug -doc -gnutls -idn -imap -mbox -nntp -qdbm -sasl -smime -smtp -tokyocabinet 0 kB Could you post your 'mutt -v' output as well? I don't want to make any assumptions about what an emerge does. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago
Re: GPG with mutt not working
On 05/25/11 15:49, David Champion wrote: * On 25 May 2011, Joseph wrote: Is anybody using Gentoo? I cannot get GPG to work with mutt. It used to work not I don't see any menu to sign / view/ decrypt/ encrypt the message GPG is compiled IN mail-client/mutt-1.5.21-r1 USE=crypt gdbm gpg nls pop sidebar ssl -berkdb -debug -doc -gnutls -idn -imap -mbox -nntp -qdbm -sasl -smime -smtp -tokyocabinet 0 kB Could you post your 'mutt -v' output as well? I don't want to make any assumptions about what an emerge does. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago mutt -v Mutt 1.5.21 (2010-09-15, Gentoo 1.5.21-r1) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.6.36-gentoo-r5 (x86_64) ncurses: ncurses 5.7.20081102 (compiled with 5.7) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Jan 22 2010 20:58:12) Compile options: -DOMAIN -DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP -USE_NNTP -USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=Maildir PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc/mutt EXECSHELL=/bin/sh MIXMASTER=mixmaster To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. sidebar dgc.subjrx fg.smarttime vvv.initials vvv.quote vvv.nntp patch-1.5.20hg.pdmef.progress.vl.2 rr.compressed patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf lukas@lpr.ch -- Joseph
Re: GPG with mutt not working
On 05/25/11 15:50, Joseph wrote: On 05/25/11 15:49, David Champion wrote: * On 25 May 2011, Joseph wrote: Is anybody using Gentoo? I cannot get GPG to work with mutt. It used to work not I don't see any menu to sign / view/ decrypt/ encrypt the message GPG is compiled IN mail-client/mutt-1.5.21-r1 USE=crypt gdbm gpg nls pop sidebar ssl -berkdb -debug -doc -gnutls -idn -imap -mbox -nntp -qdbm -sasl -smime -smtp -tokyocabinet 0 kB Could you post your 'mutt -v' output as well? I don't want to make any assumptions about what an emerge does. Could the problem be with gnupg? I'm using ver. gnupg-2.0.17 -- Joseph
Re: GPG with mutt not working
On Wed, May 25, 2011 at 03:50:12PM -0600, Joseph wrote: On 05/25/11 15:49, David Champion wrote: * On 25 May 2011, Joseph wrote: Is anybody using Gentoo? I cannot get GPG to work with mutt. For what it's worth, I use mutt+gpg under Gentoo, and it's working fine for me. Which at least suggests that the issue isn't Gentoo. Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org
Re: GPG with mutt not working
On 05/26/11 00:17, Toby Cubitt wrote: On Wed, May 25, 2011 at 03:50:12PM -0600, Joseph wrote: On 05/25/11 15:49, David Champion wrote: * On 25 May 2011, Joseph wrote: Is anybody using Gentoo? I cannot get GPG to work with mutt. For what it's worth, I use mutt+gpg under Gentoo, and it's working fine for me. Which at least suggests that the issue isn't Gentoo. Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org What version of gnupg and mutt are you using? I have mutt-1.5.21-r1 gnupg-2.0.17 -- Joseph
Re: GPG with mutt not working
* On 25 May 2011, Joseph wrote: +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS You have GPGME as well as classic pgp (i.e. forking off pgp/gpg commands) support. Is $crypt_use_gpgme set? If so, your classic settings are not used, and you're depending on gpgme. That doesn't explain why it's not working but it could explain why it quit working. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago
Re: GPG with mutt not working
On Wed, May 25, 2011 at 04:32:54PM -0600, Joseph wrote: On 05/26/11 00:17, Toby Cubitt wrote: On Wed, May 25, 2011 at 03:50:12PM -0600, Joseph wrote: On 05/25/11 15:49, David Champion wrote: * On 25 May 2011, Joseph wrote: Is anybody using Gentoo? I cannot get GPG to work with mutt. For what it's worth, I use mutt+gpg under Gentoo, and it's working fine for me. Which at least suggests that the issue isn't Gentoo. What version of gnupg and mutt are you using? I have mutt-1.5.21-r1 gnupg-2.0.17 Sorry, I should have said: gnupg-2.0.17 use flags: bzip2 nls mutt-1.5.21-r2 (but it was also working when I was using 1.5.21-r1) use flags: crypt doc mbox nls sidebar ssl tokyocabinet (For the record, I also apply a bunch of extra patches to mutt, that aren't included in the standard ebuild. But none of them have anything to do with encryption, signatures, or gpg, so they're almost certainly not relevant here.) HTH, Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org
Re: GPG with mutt not working
* Toby Cubitt ts...@cantab.net [2011-05-26 01:26]: What version of gnupg and mutt are you using? I have mutt-1.5.21-r1 gnupg-2.0.17 Sorry, I should have said: gnupg-2.0.17 use flags: bzip2 nls mutt-1.5.21-r2 (but it was also working when I was using 1.5.21-r1) use flags: crypt doc mbox nls sidebar ssl tokyocabinet (For the record, I also apply a bunch of extra patches to mutt, that aren't included in the standard ebuild. But none of them have anything to do with encryption, signatures, or gpg, so they're almost certainly not relevant here.) Here it works also without any problems ... mutt- (berkdb crypt debug gdbm gpg imap mbox nls pop sasl smime smtp ssl -doc -gnutls -idn -qdbm -sidebar -tokyocabinet) gnupg-2.0.17-r (02:44:03 AM 04/21/2011)(bzip2 nls -adns -caps -doc -ldap -selinux -smartcard -static -usb) How do you implement GPG in your mutt config? Here is how I have configured it: a) mutt source ~/.mutt/gpgrc b) gnupg # %pThe empty string when no passphrase is needed, # the string PGPPASSFD=0 if one is needed. # # This is mostly used in conditional % sequences. # # %fMost PGP commands operate on a single file or a file # containing a message. %f expands to this file's name. # # %sWhen verifying signatures, there is another temporary file # containing the detached signature. %s expands to this # file's name. # # %aIn signing contexts, this expands to the value of the # configuration variable $pgp_sign_as. You probably need to # use this within a conditional % sequence. # # %rIn many contexts, mutt passes key IDs to pgp. %r expands to # a list of key IDs. # Note that we explicitly set the comment armor header since GnuPG, when used # in some localiaztion environments, generates 8bit data in that header, thereby # breaking PGP/MIME. # decode application/pgp set pgp_decode_command=/usr/bin/gpg --charset utf-8 --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f # verify a pgp/mime signature set pgp_verify_command=/usr/bin/gpg --status-fd=2 --no-verbose --quiet --batch --output - --verify %s %f # decrypt a pgp/mime attachment set pgp_decrypt_command=/usr/bin/gpg --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f # create a pgp/mime signed attachment # set pgp_sign_command=/usr/bin/gpg-2comp --comment '' --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f set pgp_sign_command=/usr/bin/gpg--no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --detach-sign --textmode %?a?-u %a? %f # create a application/pgp signed (old-style) message # set pgp_clearsign_command=/usr/bin/gpg-2comp --comment '' --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f set pgp_clearsign_command=/usr/bin/gpg --charset utf-8 --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --textmode --clearsign %?a?-u %a? %f # create a pgp/mime encrypted attachment # set pgp_encrypt_only_command=pgpewrap gpg-2comp -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f set pgp_encrypt_only_command=pgpewrap /usr/bin/gpg --charset utf-8--batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f # create a pgp/mime encrypted and signed attachment # set pgp_encrypt_sign_command=pgpewrap gpg-2comp --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f set pgp_encrypt_sign_command=pgpewrap /usr/bin/gpg --charset utf-8 %?p?--passphrase-fd 0? --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f # import a key into the public key ring set pgp_import_command=/usr/bin/gpg --no-verbose --import %f # export a key from the public key ring set pgp_export_command=/usr/bin/gpg --no-verbose --export --armor %r # verify a key set pgp_verify_key_command=/usr/bin/gpg --verbose --batch --fingerprint --check-sigs %r # read in the public key ring set pgp_list_pubring_command=/usr/bin/gpg --no-verbose --batch --quiet --with-colons --list-keys %r # read in the secret key ring set pgp_list_secring_command=/usr/bin/gpg --no-verbose --batch --quiet --with-colons --list-secret-keys %r # fetch keys #set pgp_getkeys_command=/usr/bin/gpg --recv-keys %r set pgp_getkeys_command= # pattern for good signature - may need to be adapted to locale! # set pgp_good_sign=^gpg: Good signature from # OK, here's a version which uses gnupg's message catalog: set pgp_good_sign=`gettext -d gnupg -s 'Good signature from ' | tr -d ''` # This version uses --status-fd messages # set pgp_good_sign=^\\[GNUPG:\\] GOODSIG pgp8tSSDKbgYx.pgp Description: PGP signature
Re: GPG with mutt not working
On 05/25/11 17:42, David Champion wrote: * On 25 May 2011, Joseph wrote: +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS You have GPGME as well as classic pgp (i.e. forking off pgp/gpg commands) support. Is $crypt_use_gpgme set? If so, your classic settings are not used, and you're depending on gpgme. That doesn't explain why it's not working but it could explain why it quit working. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago Thank for your input. Now, how do I get rid of one or the other: +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_GPGME 2.) How to check if crypt_use_gpgme is set? Do I put it in .muttrc ? -- Joseph
Re: GPG with mutt not working
I've copied your gpgrc to mine but it didn't do anything. Here is my pgp: muttrc: source ~/.mutt/pgp pgp: # decode application/pgp set pgp_decode_command=gpg --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f # verify a pgp/mime signature set pgp_verify_command=gpg --status-fd=2 --no-verbose --quiet --batch --output - --verify %s %f # decrypt a pgp/mime attachment set pgp_decrypt_command=gpg --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f # create a pgp/mime signed attachment # set pgp_sign_command=gpg-2comp --comment '' --no-verbose --batch --output - %?p?--passphrase-fd 0? --armor --detach-sign --textmode %?a?-u %a? %f set pgp_sign_command=gpg --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --detach-sign --textmode %?a?-u %a? %f # create a application/pgp signed (old-style) message # set pgp_clearsign_command=gpg-2comp --comment '' --no-verbose --batch --output - %?p?--passphrase-fd 0? --armor --textmode --clearsign %?a?-u %a? %f set pgp_clearsign_command=gpg --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --textmode --clearsign %?a?-u %a? %f # create a pgp/mime encrypted attachment # set pgp_encrypt_only_command=pgpewrap gpg-2comp -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f #new# set pgp_encrypt_only_command=pgpewrap gpg --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f set pgp_encrypt_only_command=pgpewrap gpg --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust --encrypt-to 0xED0E1FB7 -- -r %r -- %f # create a pgp/mime encrypted and signed attachment # set pgp_encrypt_sign_command=pgpewrap gpg-2comp %?p?--passphrase-fd 0? -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f #new# set pgp_encrypt_sign_command=pgpewrap gpg %?p?--passphrase-fd 0? --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f set pgp_encrypt_sign_command=pgpewrap gpg --passphrase-fd 0 --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust --encrypt-to 0xED0E1FB7 -- -r %r -- %f # import a key into the public key ring set pgp_import_command=gpg --no-verbose --import %f # export a key from the public key ring set pgp_export_command=gpg --no-verbose --export --armor %r # verify a key set pgp_verify_key_command=gpg --verbose --batch --fingerprint --check-sigs %r # read in the public key ring set pgp_list_pubring_command=gpg --no-verbose --batch --quiet --with-colons --list-keys %r # read in the secret key ring set pgp_list_secring_command=gpg --no-verbose --batch --quiet --with-colons --list-secret-keys %r # fetch keys # set pgp_getkeys_command=pkspxycwrap %r # pattern for good signature - may need to be adapted to locale! set pgp_good_sign=^gpgv?: Good signature from # OK, here's a version which uses gnupg's message catalog: # set pgp_good_sign=`gettext -d gnupg -s 'Good signature from ' | tr -d ''` # This version uses --status-fd messages # set pgp_good_sign=^\\[GNUPG:\\] GOODSIG # specify the uid to use when encrypting/signing #set pgp_sign_as=0xED0E1FB7 set crypt_use_gpgme # set pgp_auto_decode=yes # automatically verify the sign of a message when opened set crypt_verify_sig=ask-no #set crypt_verify_sig=yes set pgp_verify_sig=ask-no -- Joseph On 05/26/11 01:48, Stefan Wimmer wrote: * Toby Cubitt ts...@cantab.net [2011-05-26 01:26]: What version of gnupg and mutt are you using? I have mutt-1.5.21-r1 gnupg-2.0.17 Sorry, I should have said: gnupg-2.0.17 use flags: bzip2 nls mutt-1.5.21-r2 (but it was also working when I was using 1.5.21-r1) use flags: crypt doc mbox nls sidebar ssl tokyocabinet (For the record, I also apply a bunch of extra patches to mutt, that aren't included in the standard ebuild. But none of them have anything to do with encryption, signatures, or gpg, so they're almost certainly not relevant here.) Here it works also without any problems ... mutt- (berkdb crypt debug gdbm gpg imap mbox nls pop sasl smime smtp ssl -doc -gnutls -idn -qdbm -sidebar -tokyocabinet) gnupg-2.0.17-r (02:44:03 AM 04/21/2011)(bzip2 nls -adns -caps -doc -ldap -selinux -smartcard -static -usb) How do you implement GPG in your mutt config? Here is how I have configured it: a) mutt source ~/.mutt/gpgrc b) gnupg # %pThe empty string when no passphrase is needed, # the string PGPPASSFD=0 if one is needed. # # This is mostly used in conditional % sequences. # # %fMost PGP commands operate on a single file or a file # containing a message. %f expands to this file's name. # # %sWhen verifying signatures, there is another temporary file # containing the detached signature. %s expands to this # file's name. # # %aIn signing contexts, this expands to the value of the #
Re: GPG with mutt not working
* On 25 May 2011, Joseph wrote: On 05/25/11 17:42, David Champion wrote: * On 25 May 2011, Joseph wrote: +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS You have GPGME as well as classic pgp (i.e. forking off pgp/gpg commands) support. Is $crypt_use_gpgme set? If so, your classic settings are not used, and you're depending on gpgme. That doesn't explain why it's not working but it could explain why it quit working. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago Thank for your input. Now, how do I get rid of one or the other: +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_GPGME I don't know, that depends on your build environment. I have used gentoo too little to know how to change its ebuild. 2.) How to check if crypt_use_gpgme is set? Do I put it in .muttrc ? It is a muttrc variable. You can check its current value with: mutt -D | grep gpgme You can explicitly unset it in .muttrc with: unset crypt_use_gpgme That will disable the gpgme backend without requiring you to compile without it, allowing you to fall back to the classic backend. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago
Re: GPG with mutt not working
On 05/25/11 22:04, David Champion wrote: [snip] +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_GPGME I don't know, that depends on your build environment. I have used gentoo too little to know how to change its ebuild. These variable are set globally when I enable USE=gpg in Gentoo. 2.) How to check if crypt_use_gpgme is set? Do I put it in .muttrc ? It is a muttrc variable. You can check its current value with: mutt -D | grep gpgme I have it set IN but it make no difference on the outcome, no gpg for me in Mutt :-( -- Joseph
gpg with Mutt not working
Hello, I'd like to have gpg with --clearsign working in Mutt and the text to be in the message, not as an attachment. I tried all of these before sending an email, i for inline, c for clearsign, and s for sign. s does sign the message, but it puts the signature in an attachment. The others do nothing. I copied /usr/share/doc/mutt-1.5.18/gpg.rc and am using it in my mutt configuration. What could be the problem? Here is the configuration. # -*-muttrc-*- # # Command formats for gpg. # # This version uses gpg-2comp from # http://70t.de/download/gpg-2comp.tar.gz # # $Id$ # # %pThe empty string when no passphrase is needed, # the string PGPPASSFD=0 if one is needed. # # This is mostly used in conditional % sequences. # # %fMost PGP commands operate on a single file or a file # containing a message. %f expands to this file's name. # # %sWhen verifying signatures, there is another temporary file # containing the detached signature. %s expands to this # file's name. # # %aIn signing contexts, this expands to the value of the # configuration variable $pgp_sign_as. You probably need to # use this within a conditional % sequence. # # %rIn many contexts, mutt passes key IDs to pgp. %r expands to # a list of key IDs. # Note that we explicitly set the comment armor header since GnuPG, when used # in some localiaztion environments, generates 8bit data in that header, thereby # breaking PGP/MIME. # decode application/pgp set pgp_decode_command=gpg --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f # verify a pgp/mime signature set pgp_verify_command=gpg --status-fd=2 --no-verbose --quiet --batch --output - --verify %s %f # decrypt a pgp/mime attachment set pgp_decrypt_command=gpg --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f # create a pgp/mime signed attachment # set pgp_sign_command=gpg-2comp --comment '' --no-verbose --batch --output - %?p?--passphrase-fd 0? --armor --detach-sign --textmode %?a?-u %a? %f set pgp_sign_command=gpg --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --detach-sign --textmode %?a?-u %a? %f # create a application/pgp signed (old-style) message # set pgp_clearsign_command=gpg-2comp --comment '' --no-verbose --batch --output - %?p?--passphrase-fd 0? --armor --textmode --clearsign %?a?-u %a? %f set pgp_clearsign_command=gpg --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --textmode --clearsign %?a?-u %a? %f # create a pgp/mime encrypted attachment # set pgp_encrypt_only_command=pgpewrap gpg-2comp -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f set pgp_encrypt_only_command=pgpewrap gpg --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f # create a pgp/mime encrypted and signed attachment # set pgp_encrypt_sign_command=pgpewrap gpg-2comp %?p?--passphrase-fd 0? -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f set pgp_encrypt_sign_command=pgpewrap gpg %?p?--passphrase-fd 0? --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f # import a key into the public key ring set pgp_import_command=gpg --no-verbose --import %f # export a key from the public key ring set pgp_export_command=gpg --no-verbose --export --armor %r # verify a key set pgp_verify_key_command=gpg --verbose --batch --fingerprint --check-sigs %r # read in the public key ring set pgp_list_pubring_command=gpg --no-verbose --batch --quiet --with-colons --list-keys %r # read in the secret key ring set pgp_list_secring_command=gpg --no-verbose --batch --quiet --with-colons --list-secret-keys %r # fetch keys # set pgp_getkeys_command=pkspxycwrap %r # pattern for good signature - may need to be adapted to locale! # set pgp_good_sign=^gpgv?: Good signature from # OK, here's a version which uses gnupg's message catalog: # set pgp_good_sign=`gettext -d gnupg -s 'Good signature from ' | tr -d ''` # This version uses --status-fd messages set pgp_good_sign=^\\[GNUPG:\\] GOODSIG #set pgp_encryptself set pgp_replysign set pgp_verify_sig=yes
