Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 773  |
|  mark lewis to August Abolins  |
|  Safester, anyone?  |
|  30 Jan 22 05:04:48  |
 REPLY: 2:221/1.58@fidonet f8e44f3a MSGID: 1:3634/12.73 61f66464 PID: GED+LNX 1.1.5-b20180707 CHRS: CP437 2 TZUTC: -0500 TID: hpt/lnx 1.9.0-cur 17-02-17 On 2022 Jan 29 09:12:00, you wrote to Wilfred van Velzen: WvV>> An attacker with enough resources could in theory find some or all WvV>> passwords. And of course that becomes progressively easier in the WvV>> future... AA> I am not impressed with the reports that people can process millions AA> of hashes per second using dedicated GPUs. So what if the hashes are AA> decoded. you're missing something here... it isn't the hashes being decoded... they're just a large number... it is the use of them to decode messages that is the goal... the faster you calculate hashes to beat against the encoded message to see if there's anything legible in the result, the faster you can gain access to that information... AA> They can't do anything with them to target millions of people enmasse AA> anyway. I think they would have to target SPECIFIC accounts and run AA> the passwords one by one. if something is found in passing, then specific accounts may gain closer looks at their traffic... AA> In Safester, the decoded hash would reveal the passphrase, but the AA> decrypting of the messages would be useless without the user's key AA> which would reside in the local Safester prog or app. if i were to intercept an encoded message and want to decode it, i wouldn't be worrying about the passphrase or the key... i'd concentrate on throwing hashes at the message and seeing if anything legible appeared at the end of the decode phase... if there was nothing, then throw another hash at it and look again... )\/(ark "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... Cats are not dogs! -P.G. Wodehouse --- * Origin: (1:3634/12.73) SEEN-BY: 1/120 123 15/0 18/0 90/1 105/81 106/201 116/116 120/340 123/0 SEEN-BY: 123/25 131 180 190 200 755 129/330 331 135/300 138/146 153/7715 SEEN-BY: 222/2 226/30 227/114 229/110 206 317 400 424 426 664 700 SEEN-BY: 240/1120 5832 250/1 266/512 275/100 1000 282/1038 292/854 SEEN-BY: 301/1 317/3 320/219 322/757 342/11 200 396/45 460/58 640/1321 SEEN-BY: 712/848 2320/105 3634/0 12 15 27 50 119 5020/1042 PATH: 3634/12 153/7715 229/426 |
[ << oldest | < older | list | newer > | newest >> ]