Timeline for How to generate a seed safely?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2018 at 17:35 | history | edited | aboose♦ | CC BY-SA 3.0 |
added 6 characters in body
|
| Jan 10, 2018 at 11:30 | comment | added | blockmined | Method with Keypass on PC is valid also on Linux platform with KeePass 2.X. | |
| Jan 10, 2018 at 7:47 | history | edited | aboose♦ | CC BY-SA 3.0 |
added 316 characters in body
|
| Nov 29, 2017 at 19:07 | comment | added | Laurence |
To expand on aboose's response, it was because the PowerShell script that people were using contained the Get-Random command. This command is not intended to generate cryptographically secure randomness as it has just 2,147,483,647 starting states/seeds. So all an attacker needed to do was run through all 2^31-1 of these seeds to find all IOTA seeds generated by it.
|
|
| Nov 29, 2017 at 0:25 | comment | added | aboose♦ | Hi Scott - it was found that the powershell method seems to be not fully random, and is more likely to give out certain outputs. People trying to exploit this have a list of common seeds that it gives out, and will be likely to check those and empty you out if you use it. | |
| Nov 28, 2017 at 22:52 | comment | added | Scott Cooper | Can you elaborate on "The PowerShell method has been demonstrated to be insecure. Do not use it." | |
| Nov 28, 2017 at 19:54 | history | answered | aboose♦ | CC BY-SA 3.0 |