Timeline for What stops a malicious user from hitting an endpoint with falsified data from the console of a webpage?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4 at 9:46 | comment | added | Martijn | My approach: ALL data from a client wants to hack/infect/mess with you! And if it didnt, you were just lucky :) | |
| Mar 1 at 23:45 | comment | added | Bob | As an addendum, any data generated by the server can only be trusted if it has stayed within the server or has been signed. If you send it out to the client and then round trip it back to the server, it can no longer be trusted (unless signed) since it could be modified during that trip. | |
| Mar 1 at 20:58 | vote | accept | temporary_user_name | ||
| Mar 1 at 16:44 | comment | added | gidds | “never trust user input” — this deserves to be in bold, capitalised, and in as large a typeface as possible! | |
| Mar 1 at 8:24 | vote | accept | temporary_user_name | ||
| Mar 1 at 8:24 | |||||
| Mar 1 at 7:32 | history | answered | Ja1024 | CC BY-SA 4.0 |