sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Sks-devel] sks not storing a key


From: Brian Minton
Subject: [Sks-devel] sks not storing a key
Date: Tue, 19 Jul 2016 09:11:20 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0

I recently sent a key to my keyserver, keyserver.brian.minton.name which
showed success, but then when I tried to receive it back, I got an error
saying no data.

Here's the output of sending the key (note that localhost is the keyserver):


> gpg2 -vvvvvvv --debug 4 --send DD1A52F9DA8C9020
> gpg: reading options from '/home/bminton/.gnupg/gpg.conf-2'
> gpg: using character set 'utf-8'
> gpg: enabled debug flags: crypto
> gpg: sending key 4FD0FA5528DB9E3F to hkp://localhost
> gpg: DBG: rsa_verify 
> data:+01ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffff003051300d0609608648016503040203050004401d \
> gpg: DBG:                  
> a922a4f943595489ee637dd388c5a8d42a26a1e3296a4134f6a17e6f09a56b50 \
> gpg: DBG:                  
> afb27e10b5cf2711e367cc89959966aceb843c9e880dbe3d72e92b05a36177
> gpg: DBG: rsa_verify  
> sig:+9c091f3d94d101e59fed9abac57651e53c27268a0096813ef64aa3f6d0e19ebc \
> gpg: DBG:                  
> 01dd4f8f92304a6303f409e517a954fefa8bdf212ff81c1afab6e0c3cf98706a \
> gpg: DBG:                  
> 9296d913d22daed18ffe6c51539a3439364fec7a4c6818e8f4677b8d3bab2651 \
> gpg: DBG:                  
> 8cc586499478af2f912490e568d89ae7d66e63391379b7636271e0342f91ed70 \
> gpg: DBG:                  
> 60e1c178c937fbf3da878efc7865f2d9e5e7aff285f5ed28164d361aee201a12 \
> gpg: DBG:                  
> c9153f2d5c55056cc14be4c912887c673a5d157a2ae84f49d72670b6f92a40db \
> gpg: DBG:                  
> 8f034f8a4c974d9b900e34df3e16e61c20084af4d33b5fb375acebe1ff572a7d \
> gpg: DBG:                  
> 254c01f995a7509dc556ecc2e72dc36eec7fc5b3a427d8c18e4d0f8cd5aefc3f
> gpg: DBG: rsa_verify    
> n:+bee23a531821502d4098729016ba598e67aebaf9e4bcff092056177b244f53ea \
> gpg: DBG:                  
> 9784c76683692614cc92c6c608a9b3b0ee00adffd8195862276994939448cbd3 \
> gpg: DBG:                  
> 2274bcd2b4472eea9b826961176e9051706451b189464c378e5a2432f835d062 \
> gpg: DBG:                  
> a0c4847da1477b8668d24867007cb8fc3645e3c1f63f6e9eafec5b733bc1353d \
> gpg: DBG:                  
> 6ccb05b9960c884b1154f1fc364343b8727433104b9959f3d26ed235990e9d7b \
> gpg: DBG:                  
> 21edba9c63b2f15c7f79b778b76bea215a163046faebe316d60b00290dbfbd5d \
> gpg: DBG:                  
> f19d1acd9ea5cf6ede1069751999159b80617b103058e607154c63ce6e59e615 \
> gpg: DBG:                  
> 8140ebfa419d3912c406f0a01a96bfd81a6e962dc4f226dbba98c7f8819e23df
> gpg: DBG: rsa_verify    e:+010001
> gpg: DBG: rsa_verify  
> cmp:+01ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff \
> gpg: DBG:                  
> ffffffffffffffffffffff003051300d0609608648016503040203050004401d \
> gpg: DBG:                  
> a922a4f943595489ee637dd388c5a8d42a26a1e3296a4134f6a17e6f09a56b50 \
> gpg: DBG:                  
> afb27e10b5cf2711e367cc89959966aceb843c9e880dbe3d72e92b05a36177
> gpg: DBG: rsa_verify    => Good
> gpg: secmem usage: 0/65536 bytes in 0 blocks

And here's the output of receiving:

> gpg2 -vvvvvvv --debug 4 --recv DD1A52F9DA8C9020
> gpg: reading options from '/home/bminton/.gnupg/gpg.conf-2'
> gpg: using character set 'utf-8'
> gpg: enabled debug flags: crypto
> gpg: keyserver receive failed: No data
> gpg: secmem usage: 0/65536 bytes in 0 blocks

I know sks should be able to handle the key, since I got it from
pgp.mit.edu, an sks server.

thanks,
Brian Minton


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]