Timeline for Are there standardized ways of generating wallets from passphrases?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2019 at 13:37 | answer | added | John C. | timeline score: -1 | |
| Apr 22, 2015 at 18:21 | answer | added | Nick ODell | timeline score: 1 | |
| Apr 22, 2015 at 18:21 | history | edited | Nick ODell |
edited tags
|
|
| Jan 8, 2014 at 21:36 | comment | added | Steven Roose | I think you don't understand what I mean here. BF is done by guessing. Smart hackers can reduce the amount of guesses required by using dictionaries etc. But that's beside my point. If a hash is used that takes an average computer 1 second to compute instead of less than a millisecond like MD5 or SHA256, even the smartest crackers won't be able to do it within reasonable time. | |
| Jan 8, 2014 at 13:46 | comment | added | T9b | Suggest you read this... arstechnica.com/security/2013/05/… | |
| Jan 8, 2014 at 12:26 | comment | added | T9b | I think you have completely misunderstood the scope of "brute-force" attacks. You are limiting your understanding to "trying to reverse a hash" which is, of course, very difficult. However bitcoin addresses are being compromised all the time, by people who assume that the hash is providing the security on a passphrase. The best example of this is brain wallets, which are being compromised all the time by brute-force attacks using a dictionary of possible phrases. The hash doesn't make them secure. | |
| Jan 7, 2014 at 16:28 | comment | added | Steven Roose | Not everything is in the same way subject to a brute-force attack. F.e. Bitcoin addresses could also be brute-forced, but we don't see that as a threat either because it is not feasible for someone to try to brute-force it. | |
| Jan 7, 2014 at 16:26 | comment | added | Steven Roose | @T9b In fact a the hash can provide the security. In this case, a hash method that is so resource-intensive that brute-forcing would be infeasible would profile the perfect security. An example is the AES 256 CBC encryption method, which is proven to be secure against brute-forcing because of the computational complexity. | |
| Jan 7, 2014 at 14:27 | comment | added | T9b | Except that now I know you've double hashed, all I have to do is double hash every phrase in my book and compare the result, which will always be the same. It's not the hash that is the security - don't confuse these two issues. | |
| Jan 6, 2014 at 15:48 | answer | added | T9b | timeline score: -1 | |
| Jan 4, 2014 at 21:53 | comment | added | John T | Double hashing should be the minimum good to generate wallets. | |
| Jan 3, 2014 at 21:49 | history | asked | Steven Roose | CC BY-SA 3.0 |