Hello!


I see this when I look up my keys:

pub 2048R/5789589B 2020-01-02

Fingerprint=D0EB 2A29 5204 F316 7EB2 503C EF0E 8965 5789 589B



uid August Abolins <august@kolico.ca>

sig sig3 5789589B 2020-01-06 __ 2024-12-31 [selfsig]



uid August Abolins <august@R_E_M_O_V_Ekolico.ca>

sig sig3 5789589B 2020-01-02 __ 2024-12-31 [selfsig]

sig sig2 56CDF35B 2020-01-03 __ __ Tommi Koivula <tommi@fidonet.fi>

sig sig3 2A6F822A 2020-01-03 __ __ Tommi Koivula <tommi@rbb.fidonet.fi>


Does that mean that Tommi signed my key? If so, I should probably have a copy of Tommi's public key submission.

Is this simply accomplished with a refresh from a server?

I tried:

gpg --refresh-keys --keyserver pgp.key-server.io

gpg: refreshing 12 keys from hkp://pgp.key-server.io
gpg: keyserver refresh failed: No keyserver available

But.. I *can* visit the server and search via the web interface, no
problem.

What servers is everybody else using that prove to be more reliable?

If, I can't use the refresh function, do I just delete my local copies of Tommi's keys, and just look for newer ones of his 56CDF35B and 2A6F822A?




../|ug

--- OpenXP 5.0.45
* Origin: Key ID = 0x5789589B (2:221/1.58)

Hi August,

On 2020-06-26 18:08:00, you wrote to All:

I see this when I look up my keys:

pub 2048R/5789589B 2020-01-02

Fingerprint=D0EB 2A29 5204 F316 7EB2 503C EF0E 8965 5789 589B

uid August Abolins <august@kolico.ca>

sig sig3 5789589B 2020-01-06 __ 2024-12-31 [selfsig]

uid August Abolins <august@R_E_M_O_V_Ekolico.ca>

sig sig3 5789589B 2020-01-02 __ 2024-12-31 [selfsig]

sig sig2 56CDF35B 2020-01-03 __ __ Tommi Koivula <tommi@fidonet.fi>

sig sig3 2A6F822A 2020-01-03 __ __ Tommi Koivula <tommi@rbb.fidonet.fi>

Hmm, double spacing on the inserted part?

Does that mean that Tommi signed my key?

Looks like it.

If so, I should probably have a copy of Tommi's public key submission.

I think you already do, because otherwise it wouldn't have shown Tommi's name and email adres, but something like [unknown], I think.

Is this simply accomplished with a refresh from a server?

I tried:

gpg --refresh-keys --keyserver pgp.key-server.io

gpg: refreshing 12 keys from hkp://pgp.key-server.io
gpg: keyserver refresh failed: No keyserver available

Try:

# gpg --keyserver hkp://pool.sks-keyservers.net --keyserver-options no-honor-keyserver-url --refresh-keys koivula

Or replace the --refresh-keys with --recv-keys, to get/update all Tommi's keys from the key server...

But.. I *can* visit the server and search via the web interface, no problem.

Maybe it doesn't use the hkp: but http: protocol?

What servers is everybody else using that prove to be more reliable?

I don't use them very often, so I wouldn't know about reliability...

If, I can't use the refresh function, do I just delete my local copies
of Tommi's keys, and just look for newer ones of his 56CDF35B and 2A6F822A?

You don't have to delete them first, to import an updated version...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

** On Saturday 27.06.20 - 11:52, Wilfred van Velzen wrote to August Abolins:

uid August Abolins <august@R_E_M_O_V_Ekolico.ca>

sig sig3 5789589B 2020-01-02 __ 2024-12-31 [selfsig]

sig sig2 56CDF35B 2020-01-03 __ __ Tommi Koivula <tommi@fidonet.fi>

sig sig3 2A6F822A 2020-01-03 __ __ Tommi Koivula
<tommi@rbb.fidonet.fi>

Hmm, double spacing on the inserted part?

I just copy-pasted as it was reported to me pgp.key-server.io online (at their web interface. It is not the double-space problem I was having with signed messsages here.

Does that mean that Tommi signed my key?

Looks like it.

If so, I should probably have a copy of Tommi's public key submission.

I think you already do, because otherwise it wouldn't have shown Tommi's name and email adres, but something like [unknown], I think.

The report above is what I see at pgp.key-server.io

Locally, I get this:

Is this simply accomplished with a refresh from a server?

I tried:

gpg --refresh-keys --keyserver pgp.key-server.io

gpg: refreshing 12 keys from hkp://pgp.key-server.io
gpg: keyserver refresh failed: No keyserver available

Try:

# gpg --keyserver hkp://pool.sks-keyservers.net --keyserver-options no-honor-keyserver-url --refresh-keys koivula

Or replace the --refresh-keys with --recv-keys, to get/update all
Tommi's keys from the key server...

But.. I *can* visit the server and search via the web interface, no
problem.

Maybe it doesn't use the hkp: but http: protocol?

What servers is everybody else using that prove to be more reliable?

I don't use them very often, so I wouldn't know about reliability...

If, I can't use the refresh function, do I just delete my local copies
of Tommi's keys, and just look for newer ones of his 56CDF35B and
2A6F822A?

You don't have to delete them first, to import an updated version...

Bye, Wilfred.

-+- FMail-lnx64 2.1.0.18-B20170815
+ Origin: FMail development HQ (2:280/464)

../|ug

--- OpenXP 5.0.45
* Origin: Key ID = 0x5789589B (2:221/1.58)

Hello Wilfred..

** On Saturday 27.06.20 - 21:32, August Abolins wrote to Wilfred van Velzen:

The report above is what I see at pgp.key-server.io

Locally, I get this:

(Whooops.. apparently I sent out a partially written reply!)

Or replace the --refresh-keys with --recv-keys, to get/update all
Tommi's keys from the key server...

Ah.. ok!

But.. I *can* visit the server and search via the web interface, no
problem.

Maybe it doesn't use the hkp: but http: protocol?

I tried both. Same result. It seems the problem is limited to my XP
machine (mobile ISP). But accessing the servers from command line works
fine from my Win7 pc (DSL).

If, I can't use the refresh function, do I just delete my local
copies of Tommi's keys, and just look for newer ones of his
56CDF35B and 2A6F822A?

You don't have to delete them first, to import an updated
version...

But.. if I can't update the keys from a server, I have to do it manually. That is, I would have to export my keys from the Win7 pc, and carry them
over to my XP pc. Bummer.

../|ug

--- OpenXP 5.0.45
* Origin: Key ID = 0x5789589B (2:221/1.58)

Hi August,

On 2020-06-27 22:43:00, you wrote to me:

The report above is what I see at pgp.key-server.io

Locally, I get this:

(Whooops.. apparently I sent out a partially written reply!)

Indeed you did. ;)

But.. I *can* visit the server and search via the web interface, no
problem.

Maybe it doesn't use the hkp: but http: protocol?

I tried both. Same result. It seems the problem is limited to my XP machine (mobile ISP). But accessing the servers from command line works fine from my Win7 pc (DSL).

Strange...

If, I can't use the refresh function, do I just delete my local
copies of Tommi's keys, and just look for newer ones of his
56CDF35B and 2A6F822A?

You don't have to delete them first, to import an updated
version...

But.. if I can't update the keys from a server, I have to do it
manually. That is, I would have to export my keys from the Win7 pc,
and carry them over to my XP pc. Bummer.

Where you can just import them. You don't have to delete them at the destination first. If they already exist they are updated with the import...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)