Funds of every Trust Wallet browser extension could have been stolen
I was writing about this exact problem of bad RNGs in web cryptocurrency wallets a ~decade ago. It is profoundly depressing that so little has changed:<p><a href="https:&#x2F;&#x2F;medium.com&#x2F;mike-hearn&#x2F;type-safety-and-rngs-40e3ec71ab3a" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;mike-hearn&#x2F;type-safety-and-rngs-40e3ec71a...</a><p><i>Browsers have a number of problems that make it difficult to build wallets, but I’m not going to try and convince you to stop making them here. Suffice it to say there are alternatives for writing cross platform wallets you could consider.</i><p>Browsers just aren&#x27;t intended for doing things that require the generation and safe storage of private keys. The developers don&#x27;t care about these use cases. Like with so many others, if you want to do it properly you have to go outside the browser.<p>Back when I was involved with the cryptocurrency world (pre-2016) I kept hitting this general reluctance to just write normal desktop apps, and whenever I advised people to do it for security or stability reasons they&#x27;d insist on writing something browser&#x2F;JS based instead. I did write desktop based wallets, but was considered old fashioned for doing so (at the ripe age of 35). <i>Way</i> too frequently people would end up losing all their money to dumb and entirely predictable hacks as a consequence of using a web-based wallet, or even just lose because of sites going offline. Browsers improved a bit since but as this episode shows, they still aren&#x27;t intended for it.<p>Part of why people wanted to write js was that it is easy to distribute the results. They optimized for developer convenience over security. Chrome offers a portability layer and keeps extensions up to date for you. Years passed and I saw the same problem crop up in other contexts too: the right approach was to write a desktop app, people tried to hack Chrome into compliance instead so they could let it handle distribution, it didn&#x27;t work, and that sometimes led to disaster for their users.<p>These days I have a company that tries to solve this problem. We make Conveyor [1], which has the goal of making desktop app distribution as easy as for a web app. And it mostly succeeds: it can cross-build&#x2F;package apps for every platform, and on Win&#x2F;macOS it can provide update-on-start so you can iterate as quickly as with a web app. You pick your preferred portability layer (flutter, jvm, electron, something rusty etc) and can choose between more battle tested frameworks or more experimental frameworks depending on your appetite for risk. Whatever you pick, the distribution experience is the same. You don&#x27;t have to compromise on UX either. Frameworks like Compose for Desktop, Flutter, heck even JavaFX give you nice solid 60fps animations and can be made to look good easily. You can store private keys in the user&#x27;s secure keystores. If your site goes down it&#x27;s not an emergency, your app still works, only updates stop until you&#x27;re back online. Even if your certificates expire your app will still work!<p>I hope that people will take this stuff more seriously in future. It&#x27;s got a lot easier to distribute apps without relying on browsers or stores over time. Browser developers do a good job but are ultimately constrained by the web&#x27;s origins. It&#x27;s not just cryptocurrency wallets that can benefit from escaping the browser either! Quite a lot of security bugs can be eliminated when you leave the browser. For example you can write apps that are immune by design to XSS, XSRF, SQL injection, phishing and other common bug classes.<p>At some point I should probably write these thoughts down in a more modern blog post.<p>[1] <a href="https:&#x2F;&#x2F;hydraulic.software&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hydraulic.software&#x2F;</a>