TIP: Click on subject to list as thread! ANSI
echo: public_keys
to: Tommi Koivula
from: mark lewis
date: 2016-02-26 10:41:54
subject: Testing

26 Feb 16 15:54, you wrote to Paul Hayton:

 TK> XPost: p, u, b
 TK> XPost: l, i, c
 TK> XPost: _, k, e
 TK> XPost: y, s

 TK> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
 TK> --DdhfP4QXQJPOOw5HqjI9i71KnDrMw4ikQ
 TK> Content-Type: multipart/mixed;
 TK>  boundary="------------72DBAAE51EADB07D7C166154"

uuugh what a mess ;) :lol:

[trim]

 TK> Cannot decrypt your message. :(

yes, that's what he and i have been talking about... he tried to encrypt it
with his private key so that anyone with his public key could decrypt it...
i forget exactly how we did that with the original pgp and everything i
find now doesn't say how to do that... maybe because they expect a
"public key" to be easily found and they're not thinking about
restricted distribution of certain public keys...


 TK> --------------72DBAAE51EADB07D7C166154
 TK> Content-Type: application/pgp-keys;
 TK>  name="0x2442E762.asc"

got your key, thanks! :)

)\/(ark

Always Mount a Scratch Monkey

... My function in life: to render clear what is blindingly conspicuous.
---
* Origin: (1:3634/12.73)
SEEN-BY: 109/500 116/116 123/5 52 140 500 789 124/5013 5014 135/300 140/1
SEEN-BY: 154/0 10 701 203/0 226/600 227/51 201 229/426 230/0 261/38 280/464
SEEN-BY: 280/5003 292/624 854 320/119 322/759 340/800 342/11 423/120 633/0 267
SEEN-BY: 633/280 281 712/620 848 770/1 3634/12 27 50
@PATH: 3634/12 123/500 154/10 280/464 712/848 633/280 267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.