Timeline for Random Password Generator
Current License: CC BY-SA 3.0
55 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2021 at 12:55 | answer | added | EacyCoding | timeline score: 1 | |
| Jun 25, 2015 at 14:34 | answer | added | user3464592 | timeline score: 1 | |
| Dec 7, 2014 at 9:56 | comment | added | Iszi | @CodesInChaos I don't see why a true RNG is required to create all possible passwords. To generate all possible passwords with equal probability, yes. But (unless I'm misunderstanding something) the PRNG limitation you describe does not preclude one from meeting the requirements specified above. Certainly, you could not generate all possible passwords from a single output of the PRNG. But if every character was individually generated according to separate PRNG outputs, as is done in my answer (and I'm sure some others), you need a very small fraction of that 32-bit PRNG space. | |
| Jan 12, 2014 at 22:17 | vote | accept | Hand-E-Food | ||
| Jan 9, 2014 at 16:27 | answer | added | Gx1sptDTDa | timeline score: 0 | |
| Jan 9, 2014 at 16:26 | answer | added | user3175123 | timeline score: 1 | |
| Jan 9, 2014 at 15:13 | answer | added | Oberon | timeline score: 1 | |
| Jan 9, 2014 at 13:35 | answer | added | craesh | timeline score: 0 | |
| Jan 9, 2014 at 5:38 | answer | added | Iszi | timeline score: 2 | |
| Jan 8, 2014 at 9:40 | answer | added | Gaslight Deceive Subvert | timeline score: 1 | |
| Jan 8, 2014 at 9:18 | answer | added | Rik | timeline score: 0 | |
| Jan 8, 2014 at 8:27 | answer | added | madoke | timeline score: 1 | |
| Jan 8, 2014 at 6:48 | answer | added | Joe | timeline score: 2 | |
| Jan 7, 2014 at 10:17 | answer | added | Michael | timeline score: 0 | |
| Jan 7, 2014 at 10:13 | answer | added | Cezar Moise | timeline score: 0 | |
| Jan 6, 2014 at 17:24 | answer | added | Joachim Isaksson | timeline score: 1 | |
| Jan 6, 2014 at 16:03 | answer | added | Joachim Isaksson | timeline score: 4 | |
| Jan 6, 2014 at 15:40 | answer | added | Dom Hastings | timeline score: 1 | |
| Jan 6, 2014 at 15:05 | comment | added | o0'. | @xfix I wouldn't even dare put the word "safe" near to such a broken password system. Firing the security guys should not be enough for such a mistake, you should also fire the guy who hired them. | |
| Jan 6, 2014 at 14:59 | comment | added | Martin Thoma | @EthanBolker: Well, I guess that is now ok. It would be quite difficult to check if it really is with equal probability. And probably the only solutions that would come out of this would be "generate and test" ones. | |
| Jan 6, 2014 at 14:53 | comment | added | Ethan Bolker | You haven't really answered @moose by requiring that all passwords be generatable. They should appear with equal probability. | |
| Jan 6, 2014 at 14:16 | answer | added | Joachim Isaksson | timeline score: 1 | |
| Jan 6, 2014 at 14:15 | comment | added | Cruncher | @CodesInChaos for simplification we can probably assume true rng? | |
| Jan 6, 2014 at 13:08 | comment | added | Carl Witthoft | Just give everyone "Passw@rd1234" . They'll never suspect anyone else has the same password! | |
| Jan 6, 2014 at 12:53 | answer | added | Joachim Isaksson | timeline score: 1 | |
| Jan 6, 2014 at 12:44 | answer | added | Neha Sangore | timeline score: 0 | |
| Jan 6, 2014 at 9:22 | answer | added | Pawelmhm | timeline score: 0 | |
| Jan 6, 2014 at 8:57 | answer | added | Avi | timeline score: 0 | |
| Jan 6, 2014 at 8:51 | comment | added | CodesInChaos | "It must be able to generate all permutations of all allowable characters." If you enforce that rule strictly, most answers will be invalid since the underlying PRNG is too bad. In many languages it's seeded by a 32 bit value which is obviously not enough to generate all possible values of such a complex password. | |
| Jan 6, 2014 at 8:21 | comment | added | null | Well, technically those passwords are safe, but you can be 150% sure that they will be written down by everyone. This reminds me of codegolf.stackexchange.com/questions/6203/security-by-post-it, but it isn't a duplicate (because that one was about verifying). | |
| Jan 6, 2014 at 8:11 | answer | added | Rik | timeline score: 7 | |
| Jan 6, 2014 at 8:09 | answer | added | Zach Leighton | timeline score: -1 | |
| Jan 6, 2014 at 5:59 | answer | added | AmeliaBR | timeline score: 5 | |
| Jan 6, 2014 at 5:46 | comment | added | Jonathon Reinhart |
@MvG Indeed: correcthorsebatterystaple
|
|
| Jan 6, 2014 at 5:45 | comment | added | Grijesh Chauhan | Password Generator (mkpasswd) (Python recipe) | |
| Jan 6, 2014 at 5:15 | comment | added | MvG | The IT guys should be fired, or at least better educated: If you do generate passwords randomly, then restricting the set of permissible passwords to those which include at least one character of each category in fact weakens the passwords, since it reduces the size of the permissible set. And our programs would be that much easier if we didn't have to check for that… OK, don't modify the contest after so many submissions have arrived; it's fine as a challenge. | |
| Jan 6, 2014 at 5:12 | answer | added | vhadalgi | timeline score: 2 | |
| Jan 6, 2014 at 5:02 | history | tweeted | twitter.com/#!/StackCodeGolf/status/420057837918617602 | ||
| Jan 6, 2014 at 4:32 | answer | added | ntalbs | timeline score: 2 | |
| Jan 6, 2014 at 3:55 | answer | added | Eliseo D'Annunzio | timeline score: 3 | |
| Jan 6, 2014 at 3:17 | answer | added | MvG | timeline score: 8 | |
| Jan 6, 2014 at 3:04 | answer | added | Vasili Syrakis | timeline score: 1 | |
| Jan 6, 2014 at 1:41 | answer | added | assylias | timeline score: 13 | |
| Jan 6, 2014 at 1:35 | answer | added | SameOldNick | timeline score: 1 | |
| Jan 5, 2014 at 23:51 | answer | added | DavidC | timeline score: 4 | |
| Jan 5, 2014 at 23:02 | answer | added | IQAndreas | timeline score: 2 | |
| Jan 5, 2014 at 22:57 | history | edited | Hand-E-Food | CC BY-SA 3.0 |
Added rule.
|
| Jan 5, 2014 at 22:53 | comment | added | Hand-E-Food | @moose, agreed. I've added a new rule. | |
| Jan 5, 2014 at 22:52 | history | edited | Hand-E-Food | CC BY-SA 3.0 |
Added rule.
|
| Jan 5, 2014 at 22:37 | answer | added | daniero | timeline score: 13 | |
| Jan 5, 2014 at 22:36 | comment | added | Martin Thoma | You should also demand that all passwords which are allowed appear with the same probability (otherwise I can simply make a 30 characters long list with allowed characters, shuffle it, and give the first 15 ones) | |
| Jan 5, 2014 at 22:27 | answer | added | Martin Thoma | timeline score: 8 | |
| Jan 5, 2014 at 22:27 | answer | added | ybeltukov | timeline score: 29 | |
| Jan 5, 2014 at 22:21 | answer | added | Jonathon Reinhart | timeline score: 4 | |
| Jan 5, 2014 at 22:03 | history | asked | Hand-E-Food | CC BY-SA 3.0 |