Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 672  |
|  Paul Hayton to mark lewis  |
|  Hum..  |
|  26 Feb 16 22:34:46  |
 RESCANNED 3:770/1 TID: Mystic BBS 1.12 A5 MSGID: 3:770/100 485ab457 REPLY: 1:3634/12.73 56cdc519 TZUTC: 1300 On 02/24/16, mark lewis pondered and said... ml> it works two ways... ml> ml> 1. if you post a message encrypted with your PRIVATE key, anyone with ml> your PUBLIC key can decrypt it... that proves it was you that encrypted The issue I am having is using the tool I have come across to do just that. Use my Private key to encrypt something that can be unlocked by the PUBLIC key. It would appear gpg4win does not allow this and in a way I can understand why as it flys in the face of what I think the PUBLIC vs PRIVATE keys are to be used for (I think) --- Mystic BBS v1.12 A5 (Windows) * Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100) SEEN-BY: 1/123 57/0 90/1 120/340 601 123/131 153/250 757 220/70 226/17 SEEN-BY: 226/30 227/114 702 229/101 424 426 664 1014 240/5832 249/206 SEEN-BY: 249/317 400 267/800 280/464 292/854 310/31 317/3 322/757 SEEN-BY: 340/1000 342/200 712/848 770/0 1 100 340 772/0 1 220 230 SEEN-BY: 772/500 PATH: 770/100 1 229/664 426 |
[ << oldest | < older | list | newer > | newest >> ]