Difference between revisions of "Countdown in header text/images"
(→Explanation: no one's guessing future file names) |
|||
Line 9: | Line 9: | ||
***https://xkcd.com/count-wimRikmef/imgs/ac84f99b9c41eb75e1a595ea74c7bccf48f36c345d8b88ad5dd478d4520bc0b2.png | ***https://xkcd.com/count-wimRikmef/imgs/ac84f99b9c41eb75e1a595ea74c7bccf48f36c345d8b88ad5dd478d4520bc0b2.png | ||
*Attempting to brute-force future files, assuming you could test 1 trillion file names per second, would take 200,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 times the age of the universe. | *Attempting to brute-force future files, assuming you could test 1 trillion file names per second, would take 200,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 times the age of the universe. | ||
+ | **When I first looked at it and decided it was an obvious hash (yes SHA256 sounds about right, but nice to know someone's tried it) I personally had hoped it would be a hash of the datetime (plus a salt, maybe, to give it that extra little frisson of difficulty in reverse engineering... ;) ). But if it's as you say I think I'll refrain from getting any rainbow-tables set up and bashing through the possibilities in the rather huge phase-space it could represent. Of course, there must be a look-up table used by the server. It'd be too much to hope for that it's publically exposed though, and totally a rookie-error if it is. (That Randall, and maybe anyone he actually drafted in to implement it to save himself the worry, is surely not going to commit.) [[Special:Contributions/172.70.85.73|172.70.85.73]] 03:32, 13 January 2022 (UTC) | ||
==Images== | ==Images== |
Revision as of 03:32, 13 January 2022
Explanation
- Here are (work in process) all the images from xkcd used in the Countdown in header text.
- The images can also be found here, on munvoseli's page.
- The images have been numbered here on explain xkcd and the number is a link to the image in the count-wimRikmef folder on xkcd.com:
- https://xkcd.com/count-wimRikmef/imgs/
- Each picture's filename is the SHA256 hash of the image itself, so it is impossible to predict future file names:
- Here the name for the first picture: ac84f99b9c41eb75e1a595ea74c7bccf48f36c345d8b88ad5dd478d4520bc0b2.png
- https://xkcd.com/count-wimRikmef/imgs/ac84f99b9c41eb75e1a595ea74c7bccf48f36c345d8b88ad5dd478d4520bc0b2.png
- Attempting to brute-force future files, assuming you could test 1 trillion file names per second, would take 200,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 times the age of the universe.
- When I first looked at it and decided it was an obvious hash (yes SHA256 sounds about right, but nice to know someone's tried it) I personally had hoped it would be a hash of the datetime (plus a salt, maybe, to give it that extra little frisson of difficulty in reverse engineering... ;) ). But if it's as you say I think I'll refrain from getting any rainbow-tables set up and bashing through the possibilities in the rather huge phase-space it could represent. Of course, there must be a look-up table used by the server. It'd be too much to hope for that it's publically exposed though, and totally a rookie-error if it is. (That Randall, and maybe anyone he actually drafted in to implement it to save himself the worry, is surely not going to commit.) 172.70.85.73 03:32, 13 January 2022 (UTC)
Images
Go to bottom
- Just an easy fix making it easy to jump to the newest image here at the bottom of a potentially very long list of pictures.