From gniibe at fsij.org Mon Sep 2 05:27:04 2013 From: gniibe at fsij.org (NIIBE Yutaka) Date: Mon, 02 Sep 2013 12:27:04 +0900 Subject: True RNG and GnuPG / libgcrypt (was: NeuG 0.11) In-Reply-To: <1377157444.3419.8.camel@cfw2.gniibe.org> References: <1377157444.3419.8.camel@cfw2.gniibe.org> Message-ID: <1378092424.3168.5.camel@cfw2.gniibe.org> I have a question about support of hardware RNG and GnuPG / libgcrypt. I develop NeuG, my own True RNG implementation. It is Free Software for embedded MCU, specifically, STM32F103. It is possible to use the routine as a standalone device, and free hardware design by me is also available. When I test (at least for each release), I collect 64GiB of output and test by NIST STS 2.1.1, Dieharder 3.31.1. Recently, it is also tested by PractRand 0.90. I don't know if it's good to address, but it is also tested by TestU01, too. (Note that TestU01 is not free software.) I think that the quality of random output is good enough. Currently, I use the output through the interface of /dev/random on GNU/Linux. There are two issues for me, now. (1) I don't find any method to feed entropy (for /dev/random) on *BSD system (2) It would be better for an application to use the standalone device directly, not through /dev/random Please let me know any related information about those issues. And... How do you think about supporting hardware RNG by GnuPG / libgcrypt? * * * FYI, here's the information about NeuG to /dev/random. Standalone device of NeuG can be used to feed entropy to /dev/random. I have following files for that: ============================== /etc/udev/rules.d/90-neug.rules KERNEL=="ttyACM[0-9]*", SUBSYSTEMS=="usb", ACTION=="add", \ ATTRS{idVendor}=="234b", ATTRS{idProduct}=="0001", \ RUN+="/etc/udev/ctrl_rng.sh" SUBSYSTEMS=="usb", ACTION=="remove", \ ATTRS{idVendor}=="234b", ATTRS{idProduct}=="0001", \ RUN+="/etc/udev/ctrl_rng.sh" ============================== ============================== /etc/udev/ctrl_rng.sh #! /bin/sh PIDFILE=/var/run/rngd.pid case "$ACTION" in add) stty -F $DEVNAME raw -echo -parenb /usr/sbin/rngd --fill-watermark=90% --feed-interval=1 --rng-device=$DEVNAME ;; remove) # This will be called twice, since there are two interfaces for the device. # Called once for 10/0/0, another for 2/2/1. if [ x$INTERFACE = x"2/2/1" -a -f $PIDFILE ]; then kill -SIGTERM `cat $PIDFILE` rm -f $PIDFILE else exit 0 fi ;; esac exit 0 ============================== That's for automatically connecting NeuG standalone device to RNGD, when plugged. -- From gniibe at fsij.org Mon Sep 2 06:07:44 2013 From: gniibe at fsij.org (NIIBE Yutaka) Date: Mon, 02 Sep 2013 13:07:44 +0900 Subject: True RNG and GnuPG / libgcrypt (was: NeuG 0.11) In-Reply-To: <1378092424.3168.5.camel@cfw2.gniibe.org> References: <1377157444.3419.8.camel@cfw2.gniibe.org> <1378092424.3168.5.camel@cfw2.gniibe.org> Message-ID: <1378094864.3168.7.camel@cfw2.gniibe.org> Replying to my own question: On 2013-09-02 at 12:27 +0900, NIIBE Yutaka wrote: > How do you think about supporting hardware RNG by GnuPG / libgcrypt? It seems that easiest way to support hardware RNG (without touching libgcrypt) is to use the EGD (Entropy Gathering Daemon) interface, and to write a helper daemon which accesses hardware RNG and provides its random data through the interface. -- From users.giulietta at gmail.com Tue Sep 3 22:53:54 2013 From: users.giulietta at gmail.com (Tone Kastlunger) Date: Tue, 3 Sep 2013 23:53:54 +0300 Subject: gpg-agent miscoordination on homedir Message-ID: Hi; apparently gpg-agent has indeed some issues with non-standard homedirs I have been trying to get gpg4win to work over gpgme; but passphrase dialog was not showing in my project and bad passphrase was always raised. It kept puzzling me until after alot of googling around I reached this: http://lists.gnupg.org/pipermail/gnupg-users/2012-April/044138.html Basically what I did in my project is to set a custom home directory via gpgme_ctx_set_engine_info; pre-starting the gpg-agent with the same argumes as the gpgme would PLUS the --homedir set to the same value passed to gpgme_ctx_set_engine_info fixed the issue and made the pass entry dialog show correctly. I think it might have something to do with the gpg-agent not finding the socket descriptor. Best, tortoisedoc -------------- next part -------------- An HTML attachment was scrubbed... URL: From users.giulietta at gmail.com Wed Sep 4 07:52:35 2013 From: users.giulietta at gmail.com (Tone Kastlunger) Date: Wed, 4 Sep 2013 08:52:35 +0300 Subject: gpg-agent miscoordination on homedir In-Reply-To: References: Message-ID: Few more details: gpgme used to generate symmetric encryption with gpgme_op_encrypt; version is latest gpg4win. Best, tortoisedoc On Tue, Sep 3, 2013 at 11:53 PM, Tone Kastlunger wrote: > Hi; > apparently gpg-agent has indeed some issues with non-standard homedirs > > I have been trying to get gpg4win to work over gpgme; > but passphrase dialog was not showing in my project and bad passphrase was > always raised. > > It kept puzzling me until after alot of googling around I reached this: > > http://lists.gnupg.org/pipermail/gnupg-users/2012-April/044138.html > > Basically what I did in my project is to set a custom home directory via > gpgme_ctx_set_engine_info; > > pre-starting the gpg-agent with the same argumes as the gpgme would PLUS > the > --homedir set to the same value passed to gpgme_ctx_set_engine_info fixed > the issue and made the pass entry dialog show correctly. > > I think it might have something to do with the gpg-agent not finding the > socket descriptor. > > Best, > tortoisedoc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amk at amk.ca Fri Sep 6 15:31:59 2013 From: amk at amk.ca (A.M. Kuchling) Date: Fri, 6 Sep 2013 09:31:59 -0400 Subject: How to help with GnuPG documentation? Message-ID: <20130906133159.GA67631@DATLANDREWK.local> I'd like to help with updating GnuPG's documentation and/or the web site. What tasks need to be done? I'm happy to write new material, check that existing text and examples are still correct for GnuPG 2, convert the documentation from one format to another, update the FAQ, etc. For example, I noticed the GNU Privacy Handbook has a copyright date of 1999. Does it need updating for current versions of GnuPG? If yes, where is the master Texinfo source? I've been unable to locate it. (My writing background: I've written some pieces of the official Python documentation, such as the What's New in Python 2.x and some of the HOWTOs, but now am looking for a new documentation project to work on.) Thanks! --amk From orion at cora.nwra.com Fri Sep 6 22:54:11 2013 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 6 Sep 2013 20:54:11 +0000 (UTC) Subject: Should pinentry use libassuan and/or libgcrypt? Message-ID: Please pardon this naive question. From a packaging standpoint, I was trying to determine if pinentry "bundles" libassuan and/or parts of libgcrypt (as secmem). Apparently there is a "stripped down" libassuan in assuan/, and it has a secmem/ directory which I think provides functionality that is in libgcrypt. Is there a technical reason to do it this way rather than using libassuan and libgcrypt directly? Naively I'm thinking that reusing security sensitive code via a library would be better than copies of source code making for multiple places to fix issues. - Orion From wk at gnupg.org Sat Sep 7 12:24:30 2013 From: wk at gnupg.org (Werner Koch) Date: Sat, 07 Sep 2013 12:24:30 +0200 Subject: Should pinentry use libassuan and/or libgcrypt? In-Reply-To: (Orion Poplawski's message of "Fri, 6 Sep 2013 20:54:11 +0000 (UTC)") References: Message-ID: <87eh91gc9t.fsf@vigenere.g10code.de> On Fri, 6 Sep 2013 22:54, orion at cora.nwra.com said: > Please pardon this naive question. From a packaging standpoint, I was > trying to determine if pinentry "bundles" libassuan and/or parts of > libgcrypt (as secmem). Apparently there is a "stripped down" Right - very stripped down. > Is there a technical reason to do it this way rather than using libassuan > and libgcrypt directly? Naively I'm thinking that reusing security > sensitive code via a library would be better than copies of source code > making for multiple places to fix issues. Nope: The goal is to make Pinentry as small as possible so that it can be easily audited and regression in libraries don't reflect badly on it. We don't need anything from Libgcrypt. It is just a coincidence that both try to protect malloced data from being paged out. We could even get rid of that if only the swap space would be encrypted. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From wk at gnupg.org Sat Sep 7 12:45:11 2013 From: wk at gnupg.org (Werner Koch) Date: Sat, 07 Sep 2013 12:45:11 +0200 Subject: How to help with GnuPG documentation? In-Reply-To: <20130906133159.GA67631@DATLANDREWK.local> (A. M. Kuchling's message of "Fri, 6 Sep 2013 09:31:59 -0400") References: <20130906133159.GA67631@DATLANDREWK.local> Message-ID: <87zjrogbbc.fsf@vigenere.g10code.de> Hi, On Fri, 6 Sep 2013 15:31, amk at amk.ca said: > I'd like to help with updating GnuPG's documentation and/or the web > site. What tasks need to be done? I'm happy to write new material, > check that existing text and examples are still correct for GnuPG 2, > convert the documentation from one format to another, update the FAQ, Right, the documentation is pretty old. There are a lot of open tasks; see below. > For example, I noticed the GNU Privacy Handbook has a copyright date > of 1999. Does it need updating for current versions of GnuPG? If yes, > where is the master Texinfo source? I've been unable to locate it. The problem with the GPH is that we put it under the GNU FDL which turns out to be a real problem for reuse. I'd love to change this to CC-by-sa/GPL - I just have not come around to ask the FSF to allow for that. I have recently been in contact with Mike Ashley, who wrote the GPH and he agrees that this will be good move. There is also another book: The Gpg4win Compendium (German and English version) which has quite some interesting stuff in it. It suffers from the same FDL problem. Here I already contacted the copyright holders and it seems that we will eventually be able to change the license. The most important thing to do is to give the www.gnupg.org a fresh look. The site is based on WML which is not exactly easy to maintained or use. I have already started to change that by converting the rendered HTML pages to org-mode. Most existing pages have now been converted but a menu system and a new CSS is missing. I have not yet pushed the new org-mode based pages but can do this soon. Although we need to maintain the old links (because they are references a lot) we should add some more information targeted to an average use. For the old pages a simple note at the top, that the info below is probably out of dated will make sense. The FAQ has been converted to org-mode and is part of GnuPG proper; it is easy to update but it needs more stuff. Fortunately Robert Hansen worked on a new FAQ and we should merge the existing stuff with his new answers. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From rjh at sixdemonbag.org Sat Sep 7 14:26:42 2013 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sat, 07 Sep 2013 08:26:42 -0400 Subject: How to help with GnuPG documentation? In-Reply-To: <87zjrogbbc.fsf@vigenere.g10code.de> References: <20130906133159.GA67631@DATLANDREWK.local> <87zjrogbbc.fsf@vigenere.g10code.de> Message-ID: <522B1B82.40402@sixdemonbag.org> On 9/7/2013 6:45 AM, Werner Koch wrote: > The FAQ has been converted to org-mode and is part of GnuPG proper; it > is easy to update but it needs more stuff. Fortunately Robert Hansen > worked on a new FAQ and we should merge the existing stuff with his new > answers. Further, there's a github repository for it: https://github.com/rjhansen/gpgfaq I was under the impression it was going to be a total rewrite rather than a merge. If there are any questions in the current FAQ that are not in the new one (and need to be), I'd consider that a bug and would appreciate being told about them. :) What do you need from me, on my end, in order to begin replacing the old FAQ with the new one? From nicholas.cole at gmail.com Sat Sep 7 17:58:29 2013 From: nicholas.cole at gmail.com (Nicholas Cole) Date: Sat, 7 Sep 2013 16:58:29 +0100 Subject: Command Line Consistency Message-ID: Dear Werner, I wonder if the command line for --disable-cipher-algo name could be made consistent with --personal-cipher-preferences string Currently, the former can only accept the name of the algorithm, whereas the latter can accept either the name or the OpenPGP number. In addition --disable-cipher-algo only accepts a single name at a time, whereas the other similar options tend to accept a list. Just a thought. N. From amk at amk.ca Sat Sep 7 18:03:41 2013 From: amk at amk.ca (A.M. Kuchling) Date: Sat, 7 Sep 2013 12:03:41 -0400 Subject: How to help with GnuPG documentation? In-Reply-To: <87zjrogbbc.fsf@vigenere.g10code.de> References: <20130906133159.GA67631@DATLANDREWK.local> <87zjrogbbc.fsf@vigenere.g10code.de> Message-ID: <20130907160341.GB74214@datlandrewk.home> On Sat, Sep 07, 2013 at 12:45:11PM +0200, Werner Koch wrote: > or use. I have already started to change that by converting the > rendered HTML pages to org-mode. Most existing pages have now been > converted but a menu system and a new CSS is missing. I have not yet > pushed the new org-mode based pages but can do this soon. OK; I'm happy to work on this, or on the FAQ conversion. I already use org-mode to track my todo items so I have some familiarity with it, though I haven't used it for writing documents. Are either the web site or the FAQ available as repositories? Or should I be writing Robert Hansen and offering help? Thanks! --amk From wk at gnupg.org Sat Sep 7 20:30:06 2013 From: wk at gnupg.org (Werner Koch) Date: Sat, 07 Sep 2013 20:30:06 +0200 Subject: How to help with GnuPG documentation? In-Reply-To: <522B1B82.40402@sixdemonbag.org> (Robert J. Hansen's message of "Sat, 07 Sep 2013 08:26:42 -0400") References: <20130906133159.GA67631@DATLANDREWK.local> <87zjrogbbc.fsf@vigenere.g10code.de> <522B1B82.40402@sixdemonbag.org> Message-ID: <87bo44fpsh.fsf@vigenere.g10code.de> On Sat, 7 Sep 2013 14:26, rjh at sixdemonbag.org said: > I was under the impression it was going to be a total rewrite rather > than a merge. If there are any questions in the current FAQ that are To avoid breaking links to the existing FAQ, we should keep the anchors which are already known. Those answers might be moved to an old-stuff section andd updated with a link to a more appropriate Q+A. > not in the new one (and need to be), I'd consider that a bug and would > appreciate being told about them. :) I have not checked for quite some time :-( > What do you need from me, on my end, in order to begin replacing the old > FAQ with the new one? Well, I would like to change to org-mode. pandoc has support for this or it can be done manually while kind of merging with the list. org-mode is really easy to read and edit. Here is an example (indented by 2 spaces) #+LINK: gnupgweb http://www.gnupg.org/ #+LINK: roundup https://bugs.g10code.com/gnupg/issue * General Questions ** What is GnuPG? :PROPERTIES: :CUSTOM_ID: what-is-gnupg :END: [[gnupgweb][GnuPG]] stands for GNU Privacy Guard ... One asterisk translates to

