Timeline for How long it will take to crack a RAR password?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2015 at 21:55 | comment | added | CodesInChaos | @kasperd 95 bits of entropy + 17 bits of iterated hashing = 112 bits of security. See my answer. | |
| Oct 31, 2015 at 21:46 | comment | added | kasperd | @CodesInChaos 16 characters chosen among all the alphanumeric characters in ASCII gives you around 95 bits of entropy not 112. | |
| Mar 27, 2013 at 4:51 | history | tweeted | twitter.com/#!/StackSecurity/status/316774346792267776 | ||
| Mar 26, 2013 at 20:18 | vote | accept | ilhan | ||
| Mar 26, 2013 at 18:32 | comment | added | Saladin | @Xander okay i was thinking somewhere along the lines of a static file kept on a secure server (without any copies rights) which the attacker is trying to bruteforce. If it has been already copied (e.g in usb) then you are right, it wouldn't have any effect. Thanks for clarifying. | |
| Mar 26, 2013 at 18:27 | comment | added | Xander | @Saladin A password-change policy wouldn't actually have any effect at all, since we're talking about a password on a file. At any given point in time the file has a password that can't be invalidated if the file is copied, so the frequency with which it is changed is immaterial to the feasibility of a brute-force attack. | |
| Mar 26, 2013 at 18:23 | answer | added | CodesInChaos | timeline score: 11 | |
| Mar 26, 2013 at 18:22 | comment | added | Saladin | With a policy which mandates a password change every one week , now top this with what @CodesInChaos said its just become very impractical. | |
| Mar 26, 2013 at 18:10 | comment | added | CodesInChaos | If you mean 16 completely random alphanumeric characters, then it's infeasible even for state level adversaries. I'd estimate a ~112 bit security level, which should be good for several decades. | |
| Mar 26, 2013 at 18:08 | history | asked | ilhan | CC BY-SA 3.0 |