I still see it as laziness of design. It goes back to the days when sites required you to use Internet Exploder, er, Explorer... because it followed a different implementation track than Netscape/Mozilla, and IE accepted broken HTML because Internet Insecurity Server (IIS) would serve it that way. When you have defined standards and follow them with your site design, the browser a user chooses when visiting your site should be 100% irrelevant, and if it is that is the fault of the browser maker because they do not implement the standard. If you develop your site to require a certain feature of a specific make of browser be used, the fault is yours for developing a browser-specific site.

Yeah, I read through those... and found that while it described a vulnerability, it was still light on actual exploit details.

Did they compromise the inward facing web interface, or an outward web interface? Did they do it through social engineering, or through malware running on devices on the internal network? Was the malware persistent or was it a drive-by instance running a portscanner in a browser instance?

Basically, the question I have is - would flashing say, openWRT on these devices been enough to prevent network intrusion, or were they already inside the gates to begin with?

The linked articles are remarkably light on details of how the routers were compromised. Were they breached from the internet side due to backdoors or poorly implemented services? Was it some sort of configuration default for remote administration that was just bulk abused? Or were the routers compromised from inside the network by malware running locally on machines, or on malware compromised pages? Was it due to remote code execution or was it due to default admin credentials or easily guessable passwords?

Kind of hard to defend against a threat if they won't tell you how the deed was done.

Same happens where I work. They default everything to Chrome but allow you to use Firefox and a couple of others as well. I just restrict my use of Chrome to the corporate intraweb stuff (training, help desk, etc). Overall, it's laziness of design of those intraweb sites... they force the developers to use one methodology over another instead of building things to a browser-agnostic standard.

I'm pressing 'X' to doubt. What make/model of router? I'll look up an image of the box.

Why did it need a 'big yellow burst' when it would have plainly advertised itself as a 100/1000 instead of a 10/100/1000?

Well, in this case, a distinct lack of needing to compile shaders.

And consoles have been 'PCs in fancy cases' since the OG Xbox. Arguably the Dreamcast.

As anyone knows, IT technicians are federally mandated to request a reboot of the system before continued troubleshooting. Does this apply in space and what is Outlook running on anyway?

-m

Console master race stays winning, you filthy PC gaming peasants.

Can it clone proprietary software and turn it into an open source project?

If so, then I think the tradeoff is fair.

Buy the S2 now, while they're still working through their existing backlog of stock.

I bought a PS5Pro when the word 'tariffs' was first dropped, and I'm glad I did.

Bots and other bad actors thrive in free (as in beer) environments, for reasons that should be obvious. If we want to do anything meaningful about them, sites will need a nominal but real fee to use.

It's not what anyone wanted, but "free" was always inevitably going to lead to the Internet becoming a dump. The free ride is over.

I think she could reasonably assume that she wouldn't be served liquid hot enough to literally melt her.

If by 'burned a little' you mean 'her labia literally melted and fused shut,' you're correct.

Cheap is exactly what you don't want, even if it's inexpensive.

-m