Really weird behavior with fresh install

Robert J. Hansen rjh at sixdemonbag.org
Mon Jul 20 19:33:55 CEST 2015


So, in the interests of further checking this out, I figured I'd start
from a fresh slate:

    [rjh at localhost ~]$ rm -rf .gnupg
    [rjh at localhost ~]$ gpg
    gpg: directory `/home/rjh/.gnupg' created
    gpg: new configuration file `/home/rjh/.gnupg/gpg.conf' created
    gpg: WARNING: options in `/home/rjh/.gnupg/gpg.conf' are not ...
    gpg: keyring `/home/rjh/.gnupg/secring.gpg' created
    gpg: keyring `/home/rjh/.gnupg/pubring.gpg' created
    gpg: Go ahead and type your message ...
    ^C
    gpg: Interrupt caught ... exiting



I verified the directory was clean:

    [rjh at localhost ~]$ ls -l .gnupg/
    total 12
    -rw-------. 1 rjh rjh 9188 Jul 20 13:18 gpg.conf
    -rw-------. 1 rjh rjh    0 Jul 20 13:18 pubring.gpg
    -rw-------. 1 rjh rjh    0 Jul 20 13:18 secring.gpg



Let's verify gpg-agent is gone:

    [rjh at localhost ~]$ killall gpg-agent
    gpg-agent: no process found

    [rjh at localhost ~]$ ps ax|grep gpg
    45613 pts/0    S+     0:00 grep --color=auto gpg



Then, when Enigmail tried to get a key list, this happened:

    enigmail> /usr/bin/gpg2 --charset utf-8 --display-charset utf-8
              --batch --no-tty --status-fd 2 --fixed-list-mode
              --with-colons --list-keys
    gpg: error reading key: Invalid user ID



Let's verify there are no user IDs, so ergo there can't be an error
related to an invalid key ID:

    [rjh at localhost ~]$ ls -l .gnupg/
    total 16
    -rw-------. 1 rjh rjh 9188 Jul 20 13:25 gpg.conf
    -rw-------. 1 rjh rjh    0 Jul 20 13:25 pubring.gpg
    -rw-------. 1 rjh rjh    0 Jul 20 13:25 secring.gpg
    -rw-------. 1 rjh rjh   40 Jul 20 13:30 trustdb.gpg



And finally, let's run Enigmail's same command line:

    [rjh at localhost ~]$ /usr/bin/gpg2 --charset utf-8
                       --display-charset utf-8 --batch --no-tty
                       --status-fd 2 --fixed-list-mode --with-colons
                       --list-keys
    tru::1:1437413421:0:3:1:5



... No error.

This is very, very weird.  Does anyone have any thoughts?



More information about the Gnupg-users mailing list