Mailinglist Archive: opensuse-factory (375 mails)

< Previous Next >
Re: [opensuse-factory] gpg debug flag enabled
  • From: Maximilian Trummer <maximilian@xxxxxxxxxxx>
  • Date: Tue, 01 May 2018 20:53:50 +0200
  • Message-id: <8205186.iqGOr59lr7@thinkpad>
Am Dienstag, 1. Mai 2018, 20:39:35 CEST schrieb Maximilian Trummer:
$ gpg --list-keys
gpg: enabled debug flags: memstat
/home/user/.gnupg/pubring.kbx
-----------------------------
(snip)

gpg: keydb: handles=1 locks=0 parse=1 get=1
gpg: build=0 update=0 insert=0 delete=0
gpg: reset=1 found=1 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=2 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/65536 bytes in 0 blocks
(end of output)

Is this enabled debug flag the expected behavior now, or is it an oversight?

Furthermore, when I unlock a password with passwordstore which uses gpg as
backend, there is this line at the top of the output:

can't connect to 'socket:///home/user/.gnupg/log-socket': Verbindungsaufbau
abgelehnt
("connection refused")


--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >