It's not that complex once you have formulas for computing square roots. I've recently implemented it in TypeScript using bigints for browsers & nodejs. Quite readable & performant. See index.ts file here: https://github.com/paulmillr/noble-ed25519
Wish ristretto folks added the library to their website though.
It's fair to say that this is still a theoretical attack. As authors of this paper mentioned, they don't see a way of turning the "flaw" into a real exploit.
Back then I failed. It seemed like Chrome didn’t exposed full console and window api to extensions or so. I doubt things have changed since then. But i’ll try anyway.
I had also advocated for improving built-in Safari web inspector, to make it expose reasonable APIs for extensions like this (radar issue #11653556). Unfortunately, without any result.
As i’ve noticed in repository readme, Chrome coffeescript addons cannot
manipulate DOM or play nicely (or even reasonably) with window properties. They’re just shortcuts for coffeescript.org, which just compiles coffee down to JS. This seems useless to me, because I want coffeescript as first-class browser citizen.
You put vendor styles / scripts in `vendor`, then you edit your `app` files. No matter what language you want to write, brunch will compile it on `brunch watch` or `brunch build`.
Of course you can make some sophisticated makefiles and connect sophisticated file watchers there (brunch fastly rebuilds project on every small change), but why do this when there's brunch which just works?
Wish ristretto folks added the library to their website though.