Timeline for Source code as password
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2015 at 8:15 | review | Low quality posts | |||
| Apr 11, 2015 at 8:54 | |||||
| Apr 11, 2015 at 0:28 | comment | added | Jorge Leitao | @Tom, your assumption is that preposition A: "it is a good password because few people use it" will not lead to preposition B: "because it is a good password, many people will use it". IMO that assumption is not often the valid. | |
| Apr 10, 2015 at 21:50 | comment | added | Tom | @Chloe I can't find a part that says my assumption is wrong? | |
| Apr 10, 2015 at 21:44 | comment | added | Chloe | arstechnica.com/security/2013/10/… | |
| Apr 10, 2015 at 15:52 | comment | added | Tom | If people globally know that you're using programming languages as password, it is of course not that safe anymore. You could prevent this by putting a password in the code but then we're back to square one. | |
| Apr 10, 2015 at 14:45 | comment | added | S.L. Barth is on codidact.com | I'm not the downvoter, but: if this catches on, scripts will be added to rainbow tables soon enough. | |
| Apr 10, 2015 at 12:52 | comment | added | Tom | Why downvoted?? | |
| Apr 10, 2015 at 12:39 | history | answered | Tom | CC BY-SA 3.0 |