I don't feel likely to get much out of typing (+ 2 2) and getting 4 in a web REPL. What I want is a 1-page writeup with basics about the implementation: Lisp dialect, implementation strategy, special features and limitations, how the concurrency works, resource requirements, source code SLOC, stuff like that. It's ok for the writeup to assume I'm familiar with Lisp. I looked at the web site for a few seconds and the home page was almost entirely uninformative. I didn't try reading the documentation but might look at it later.
The home page of ulisp.com isn't exactly what I want either, but it's a lot closer.
I expect typical smart cards like the one in your credit card are harder to crack than the raspberry pi was. Those cards are (or were) also used in TV set-top boxes and back in the day, there was a decades-long arms race between the chip makers and cable TV pirates. The TV pirates were also willing to make large expenditures to crack the chips so they could clone them and sell the clones. There's more about this in Ross Anderson's book "Security Engineering".
I've also heard that the Google Titan security enclave chip (used in Pixel phones) is very hard to crack. Apple has something similar for Iphones, I believe.
A Yubikey is basically a single chip and a bunch of plastic. At their $50 price point, there's plenty of room for some chip manufacturer to skim off a couple of dollars per chip to add an additional metal layer for a tamper protection mesh, and some other gizmos.
Nice, thanks. I had wondered whether the $250K in lab gear is something that a serious HW security lab would already have on hand, as opposed to specialized expenditure for just this attack. I mean I rode in a $250K(?) motor vehicle a few days ago (the #2 SF Muni bus towards the Marina) but I didn't have to spend a lot to ride it, since it was already deployed. Nobody had to go out and buy it.
Who is "we" and while pacing is good, I'm way more uncomfortable with the frontier being controlled by a few companies that managed to predatorially gobble all the world's human-created work as training data, before everything got throttled to stop that scraping. We need open training and open models.
I only see one picture, the Klein bottle on the front page. Are there more? Maybe it's my browser settings or something like that. Firefox 140.14.0esr. Thanks!
Oh I see, never mind! You have to use the "preset" pulldown to select different surfaces. I wonder how feasible it would be for other people to add new ones!
FFT multipoint evaluation is great when you know all the evaluation points in advance. However, for many practical applications the input is only streamed to you. E.g. a polynomial hash for a hashmap. Or preprocessing the taylor approximation of exp(x) for a standard library.
reply