On Monday 30 April 2018 12:52:56 deloptes wrote:
Gene Heskett wrote:
Heck, I've fooled around because I do get signed messages, but I've yet to figure out how to get a successfull verification that the signage is correct. Setup needs help with setup. Humm, isn't that a circular dependency? ;-/
If you use Kmail or Knode it would do the work for you. You just need to maintain your keylists properly - perhaps in Kgpg. So as soon as you verify a key, you alter the key trust level - the next time you open an email signed with the key, it should show green, or yellow.
Otherwise you can use gpg on the command line to verify the message. The purpose of the signature is to verify that this is exactly the message, that was sent, so the whole message is passed trough gnupg. The signature can also be used to identify the public key of the sender
I don't see redundancy - just another level of work (likebehind the curtains).
regards
The biggest problem is that I have a public key that was published back about pgp-262 or 262a time, 20 years back, so its out there "someplace", so I expect I should try to locate it and remove it from view/use before I try to setup another. Unforch ther drive in the amiga died, and took the keys with it to that great pasture that shitty drives goto when they fail.
I don't recall if I set an expire on it or not. Or without the shorter ID string, how to convince the key-servers its mine, so its ok to nuke that puppy.
Sigh... Don't get old, deloptes, its not all the fun its cracked up to be.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting