Timeline for Cracking in progress
Current License: CC BY-SA 3.0
51 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2018 at 19:37 | answer | added | J. Sallé | timeline score: 1 | |
| Oct 15, 2018 at 6:53 | answer | added | Max Yekhlakov | timeline score: 1 | |
| Nov 30, 2016 at 9:37 | vote | accept | Dada | ||
| Nov 28, 2016 at 5:52 | answer | added | Tyler MacDonell | timeline score: 0 | |
| Nov 27, 2016 at 11:08 | answer | added | steenbergh | timeline score: 0 | |
| Nov 27, 2016 at 10:04 | answer | added | hdrz | timeline score: 1 | |
| Nov 25, 2016 at 14:56 | history | edited | Dada | CC BY-SA 3.0 |
added 50 characters in body
|
| Nov 25, 2016 at 14:56 | comment | added | Dada | @Soapy you can print it, or not, it's up to you. | |
| Nov 24, 2016 at 17:26 | comment | added | Soapy |
@Dada does the last line printed need a \n at the end?
|
|
| S Nov 24, 2016 at 2:38 | history | edited | user62131 | CC BY-SA 3.0 |
Escaped ! so that it doesn't get interpreted by the shell
|
| S Nov 24, 2016 at 2:38 | history | suggested | Dessa Simpson | CC BY-SA 3.0 |
Escaped ! so that it doesn't get interpreted by the shell
|
| Nov 24, 2016 at 2:33 | review | Suggested edits | |||
| S Nov 24, 2016 at 2:38 | |||||
| Nov 23, 2016 at 22:32 | answer | added | Adám | timeline score: 3 | |
| Nov 23, 2016 at 11:32 | answer | added | Soapy | timeline score: 1 | |
| Nov 23, 2016 at 11:23 | answer | added | onin | timeline score: 0 | |
| Nov 22, 2016 at 23:52 | answer | added | Olivier Grégoire | timeline score: 2 | |
| Nov 22, 2016 at 21:57 | comment | added | Mad Physicist | You need single quotes around the last input string because it has an exclamation mark, at least in bash. | |
| Nov 22, 2016 at 20:55 | answer | added | Mwr247 | timeline score: 3 | |
| Nov 22, 2016 at 19:42 | history | tweeted | twitter.com/StackCodeGolf/status/801148847166779398 | ||
| Nov 22, 2016 at 18:58 | history | edited | Dada | CC BY-SA 3.0 |
Removed the last part that seemed confusing
|
| Nov 22, 2016 at 18:57 | comment | added | Dada | @GabrielBenamy I didn't golf it too much on purpose so Perl golfers can participate too. Thanks for pointing out the bad spelling of "Cracking" | |
| Nov 22, 2016 at 18:52 | comment | added | Gabriel Benamy |
You can save 1 byte on your code by changing while($t==time) to until($t-time). Also you spelled "Cracking" incorrectly in your argument.
|
|
| Nov 22, 2016 at 17:28 | answer | added | Angs | timeline score: 4 | |
| Nov 22, 2016 at 15:50 | answer | added | Kevin Cruijssen | timeline score: 5 | |
| Nov 22, 2016 at 15:16 | answer | added | nmjcman101 | timeline score: 6 | |
| Nov 22, 2016 at 14:27 | answer | added | matsjoyce | timeline score: 3 | |
| Nov 22, 2016 at 13:35 | answer | added | SuperJedi224 | timeline score: 1 | |
| Nov 22, 2016 at 13:04 | answer | added | Osable | timeline score: 10 | |
| Nov 22, 2016 at 11:19 | answer | added | Neil | timeline score: 28 | |
| Nov 22, 2016 at 11:00 | answer | added | SolveEverythingWithPython | timeline score: 3 | |
| Nov 22, 2016 at 10:55 | answer | added | paldir | timeline score: 1 | |
| Nov 22, 2016 at 10:43 | comment | added | Dada | @Tom I don't mind glitches, so I'm going to say no. (it adds unnecessary complexity, it would invalidate most answers, etc.) | |
| Nov 22, 2016 at 10:29 | comment | added | Tom | Shouldn't you include in the rules that the random characters should not be the actual character in that place ? Otherwise random strings can match the password given, but the search goes on, which movie buffs would rate as a glitch. | |
| Nov 22, 2016 at 10:09 | comment | added | Dada | @IporSircer you can consider that the maximum length of the input is 30 if it helps. | |
| Nov 22, 2016 at 10:08 | history | edited | Dada | CC BY-SA 3.0 |
added 141 characters in body
|
| Nov 22, 2016 at 8:16 | answer | added | Billywob | timeline score: 4 | |
| Nov 22, 2016 at 7:11 | answer | added | Ipor Sircer | timeline score: 8 | |
| Nov 22, 2016 at 6:02 | comment | added | Ipor Sircer | What is the max. length of password? | |
| Nov 22, 2016 at 3:00 | answer | added | Oliver Ni | timeline score: 7 | |
| Nov 22, 2016 at 2:58 | answer | added | milk | timeline score: 4 | |
| Nov 22, 2016 at 2:17 | answer | added | R. Kap | timeline score: 4 | |
| Nov 22, 2016 at 1:56 | answer | added | ETHproductions | timeline score: 20 | |
| Nov 21, 2016 at 23:42 | comment | added | Dada | @JonathanAllan Actually the random generation doesn't crack the password, but just outputs random characters. So no, you can't stop earlier. | |
| Nov 21, 2016 at 23:40 | comment | added | Jonathan Allan | If the random generation happens to crack the password earlier is it alright to stop at that point? | |
| Nov 21, 2016 at 23:32 | answer | added | Luis Mendo | timeline score: 4 | |
| Nov 21, 2016 at 23:13 | history | edited | Dada | CC BY-SA 3.0 |
added 138 characters in body
|
| Nov 21, 2016 at 23:12 | comment | added | Dada |
@ais523 \n is perfectly acceptable. The version with \r is just here because it looks better, but you don't need those \r.
|
|
| Nov 21, 2016 at 23:10 | comment | added | user62131 |
Is it mandatory to separate the lines of output with \r (making them all replace each other onscreen like in the animation), or is \n acceptable?
|
|
| Nov 21, 2016 at 23:10 | answer | added | Maltysen | timeline score: 3 | |
| Nov 21, 2016 at 23:07 | comment | added | JungHwan Min | Like this scene from the movie War Games? | |
| Nov 21, 2016 at 22:57 | history | asked | Dada | CC BY-SA 3.0 |