Timeline for My first random password generator
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2019 at 15:35 | history | edited | Roland Illig | CC BY-SA 4.0 |
added 3 characters in body
|
| Oct 2, 2019 at 15:02 | comment | added | Baldrickk | Do you mean "without" in the first line? | |
| Oct 2, 2019 at 5:30 | history | edited | Roland Illig | CC BY-SA 4.0 |
added 4 characters in body
|
| Oct 2, 2019 at 3:16 | comment | added | SilverbackNet | That's an excellent point; creating a contract where one doesn't need to exist is a bad idea. Expect callers always forget and leak memory, or worse use the wrong kind of free, even if you tell them to call deallocate_password(). That said, for security reasons requiring a call to wipe the password from memory might be necessary. | |
| Oct 1, 2019 at 22:23 | history | answered | Roland Illig | CC BY-SA 4.0 |