likeabatterycar

Or the upload to their CDN was truncated or corrupted, and the signature check worked as designed.

But let's not let an opportunity to paint Dell as some evil yet incompetent corporation slip through our fingers.

Is it really a burden worth complaining about to overwrite the factory fork with OpenWRT? It takes five minutes of your time. You should be doing this regardless, even if it shipped with vanilla OpenWRT, because factory firmware is often outdated out of the box.

Very true. I recently wasted days trying to setup IPSec on OpenWRT with no success. IPSec support is broken into dozens of packages without proper dependency resolution. No GUI support. Sparse documentation, and what little documentation is out there is outdated and mostly consists of sample configs rather than true documentation. You see, OpenWRT likes to break configs from version to version and the docs are never updated. You can't follow documentation from upstream because OpenWRT auto-generates the package's config files from its own configs. Which are sparsely documented.

"Helpful" forum posts mostly suggested to "use Wireguard" with a notion that IPSec is an archaic protocol that is not worth anyone's time to support, and the user is dumber for trying to use it.

Hardly.

The author seems to misunderstand PCB design flow. This is neither a "factory component placement issue" nor a silkscreen error. The error is in the schematic.

The layout CAD is often done by a different team that follows the schematic provided by design engineering. Automated workflows are common. The silk screen is predefined in a QA'd library. It is not their job to double check engineering's schematic.

The components are placed per the layout data.

Both those teams did their jobs correctly, to incorrect specifications. In fact, the factory performing assembly often is denied access to the schematic as it is sensitive IP.

If you're going to cast blame on a 30 year old computer, at least direct it at the correct group. It wasn't soldered incorrectly at the factory. They soldered it exactly how they were told to - backwards.

The 9.8 CVE was for their NAS. Exposing any NAS directly to the open Internet is a Bad Idea.

For that matter, nearly every shit-tier NAS vendor (WD, QNAP) has had some critical remote vulnerability in recent years. Some were notable for mass data loss incidents.

That aside, these companies are all very good at making very, very nice hardware at a price point consumers can afford. Some corners have to be cut and it's often software.

The dirty secret is many Internet of Shit device vendors outsource the software development, often to the lowest bidder in some offshore sweatshop. In some cases it's just a repackage of an ODM design from some no-name company in Shenzhen.

None of which are known for secure coding or good software practices.

Criticize all you want but this is a textbook example of getting what you paid for.

It's unreasonable to pay $100 for a D-Link box and expect it's Cisco ASA quality with free indefinite support.

Cisco, Juniper, and Palo Alto would all tell you to pound sand if you expect support after EOL or if you let your maintenance contract (aka protection racket) lapse.

Yes they do. It's called BGP.

This is also true of every intermediate router between you and the destination.

TLS would not need to exist otherwise.

I cannot identify who the aggrieved parties are, aside from bandwagoning D-Link haters.

These devices are end of life. Anyone running an EOL device doesn't care about security and probably wouldn't update the firmware if it was available.

For comparison, Apple does not update EOL devices outside exceptional circumstances. I never received a 20% discount to upgrade.

Understood.

So the threshold of concern by a "security" company is "they might audit your apps and find out you're gay!"

Yet not a single concern about tethering an iPhone (with an external connection) to a PC on the company's internal network, bypassing all firewalls, proxies, and other protections. That is grounds for immediate dismissal at some places.

I expect security people to think more like network engineers and less like teenagers gossiping in the canteen.

Most comfortable plane I've ever flown on. I guess that means more seats for me?

> then you have to use something else like a data diode

From what I read ARINC 429 is a one-way bus making this completely redundant and unnecessary.

> I wish that vehicular systems all had air-gap level separation of messages

From what I'm reading, ARINC 429 is as air-gapped as you can get. It is a one-way serial protocol (separate wires for transmit and receive). Only the wires that need to be connected are. Messages go from->to where they need to be.

Unless by air gapped you literally mean "don't connect anything together" at which point you no longer have a functioning vehicle.

Maybe tampering with evolution and natural selection isn't the greatest idea.

Absolutely nothing wrong with binary logs as long as the system provides a utility to get the data out of that format.

For that matter, journalctl is terrible, cryptic, and difficult to use.

Corrected link above.

Apologies for the broken link, this was a fail on my part. Microsoft has a habit of breaking their blogs every 6 months. Unfortunately I cannot update or delete the submitted URL. Corrected link below.

https://web.archive.org/web/20051026081935/http://blogs.msdn...

Because Al sold shoes at a time before we thought it was rational to pay someone $400k a year to write shitty Python code.

Said average developers then banded together and built an e-commerce website that sold shoes drop shipped direct from the sweatshop and put Al out of business.

No ma'am indeed.

I must confess I was hoping for a more sordid tale of Silicon Valley sociopathy, like someone using a potted plant in an office at YC HQ as a makeshift toilet, as a means of settling a petty disagreement. Imagine my disappointment reading this was a run-of-the-mill case of divergent minds.

Powerful enough to land a crew on the moon but would choke on any modern framework.

Don't think we would've made it to the moon if it were up to present-day UI/UX folks.

Boeing and Lockheed are union shops IIRC. Any major injuries like those mentioned in the article would mean a major shitstorm and stand-down.

Classic Hacker News. Some guy posts likely incorrect random speculation, and the comments are full of even more speculation.

The truth is Intel makes two versions of most of their WiFi cards: the normal version, and a "low cost" version where some of the internal components are missing and those functions instead offloaded to the Intel chipset on the motherboard.

Sort of like the "WinModems" of WiFi cards.

If you want one that works, buy the correct version.