and two of them to

but that can be changed. The +LINK: lines defines shortcuts for URLs and the PROPERTIES drawer is used to specify a link id (In HTML: #what-is-gnupg). I can do that conversion if you agree to make org-mode the new source format. I would also very much like to have the FAQ under a dual license CC-by-sa 3.0 unported and GPLv2+. This allows to reuse it in Wikipedia other manuals as well as in GPL code. The existing FAQ has a copyright notices mentioning only the FSF. That is actually not correct because this was never assigned to the FSF and for sure some answers have been taken from the mailing lists (which however is assumed to be in the public domain). Thus it is not easy to track who wrote for the FAQ. I would very much like to see a (C) 1998-2013 The GnuPG contributors with a list of those contributors. I am not sure whather this is legally possible given that this is a fuzzy description. As of now it reads Many thanks to Nils Ellmenreich for maintaining this FAQ file for such a long time, David D. Scribner for continuing maintenance, Werner Koch for the original FAQ file, and to all posters to gnupg-users and gnupg-devel. They all provided most of the answers. Converted to org-mode and removed from the tarballs in October 2010. We could keep that and add the copyright lines for all mentioned persons with you listed first. Any suggestions? Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From wk at gnupg.org Sat Sep 7 20:33:54 2013 From: wk at gnupg.org (Werner Koch) Date: Sat, 07 Sep 2013 20:33:54 +0200 Subject: How to help with GnuPG documentation? In-Reply-To: <20130907160341.GB74214@datlandrewk.home> (A. M. Kuchling's message of "Sat, 7 Sep 2013 12:03:41 -0400") References: <20130906133159.GA67631@DATLANDREWK.local> <87zjrogbbc.fsf@vigenere.g10code.de> <20130907160341.GB74214@datlandrewk.home> Message-ID: <877gesfpm5.fsf@vigenere.g10code.de> On Sat, 7 Sep 2013 18:03, amk at amk.ca said: > org-mode to track my todo items so I have some familiarity with it, > though I haven't used it for writing documents. Are either the web It is really cool tool. > site or the FAQ available as repositories? Or should I be writing > Robert Hansen and offering help? The original one is doc/faq.org in gnupg's git master. Or at Robert's is at https://github.com/rjhansen/gpgfaq Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From wk at gnupg.org Sat Sep 7 20:36:53 2013 From: wk at gnupg.org (Werner Koch) Date: Sat, 07 Sep 2013 20:36:53 +0200 Subject: Command Line Consistency In-Reply-To: (Nicholas Cole's message of "Sat, 7 Sep 2013 16:58:29 +0100") References: Message-ID: <8738pgfph6.fsf@vigenere.g10code.de> On Sat, 7 Sep 2013 17:58, nicholas.cole at gmail.com said: > Currently, the former can only accept the name of the algorithm, > whereas the latter can accept either the name or the OpenPGP number. I prefer to keep it as it is, changing this would require quite some changes for an option which in most cases is useless. But if someone provides a concise patch I would reconsider. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From rjh at sixdemonbag.org Sun Sep 8 02:07:46 2013 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sat, 07 Sep 2013 20:07:46 -0400 Subject: How to help with GnuPG documentation? In-Reply-To: <87bo44fpsh.fsf@vigenere.g10code.de> References: <20130906133159.GA67631@DATLANDREWK.local> <87zjrogbbc.fsf@vigenere.g10code.de> <522B1B82.40402@sixdemonbag.org> <87bo44fpsh.fsf@vigenere.g10code.de> Message-ID: <522BBFD2.3020006@sixdemonbag.org> On 9/7/2013 2:30 PM, Werner Koch wrote: > To avoid breaking links to the existing FAQ, we should keep the > anchors which are already known. Those answers might be moved to an > old-stuff section andd updated with a link to a more appropriate > Q+A. I'll see about making a first stab at this. > Well, I would like to change to org-mode. It's already in org-mode. Or, rather, it's in a *really* kludged up XML that I convert to org-mode via a Python script (which is part of the git repo). > I can do that conversion if you agree to make org-mode the new source > format. There are reasons to prefer XML right now -- basically, it makes it much easier for me to keep a table of contents together. But yes, it was always my understanding that it would be submitted as org-mode text. > I would also very much like to have the FAQ under a dual license > CC-by-sa 3.0 unported and GPLv2+. This allows to reuse it in > Wikipedia other manuals as well as in GPL code. Point. I can see about making that change. Since I'm the only author, relicensing isn't a problem. > We could keep that and add the copyright lines for all mentioned > persons with you listed first. It's not important to me that I be listed first -- just that I be listed. :) From amk at amk.ca Sun Sep 8 04:24:41 2013 From: amk at amk.ca (A.M. Kuchling) Date: Sat, 7 Sep 2013 22:24:41 -0400 Subject: Old and new FAQs Message-ID: <20130908022441.GA81707@datlandrewk.home> I took a look at the question titles in the existing and proposed new FAQs, assuming that we'd want to start from the new FAQ and cherry-pick bits from the old FAQ, since portions of it are obsolete, rather than the other way around. What I thought: * We can ignore the old FAQ's 'Compatibility Issues' and 'Problems and Error Messages' sections; it's not clear if any of them apply to GPG 2.0, and we'd have to figure out what error messages are currently relevant. * The old FAQ had an empty 'Bug reporting and hacking' section; the new FAQ should have a brief entry for that. * Some old FAQ questions that seemed worth examining further and possibly incorporating in the new FAQ: ** What is the difference between options and commands? (three related questions) ** I can't delete a user ID on my secret keyring because it has already been deleted on my public keyring. What can I do? ** I can't delete my secret key because the public key disappeared. What can I do? ** I still have my secret key, but lost my public key. What can I do? gpgsplit not installed by my MacOS binary installation. ** How do I sign a patch file? ** How can I get rid of the Version and Comment headers in armored messages? (answer is outdated; correct answer for gpg2 is --no-version --no-comments) ** What does the "You are using the xxxx character set." mean? ** How can I get list of key IDs used to encrypt a message? (answer still works) ** How can I use GnuPG in an automated environment? ** Clearsigned messages sent from my web-mail account have an invalid signature. Why? Some of these may actually be addressed in the new FAQ; I haven't actually read the entry texts yet. I've included the question lists below, so that others can compare them and suggest other topics that should or shouldn't be included. (BTW, I'm happy to take this discussion back to gnupg-doc if it's too off-topic or gets too high-traffic for gnupg-devel.) --amk Old FAQ: * Welcome ** What conventions are used in this FAQ? * General Questions ** What is GnuPG? ** Is GnuPG compatible with PGP? ** Is GnuPG free to use for personal or commercial use? * Sources of Information ** Where can I find more information on GnuPG? ** Where do I get GnuPG? * Installation ** Which OSes does GnuPG run on? ** Which random data gatherer should I use? ** How do I include support for RSA and IDEA? * Usage ** What is the recommended key size? ** Why does it sometimes take so long to create keys? ** And it really takes long when I work on a remote system. Why? ** What is the difference between options and commands? ** I can't delete a user ID on my secret keyring because it has already been deleted on my public keyring. What can I do? ** I can't delete my secret key because the public key disappeared. What can I do? ** What are trust, validity and ownertrust? ** How do I sign a patch file? ** Where is the "encrypt-to-self" option? ** How can I get rid of the Version and Comment headers in armored messages? ** What does the "You are using the xxxx character set." mean? ** How can I get list of key IDs used to encrypt a message? ** Why can't I decrypt files encrypted as symmetrical-only (-c) with a version of GnuPG prior to 1.0.1. ** How can I use GnuPG in an automated environment? ** Which email-client can I use with GnuPG? ** Can't we have a gpg library? ** I have successfully generated a revocation certificate, but I don't understand how to send it to the key servers. ** How do I put my keyring in a different directory? ** How do I verify signed packages? ** How do I export a keyring with only selected signatures (keys)? ** I still have my secret key, but lost my public key. What can I do? ** Clearsigned messages sent from my web-mail account have an invalid signature. Why? * Compatibility Issues ** How can I encrypt a message with GnuPG so that PGP is able to decrypt it? ** How do I migrate from PGP 2.x to GnuPG? ** Why is PGP 5.x not able to encrypt messages with some keys? ** Why is PGP 5.x not able to verify my messages? ** How do I transfer owner trust values from PGP to GnuPG? ** PGP does not like my secret key. ** GnuPG no longer installs a ~/.gnupg/options file. Is it missing? ** How do you export GnuPG keys for use with PGP? ** What are DH/DSS keys? * Problems and Error Messages ** Why do I get "gpg: Warning: using insecure memory!" ** Large File Support doesn't work ** In the edit menu the trust values are not displayed correctly after signing uids. Why? ** What does "skipping pubkey 1: already loaded" mean? ** GnuPG 1.0.4 doesn't create ~/.gnupg ... ** An Elgamal signature does not verify anymore since version 1.0.2 ** Old versions of GnuPG can't verify Elgamal signatures ** When I use --clearsign, the plain text has sometimes extra dashes in it - why? ** What is the thing with "can't handle multiple signatures"? ** If I submit a key to a keyserver, nothing happens ** I get "gpg: waiting for lock ..." ** Older gpg binaries (e.g., 1.0) have problems with keys from newer gpg binaries ** With 1.0.4, I get "this cipher algorithm is deprecated ..." ** Some dates are displayed as ????-??-??. Why? ** I still have a problem. How do I report a bug? ** Why doesn't GnuPG support X.509 certificates? ** Why do national characters in my user ID look funny? ** I get 'sed' errors when running ./configure on Mac OS X ... ** Why does GnuPG 1.0.6 bail out on keyrings used with 1.0.7? ** I upgraded to GnuPG version 1.0.7 and now it takes longer to load my keyrings. What can I do? ** Doesn't a fully trusted user ID on a key prevent warning messages when encrypting to other IDs on the key? ** I just compiled GnuPG from source on my GNU/Linux RPM-based system and it's not working. Why? * Advanced Topics ** How does this whole thing work? ** Why are some signatures with an ELG-E key valid? ** How does the whole trust thing work? ** What kind of output is this: "key C26EE891.298, uid 09FB: ...."? ** How do I interpret some of the informational outputs? ** Are the header lines of a cleartext signature part of the signed material? ** What is the list of preferred algorithms? ** How do I change the list of preferred algorithms? ** How can I import all the missing signer keys? * Bug reporting and hacking ** Copyright assignments ** U.S. export restrictions * Acknowledgements * Changes New FAQ: