HomeSearchPrevious dayNext day

00:07:29datechnoman quits [Quit: Ping timeout (120 seconds)]
00:08:12datechnoman (datechnoman) joins
01:21:49fishingforsoup__ quits [Read error: Connection reset by peer]
03:34:37Meli quits [Ping timeout: 252 seconds]
03:36:46Meli (Meli) joins
04:34:56Meli quits [Ping timeout: 252 seconds]
04:38:56Meli (Meli) joins
05:49:40dvd_ quits [Remote host closed the connection]
05:50:31dvd_ joins
06:20:40Minkafighter7225 quits [Quit: The Lounge - https://thelounge.chat]
06:21:13Minkafighter7225 joins
06:21:13BlueMaxima quits [Read error: Connection reset by peer]
07:09:04Arcorann (Arcorann) joins
07:33:52DiscantX quits [Ping timeout: 252 seconds]
07:37:38DiscantX joins
10:04:10sonick quits [Client Quit]
10:13:03tbc1887 (tbc1887) joins
10:13:20tbc1887 quits [Remote host closed the connection]
10:35:55Meli quits [Ping timeout: 252 seconds]
10:37:25Meli (Meli) joins
10:51:57jmtd is now known as Jon
11:02:23knecht4204 quits [Quit: The Lounge - https://thelounge.chat]
11:02:44knecht4204 (knecht420) joins
12:56:54<@JAA>'PSA: upgrade your LUKS key derivation function' https://mjg59.dreamwidth.org/66429.html
13:08:37<hexa->I find it highly unlikely that they are supposed to have brute forced a 20 character password on a pbkdf2 keyslot
13:08:49<hexa->lots of things are more plausible than that
13:16:07<@JAA>Yeah, my thoughts exactly. Doesn't mean upgrading to argon2id isn't a good idea anyway.
13:36:10<anarchat>i have my doubts as well
13:36:41<anarchat>last time i checked, it would have required the entire bitcoin network more than a millenia to crack a 20-character password with upper/lower/digits/symbols
13:36:47<anarchat>https://gitlab.com/anarcat/crypto-bench/-/blob/master/benchpasswords.png
13:36:55<anarchat>source: https://gitlab.com/anarcat/crypto-bench/-/blob/master/benchpasswords.py
13:38:22<anarchat>since i wrote that (2017) the hash rate went from 10EH/s to 380EH/s, not that significant of a change
13:44:12Church quits [Ping timeout: 252 seconds]
13:45:07Arcorann quits [Ping timeout: 252 seconds]
14:14:08Mateon2 joins
14:15:44Mateon1 quits [Ping timeout: 252 seconds]
14:15:44Mateon2 is now known as Mateon1
14:35:10Meli quits [Ping timeout: 252 seconds]
14:37:07Meli (Meli) joins
14:55:31Barto quits [Ping timeout: 252 seconds]
14:59:35hitgrr8 joins
15:03:36<@JAA>I'm getting around a billion years with the current Bitcoin network hash rate of ~400 EH/s. Depends a bit on what 'symbols' means exactly, of course.
15:04:38<@JAA>With 10 symbols: 72**20/4e20/3.1415e7 = 1.12B years
15:07:30<@JAA>Oh yeah, and that's just one SHA1 iteration, which nobody ever uses for PBKDF. The iteration count will be at least on the order of 10k in practice unless it was created on a potato CPU.
15:08:07<@JAA>Er wait no, Bitcoin uses SHA-256, doesn't it? Anyway, same difference, the hash functions don't vary that much in speed.
15:21:10<anarchat>yeah, it's a lower limit i think, right?
15:21:33Church (Church) joins
15:21:44DiscantX quits [Ping timeout: 252 seconds]
15:22:26<@JAA>Yeah, in practice, it'll be in the trillions of years.
15:23:25<@JAA>But in general, if it takes more than twice my life expectancy with overwhelming probability, like five 9s or something, that's more than sufficient.
15:25:39DiscantX joins
15:46:02VerifiedJ quits [Quit: The Lounge - https://thelounge.chat]
15:46:31VerifiedJ (VerifiedJ) joins
15:58:46benjins quits [Ping timeout: 252 seconds]
18:19:01DiscantX quits [Ping timeout: 252 seconds]
18:23:00DiscantX joins
18:31:01benjins joins
18:31:06Barto (Barto) joins
19:14:41Barto quits [Client Quit]
19:14:47Barto (Barto) joins
20:06:09AK quits [Remote host closed the connection]
20:06:51AK (AK) joins
20:21:04hitgrr8 quits [Client Quit]
20:27:17BearFortress_ quits [Client Quit]
20:31:01Barto quits [Ping timeout: 252 seconds]
20:51:42katocala quits [Remote host closed the connection]
21:01:40Barto (Barto) joins
21:36:29katocala joins
22:30:13BlueMaxima joins

HomeSearchPrevious dayNext day