Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 390  |
|  August Abolins to Wilfred van Velzen  |
|  enc + netmail  |
|  05 Jan 20 17:46:25  |
 MSGID: 2:221/360.0 5e1204cc REPLY: 2:280/464 5e11d0db PID: JamNNTPd/OS2 1.3 20191208 TID: GE/2 1.2 CHRS: IBMPC 2 TZUTC: 0200 On 1/5/2020 7:03 AM, between "Wilfred van Velzen : August Abolins": AA>> Next to being able to sign messages in echomail/newsgroups, AA>> fully encrypted messages only make sense in email - direct AA>> to a specific individual. WvV> Or routed netmail! But we really don't know the exact route a netmail will take. For a user, unless they analyze the nodelist or confirm things with their sysop, netmail is unreliable. I also use point-software (OpenXP) which allows sending crash mail. With that, I could crash my encrypted netmail to its final destination with confidence to any system that flies the U,ENC flags. AA>> That's the beauty of pulling down the keys and checking AA>> their properties. The properties will reveal creation AA>> dates, expiry dates, revocations, etc. It would be AA>> relatively easy to just pick the most recent date, and send AA>> a brief hello message with a CC: and see which ones reach AA>> their target. WvV> If there are multiple keys to choose from... Yeah, tracking people down from the past that have only one email addy listed on the servers with an expired key could be a challenge. ../|ug --- Thunderbird 2.0.0.24 (Windows/20100228) * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0) SEEN-BY: 1/123 19/10 90/1 154/10 203/0 221/0 1 6 360 227/114 229/426 SEEN-BY: 229/1014 240/5832 249/206 317 400 280/464 5003 292/854 310/31 SEEN-BY: 317/3 322/757 342/200 396/45 423/81 120 712/848 770/1 2452/250 PATH: 221/360 1 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]