Timeline for Security of API Keygen for a cryptocurrency trading platform
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2014 at 13:21 | comment | added | Gareth Rees |
+1, except for "a SHA-256 of any word processing document would do". If an attacker got access to your word processing documents, they could then find the key. It would be better to use a secure source of random numbers, such as /dev/random.
|
|
| Jan 24, 2014 at 21:59 | comment | added | bumperbox | That is a great explanation you put together, you made it very simple and easy to understand | |
| Jan 24, 2014 at 20:56 | history | edited | 200_success | CC BY-SA 3.0 |
Clarified the meanings of "ramdom" and "secure".
|
| Dec 31, 2013 at 1:58 | vote | accept | r3wt | ||
| Dec 30, 2013 at 10:24 | history | edited | 200_success | CC BY-SA 3.0 |
separated $id and rand() out of paranoia that the beginning of the random number could look like a user ID
|
| Dec 30, 2013 at 9:59 | history | edited | 200_success | CC BY-SA 3.0 |
added note about accidental collisions
|
| Dec 30, 2013 at 9:44 | history | answered | 200_success | CC BY-SA 3.0 |