511–520 of 526 posts
Earlier quoted context omitted.
I suggest Zen browser (fork of FF), it feels closer to chrome.
In a good way?
Earlier quoted context omitted.
I suggest Zen browser (fork of FF), it feels closer to chrome.
I hear about Zen. Random q: It can’t trick Canva into letting you use the color picker, or otherwise enable it, can it - if someone happens to know? (What a dumb feature to be locked to the Googlesphere.)
Let's take a moment to talk about the monetary value of this vulnerability. According to the Chrome release page ( https://chromereleases.googleblog.com/2026/09/stable-channel... ), Google paid a researcher $1000 for ethically reporting this. The CVE associated with it (CVE-2026-85046) is already being exploited in the wild. If we put our thinking caps on, how much do you think this vulnerability is actually worth? H…
- for developers: don't report, it's not worth it
- for users: Google does not care about security as it doesn't pay for reporting (enough).
Earlier quoted context omitted.
JIT bugs like this are not easily solved simply by writing a browser in a typesafe language. Here's the commit that fixes this issue: https://chromium.googlesource.com/v8/v8/+/e0562d87ad9c17042b...
If including JIT in a system renders its developer incapable of guaranteeing memory safety, then perhaps that developer’s approach to JIT is not yet mature enough to ethically distribute to non-technical consumers who are not positioned to evaluate that their security is being traded off by the developer on their behalf. We’re past the era where security issues emanating from memory-unsafe code were tolerated due to…
But if I'm wrong, dare say, how would you write a production memory-safe JIT compiler today?
Just outta curiosity because I can't find it at a cursory look - what exactly would be the type (coersion?) that would allow v8 to execute arbitrary code? Is this like something in post data to nodejs that terminates early and is able to run exec or something, like unto a sql injection?
The Chromium issue is not public yet, so let's go with a very simple example. Let's say that you have a type confusion bug that (in terms of the interpreted language) allows you to use an Integer variable as an Array. That sounds nonsensical when just considering the high-level language, but your computer is going to need something to work with when running a script. For an Integer variable it will for example store…
What's an actual snippet of pseudo-JS that could make the engine overrun its memory and start reading out of arbitrary addresses, even within the sandbox? Wouldn't that have been accounted for in the most basic design?
Earlier quoted context omitted.
I'm just saying it's more evidence that Google should be broken up.
How would you break up Google that would make browsers more secure?
Microsoft was sued by the USDOJ in 1998 precisely for this, that it was leveraging the pre-installation of Windows to force Internet Explorer to be the default browser for PC consumers. That that was bad for both security and for the web seems pretty obvious in retrospect, when you think about the trajectory of IE.
Apple's insistent blocking of non-webkit web engines, including V8, on its own hardware/iOS is an even more egregious and dangerous phenomenon.
Browser security and browsers themselves would be vastly improved if they weren't a monopoly of the two mobile OS makers.
Earlier quoted context omitted.
Google is the answer to an Internet that largely blocks ads and uses backdoors to circumvent pay walls. A single massive pillar with enough surface area to carry all the dead weight. If people want a better internet, they can start fostering one, rather than endlessly complain that someone else should be fostering it for them. There will probably be upwards of 1000 people who read this comment that have used Google s…
Google is routinely buying and destroying competitors. They lower prices to kill competition en-masse. They promote their own products in search and elsewhere over paid ads. Search Engine have chicken and egg problem, you can only have a good search if enough people use it to tune the ranking and see enough search spam cases. “Just compete with a monopoly on their own field with one hand tied behind”
They don't need to do anything adversarial, the greed driven mindset of the internet (ads suck, everything should be free) staves off any real competition.
Earlier quoted context omitted.
If including JIT in a system renders its developer incapable of guaranteeing memory safety, then perhaps that developer’s approach to JIT is not yet mature enough to ethically distribute to non-technical consumers who are not positioned to evaluate that their security is being traded off by the developer on their behalf. We’re past the era where security issues emanating from memory-unsafe code were tolerated due to…
You're just offering non-helpful ivory tower criticism without even understanding the problem space (which is actually one of the hardest open research problems in software engineering, cs.PL + formal methods). But if I'm wrong, dare say, how would you write a production memory-safe JIT compiler today ?
Security is where the rubber hits the road. It's whether customers' identities get stolen. It's whether leaders of undemocratic countries can monitor communications, locations, and social networks of people whom they oppress.
Calling this an "ivory tower" criticism is, ironically, a lack of acknowledgement of reality and that our actions have consequences to others.