security/debian-keyring error while trying to import a key

Charlie Brown

Charlie Brown

Hello everyone,
I'm trying to import a key from the /usr/local/share/keyrings/debian-keyring.gpg following this tutorial to verify a signature, but I get this error :
$ gpg --keyring=/usr/local/share/keyrings/debian-keyring.gpg --export chris@chris-lamb.co.uk | gpg --import
$
gpg: WARNING: nothing exported
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
$
when executing step #3 from the step: "1/7-Verify the Tails signing key." in the tutorial.

Also the following gpg --decrypt --verbose /usr/local/share/keyrings/debian-keyring.gpg return that
gpg: enabled compatibility flags:
gpg: decrypt_message failed: Unexpected error

where do I find the key to check it's content?

thanks.
 
I could reproduce the behavior if invoking gpg(1) as root. However, in the installation guide – the “tutorial” – the commands that require elevated privileges are prefixed with sudo . Run gpg(1) as a regular user then it works:​
Bash: 
gpg --keyring '/usr/local/share/keyrings/debian-keyring.gpg' --list-keys # _not_ --decrypt for keyring files!
If you insist on working as root, specify the --homedir /root parameter. I don’t know why this makes a difference, though.​
 
I did run the command in regular user mode not root. that's why I put the $ sign.
As for
gpg --keyring '/usr/local/share/keyrings/debian-keyring.gpg' --list-keys it list my keys but not the keys inside the debian-keyring file. Same as if I run this command
gpg --list-keys
 
Hmm… OK, now I could recreate the behavior as a normal user, too, by setting the home directory to a non‑existent directory. gpg(1) wants to create and access several files beside the specified keyring. Let’s convince gpg(1) to stop doing that, after all exporting a key from a keyring is essentially a read‑only operation.​
Bash: 
gpg --no-options --trust-model always \
--keyring '/usr/local/share/keyrings/debian-keyring.gpg' \
--armor --export 'chris@chris-lamb.co.uk'
 
Kai Burghardt said:
by setting the home directory to a non‑existent directory
Click to expand...
What do you mean by that? What's the purpose of it ?

Kai Burghardt said:
gpg(1) wants to create and access several files beside the specified keyring
Click to expand...
How did you come to that conclusion, where did you find the information?

Because, for my part, I don't seem to have a log file for gpg and the --verbose option doesn't speak much. So I'm curious to know what file you looked at so I can see too.
 
Code: 
$  gpg --debug-all --keyring=/usr/local/share/keyrings/debian-keyring.gpg --export chris@chris-lamb.co.uk | gpg --import

gpg: reading options from '/home/free/.gnupg/gpg.conf'
gpg: reading options from '[cmdline]'
gpg: reading options from '/home/free/.gnupg/common.conf'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust hashing ipc clock lookup extprog
gpg: enabled compatibility flags:
gpg: DBG: [no clock] start
gpg: DBG: iobuf-1.0: open '[stdout]' desc=file_filter(fd) fd=1
gpg: writing to stdout
gpg: DBG: iobuf-1.0: ioctl 'file_filter(fd)' no_cache=1
gpg: DBG: [no clock] keydb_new
gpg: DBG: chan_3 <- # Home: /home/free/.gnupg
gpg: DBG: chan_3 <- # Config: [none]
gpg: DBG: chan_3 <- OK Keyboxd 2.4.5 at your service
gpg: DBG: connection to the keyboxd established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.4.5
gpg: DBG: chan_3 <- OK
gpg: DBG: [no clock] keydb_search enter
gpg: DBG: keydb_search: 1 search descriptions:
gpg: DBG: keydb_search   0: SUBSTR: 'chris@chris-lamb.co.uk'
gpg: DBG: chan_3 -> SEARCH --openpgp -- *chris@chris-lamb.co.uk
gpg: DBG: chan_3 <- ERR 134217755 Not found <Keybox>
gpg: DBG: [no clock] keydb_search leave (not found)
gpg: DBG: [no clock] keydb_release
gpg: DBG: [no clock] close_context (found)
gpg: WARNING: nothing exported
gpg: DBG: iobuf-1.0: close 'file_filter(fd)'
gpg: DBG: chan_3 -> BYE
gpg: DBG: [no clock] stop
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: objcache: keys=0/0/0 chains=0,0..0 buckets=0/0 attic=0
gpg: objcache: uids=0/0/0 chains=0,0..0 buckets=0/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/32768 bytes in 0 blocks
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

You mean gpg(1) wants to access a configuration file that doesn't exist? or is it the common.conf that cause the issue?
gpg: DBG: chan_3 <- ERR 134217755 Not found <Keybox> ??
 
You must log in or register to reply here.
Back
Top