Timeline for Use brute force to mitigate brute force
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 12, 2017 at 6:36 | comment | added | forest | While @TildalWave is certainly right, it is a useful evasion technique used by malware, since the key will be nowhere in the binary itself. | |
| Apr 1, 2013 at 16:54 | history | tweeted | twitter.com/#!/StackSecurity/status/318768312584642560 | ||
| Apr 1, 2013 at 14:10 | vote | accept | Billy Moon | ||
| Apr 1, 2013 at 13:41 | comment | added | TildalWave | The problem with your code is that your server-side brute force function needs somewhere between 1 and 17576 iterations to exit successfully (has variable cost). This is not anything like how some inherently slow KDFs that @TerryChia mentioned in his answer function, by introducing a known and non-variable cost to using them. | |
| Apr 1, 2013 at 12:38 | review | First posts | |||
| Apr 1, 2013 at 12:53 | |||||
| Apr 1, 2013 at 12:27 | answer | added | user10211 | timeline score: 10 | |
| Apr 1, 2013 at 12:21 | history | asked | Billy Moon | CC BY-SA 3.0 |