Originally Posted by Ilium Software
|
Actually the 'broken' part refers to a flaw that eWallet doesn't suffer from. As long as you select a good password 256 bit RC4 encryption would take something in the area of 20,000 years to hack by brute force.
And the difference between 40 bit and 256 bit is astronomical since it is an exponential increase in security. I agree that there are stronger means of encryption but quite frankly, unless you are under the serious threat of a major government attempting to hack your wallet, it is simply overkill.
And yes, in the end it all comes down to a good password.
Marc Tassin
Ilium Software
--------------------
marc@iliumsoft.com
+1 (734) 973-9388
---------------------
http://www.iliumsoft.com
And be sure check out our new blog! http://blog.iliumsoft.com/
|
While it may provide a good security today, think of someone obtaining your wallet file, e.g. on a lost backup CD, & trying to break it with computers and tools available 10-15 years from now. Some information (SSN, some bank accounts, retirement accounts) is still going to be relevant. Of course the chances are very slim but... it's better to be paranoid than sorry. I would, at any given point, use only the strongest algorhytm currently available. ( IIRC that older version of eWallet used something like RC64)
Now in my case switching from eWallet to KeePass was also a features vs. memory use choice.