Live data from Hacker News

A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

wired.com

71–80 of 277 posts

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#71
post #33
post #5

Earlier quoted context omitted.

Connecting entertainment systems to flight control sounds very wrong. Connecting entertainment systems to flight management would be common; it should be one-way communication (entertainment can only read FMS data, not send any), for the purpose of driving the moving map displays for passengers.

The moving map could easily be fed from a separated consumer grade GPS. Same for all other metrics that the median passenger would care about (height, speed over ground), except for the ever-impressive outside temperature.

Data diodes are things that exist

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#72
post #24

Earlier quoted context omitted.

Because by keeping it closed, it is safer. /s Most executives care about profits, security is simply not important. Even if an engineer explains that he needs more time to properly secure something, he will be asked to cut corners. Then, when shit hits the fan the executive will make a "pikachu face" and engineer will get fired for not properly implementing security.

Having met a fair number of top executives I don’t feel this is true. People at the top do care quite a bit, and put personal pride into their company being good. But all low level decisions are made downstream, and middle managers are far less personally invested. Reactions to bad press are reactions. Hard to say whether it reflects anyone’s reality.

Leadership starts at the top. If middle management is making bad decisions, the fault rests with their superiors.

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#73

Earlier quoted context omitted.

> Boeing maintains that other security barriers in the 787's network architecture would make that progression impossible. They probably do something to that effect

The longer I'm alive the more firmly I commit to never assume anything. I have seen things. Terrible things.

Connectivity between zones is something FAA actually caught in 787 when it was still being built and forced a redesign.

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#74

It seems insane that all this code isn't just open source by default. No one's going to be able to rip off airlines by stealing it, you still need to have a company that, you know, sells planes. Keeping it closed seems like a full admission that "there are probably a bunch of bugs in here and we don't want people to see them"

That goes for every piece of hardware with firmware.

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#75
post #24

Earlier quoted context omitted.

Because by keeping it closed, it is safer. /s Most executives care about profits, security is simply not important. Even if an engineer explains that he needs more time to properly secure something, he will be asked to cut corners. Then, when shit hits the fan the executive will make a "pikachu face" and engineer will get fired for not properly implementing security.

Having met a fair number of top executives I don’t feel this is true. People at the top do care quite a bit, and put personal pride into their company being good. But all low level decisions are made downstream, and middle managers are far less personally invested. Reactions to bad press are reactions. Hard to say whether it reflects anyone’s reality.

They are good at giving lip service but I rarely see anything more than that given. When it comes to budgets and hiring, one might say when it comes to putting their money where their mouth is, then you see how much they actually care.

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#76
post #18
post #2

Who thought that having any communication path from the passenger entertainment system to flight control was a good idea?

You want communications from the flight controls to the maintenance system. And you want communications from the entertainment system to the maintenance system, so technicians have a single list of everything that needs fixing. It's hard to implement strict one-way communications -- usually you at least need some kind of ACK for reliable transmission. Put all those together with a vulnerability in the middle, and you…

AFDX used by 787 has one way only communications, no ACKs are used or allowed (it actually uses UDP plus network proven to not lose packets)

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#77
post #26
post #2

Who thought that having any communication path from the passenger entertainment system to flight control was a good idea?

Or to driving control! But, engineers keep making this mistake. Hackers were able to take over Jeeps via the entertainment system: https://www.bbc.com/news/technology-33650491 HN discussion: https://news.ycombinator.com/item?id=9942647

Take over as in turn off, not steer, right?

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#78
post #50

Earlier quoted context omitted.

i dont think i know of any airline company that prides themselves on the code they wrote?

Airbus. Not a matter of pride, but you don't want to help your competitors offer the same capabilities as you for $0 R&D costs

Are you seriously suggesting that Airbus would rip off Boeings code? There is such a thing as copyright.

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#79
post #14

...an FAA spokesperson wrote in a statement to WIRED that it's "satisfied with the manufacturer’s assessment of the issue." Can't help but read this as: "We don't have a clue and depend on the manufacturer to tell us everything is 5 by 5."

Separation of IFE and avionics networks is something FAA actually chastised Boeing over during 787 design, and forced them to fully separate networks not VLAN crap.

Re: A Boeing Code Leak Exposes Security Flaws Deep in a 787's Guts

#80

From the article: "He was surprised to discover a fully unprotected server on Boeing's network, seemingly full of code designed to run on the company's giant 737 and 787 passenger jets, left publicly accessible and open to anyone who found it. So he downloaded everything he could see." Is that even legal? Will he ever be allowed to cross the US border after admitting this?

>Is that even legal?

Generally no. There is a difference between being unprotected and being open to the public. While in some cases a person can claim to not have known and proving mens rea for such a crime is much harder than if it was protected and the protection had to be bypassed, it isn't impossible.

Such laws are selectively enforced, but being this is Boeing, you can expect it will be enforced on their behalf if they have any desire for it to be (given the current PR issues and the impact this might have, they might let this one go, at least for the time being).

Post reply on HN