Timeline for Is using PBKDF2 good protection against brute-force attacks on web application login pages?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2023 at 20:11 | history | edited | user63458 | CC BY-SA 4.0 |
> readability
|
| Oct 29, 2020 at 18:13 | history | edited | user63458 | CC BY-SA 4.0 |
added 11 characters in body
|
| Oct 29, 2020 at 18:00 | history | edited | user63458 | CC BY-SA 4.0 |
added 32 characters in body
|
| Oct 29, 2020 at 15:14 | vote | accept | Silvercroft | ||
| Oct 29, 2020 at 7:25 | history | edited | user63458 | CC BY-SA 4.0 |
edited body
|
| Oct 29, 2020 at 6:06 | comment | added | user63458 | @kelalaka I just meant that user credentials travel unchanged to the server, not that they can be sniffed. In any case I have applied the correction, thanks. | |
| Oct 29, 2020 at 6:05 | history | edited | user63458 | CC BY-SA 4.0 |
correction from comment
|
| Oct 28, 2020 at 17:52 | comment | added | kelalaka | Where do you know that the server-client doesn't use TLS to hide the communication? Your second sentence is completely wrong. As long as the database is not hacked it is an online attempt to hack the passwords by trials. | |
| Oct 28, 2020 at 15:04 | history | edited | user63458 | CC BY-SA 4.0 |
added 55 characters in body
|
| Oct 28, 2020 at 14:42 | history | edited | user63458 | CC BY-SA 4.0 |
added 59 characters in body
|
| Oct 28, 2020 at 14:32 | history | edited | user63458 | CC BY-SA 4.0 |
added 116 characters in body
|
| Oct 28, 2020 at 14:24 | history | edited | user63458 | CC BY-SA 4.0 |
added 116 characters in body
|
| Oct 28, 2020 at 14:18 | history | answered | user63458 | CC BY-SA 4.0 |