Artiom Chilaru

After spending a bunch of time (way more than I should have today), I have traced the issue to Crypto_Scrypt library so far. I'm not sure if it's this library,...

Ok, got some further progress on it. I've narrowed it down to the scrypt library, and managed to replicate it with minimal code. Since no other library is required to...

That's indeed the case, @scintill. Basically, I think Safari (not sure if it's limited to v6 or not) has some strange "optimisation" for javascript, which is causing a bunch of...

Great job pointing it out! By the way, it's enough putting `try/catch` blocks only around the `salsa20_8()` method.. It's still considerably slower (10sec vs 60sec on my machine), but it...

One disappointing thing to note is that it's not a bug in the javascript code, but instead a bug in the browser's execution of the code. That is to say...

The problem is - I'm not really sure where Safari messed up right there - it's definitely an issue, but replicating it on any other browser is a whole different...

I should probably note that Safari 6.05 was indeed behaving incorrectly (hence you can't decode your wallet now), but in a consistent manner. So to decode your wallet, you'd just...

There's nothing really that we could do at this point. It's a bug in an older version of Safari, and there's no way to port the broken code to newer...

I said "no way to port the broken code" because it's no easy task. It's possible in theory, but as far as I know there has been no success so...

Confirmed here too, also with BazaarGuard and OBCentral.. Worked with some others