this post was submitted on 28 Jan 2025
277 points (97.3% liked)
Technology
61203 readers
4603 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Speculative execution seems to be the source of a lot of security flaws in many different CPUs. CPU manufacturers seem to be so focused on winning the performance race that security aware architecture design takes the backseat.
Also, it's more and more clear that it's a bad idea that websites can just execute arbitrary code. The JS APIs are way too powerful and complex nowadays. Maybe websites and apps should've stayed separate concepts instead of merging into "web apps".
I also wonder if it'd be possible to design a CPU so vulnerabilities like these are fixable instead of just "mitigable". Similar to how you can reprogram an FPGA. I have no clue how chip design works though, but please feel free to reply if you know more about this.
Fast for the benchmarks. "We'll make it slower and safer later."
Take a look at ARM Morello and CHERI.
Javascript in general was a mistake, and always has been.
The web should've had Scheme or Python instead. Or better yet, we shouldn't have given up so quickly on Java Web Start because then we could've had proper web applications with their own windows and native UIs and such.
Damn straight!
Oh no, not python!
Being a Linux user I really like everything being ran in the browser. What if we just have more control of which JS APIs can be used? On a site by site bases. Which I assume can probably already be done with extensions.
Some browsers such as cromite disable JIT compilation and WebAssembly by default. Allowing you to opt-in to enable these features on a site by site bases.
JIT and WebAssembly have been the source of many high profile CVE in browser recently including the one mentioned in the post (well, this one is on Safari's Chrome).
relevant research