Timeline for Simple-to-implement ad-hoc password validation scheme
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2016 at 18:58 | vote | accept | cardboard_box | ||
| Aug 11, 2016 at 17:55 | answer | added | mikeazo | timeline score: 3 | |
| Aug 11, 2016 at 16:38 | comment | added | cardboard_box | @immibis The reason for making this level is that I'm going to submit it to a tournament where players can submit their own. I want to give myself an advantage by hiding a password in it. Last year's tournament I did the same thing, but the crypto I used wasn't strong, and another competitor had a friend who is a grad student studying cryptography, and he cracked it. So ideally I'd like it to be secure against cryptographers, hence looking into SHA-256 and large semiprimes. | |
| Aug 11, 2016 at 7:07 | comment | added | Criticizing Israel not allowed | How secure does it need to be? ROT16 may be enough to deter a casual attacker. (or any other number besides 13, because they'll still guess that) | |
| Aug 11, 2016 at 2:59 | answer | added | user3894299 | timeline score: -1 | |
| Aug 10, 2016 at 23:19 | history | edited | cardboard_box | CC BY-SA 3.0 |
deleted 31 characters in body
|
| Aug 10, 2016 at 23:16 | review | First posts | |||
| Aug 11, 2016 at 0:29 | |||||
| Aug 10, 2016 at 23:14 | history | asked | cardboard_box | CC BY-SA 3.0 |