Timeline for Source code as password
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2015 at 0:12 | comment | added | Christopher King | The entropy of the attacking method can't be lower than the entropy of your generation method. Therefore having a high entropy generation method gives you peace of mind. | |
| Apr 11, 2015 at 23:45 | comment | added | David Mulder | Not sure you're saying this is a bad idea, but as it prevents all the huge security problems of password managers I guess it's not a bad idea comparing the difficulty to remember to the 'external entropy' even if the 'internal entropy' is quite low. | |
| Apr 11, 2015 at 21:31 | comment | added | isarandi | Exactly. And you can never know whether your shiny new idea is independently (secretly) used by many others, and good password crackers may know much more about the psychology of choosing passwords than you do. Whatever clever trick you use, the attacker may predict it. Therefore you need to disconnect the choice entirely from anything predictable about you (i.e. use randomness). Then even if they correctly predict your decision, they can only conclude that you tend to choose random passwords. | |
| Apr 10, 2015 at 13:02 | history | answered | Philipp | CC BY-SA 3.0 |