Time transpires.. [ ... ] ..I'm back.
The signing process seemed to go ok, but the actual send failed.
Enigmail for TB 60.9 seems to want to send a signed message multi-part whatever - which is rejected.
Whoa! ... I found a setting for "Protocol: Inline PGP" version .vs.
the default "Protocol: MIME/PGP".
Hopefully this one will get sent with inline signature.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I don't think the previous message got signed.
Enigmail for TB 60.9 and TB 24 are quite different!
This one will be signed when I send the message.
../|ug
Time transpires.. [ ... ] ..I'm back.
The signing process seemed to go ok, but the actual send failed.
Enigmail for TB 60.9 seems to want to send a signed message multi-part whatever - which is rejected.
Whoa! ... I found a setting for "Protocol: Inline PGP" version .vs.
the default "Protocol: MIME/PGP".
Hopefully this one will get sent with inline signature.
--[snip]--
gpg: Signature made za 04 jan 2020 22:23:26 CET using RSA key ID
5789589B
gpg: Good signature from "August Abolins <august@R_E_M_O_V_Ekolico.ca>"
[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the
owner.
Primary key fingerprint: D0EB 2A29 5204 F316 7EB2 503C EF0E 8965 5789 589B --[snap]--
Interesting. I *did* pull the key set that Tommi signed, and added that one to my key management system for messages originating from the TB
60.9 pc.
Maybe there is an updated version since then?
Did you get the whole key collection? Or did you pull one of the subkeys?
Did you get the whole key collection? Or did you pull one
of the subkeys?
The whole key collection from the server, with all the
worlds keys? Nope, of course not! ;)
I just got your updated key, and all of Tommi's (I have
about 18 of his now in my keyring)...
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 141:52:32 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,263 |