Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 392  |
|  August Abolins to Wilfred van Velzen  |
|  Key management could be a nightmare  |
|  05 Jan 20 18:04:26  |
 MSGID: 2:221/360.0 5e120904 REPLY: 2:280/464 5e11d334 PID: JamNNTPd/OS2 1.3 20191208 TID: GE/2 1.2 CHRS: IBMPC 2 TZUTC: 0200 On 1/5/2020 7:12 AM, between "Wilfred van Velzen : August Abolins": AA>> I could email the secret keys between my devices, but I AA>> don't like the idea that email in general is in the clear AA>> and the isp/systems enroute can cache and record anything. WvV> You can use a common storage place, either on your own WvV> network or external lile dropbox. If that's an encrypted WvV> place (I don't know if dropbox is by default?) that would WvV> be even better. Hello Wilfred! I have an option for my Blackberry. I can send it through my own wi-fi connections to a file directory on the device. But I have to do it from my Win7 pc desktop which is at a remote location. :( AA>> The passphrase is fairly decent. I am confident that no one AA>> would be able to guess it. WvV> Than it doesn't matter too much what you use to exchange WvV> the secret key files. Nah.. Even if the secret key were sent with Gmail for example, its copy would be grabbed and stored in the cloud forever. The "they" people could then feed the key to their petra flop computers to try and crack it. I think it is absolutely imperative to never transfer a secret key through a transfer mechanism that I don't have exclusive control over. ../|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 >> ]