Talk:RC5

Cryptography: Computer science Low‑importance

	This article is within the scope of WikiProject Cryptography, a collaborative effort to improve the coverage of Cryptography on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.CryptographyWikipedia:WikiProject CryptographyTemplate:WikiProject CryptographyCryptography articles
Low	This article has been rated as Low-importance on the importance scale.
	This article is supported by WikiProject Computer science (assessed as Low-importance).

Time to crack 72-bit key

"At the current rate, it will take approximately 120 years to test every possible remaining key, and thus guarantee completion of the project.[4]"

I checked their home page and it says "This also means that we'll hit 100% in 87,428 days at yesterday's rate." As 87,424 days = 240years I think the Wikipedia article is wrong. It should take approximately 120 years before the cipher is broken (because you will statistically only have to test 50% of the keys) or 240 years to check test every possible remaining key, right? /Inuit77

http://stats.distributed.net/projects.php?project_id=8 — Preceding unsigned comment added by Inuit77 (talk • contribs) 13:59, 30 January 2014 (UTC)[reply]

I changed it. It's correct already in https://wiki.riteme.site/wiki/Password_strength Bit strength threshold /Inuit77 — Preceding unsigned comment added by Inuit77 (talk • contribs) 15:02, 30 January 2014 (UTC)[reply]

Or maybe just fewer people are running distributed.net these days? -- intgr [talk] 02:14, 31 January 2014 (UTC)[reply]