https://i.blackhat.com/USA-19/Wednesday/us-19-Santamarta-Arm...
page 52.
There are _always_ bugs in software. Your assertion that it's pure fantasy to pivot from the flight entertainment system goes against there near infinite space of sidechannel attacks and demonstrated attacks on even airgapped systems; it's almost a law of physics that you are wrong.
The "self promotion" angle was brought up last time this was discussed: https://news.ycombinator.com/item?id=20657965 and it's an obviously pointless rebuttal.
Boeing: Please post the code. Lets read it. It's already out there: https://ioactive.com/arm-ida-and-cross-check-reversing-the-7...
This is not what Boeing said to the FAA 12 years ago when they asked to certify their network architecture
> The proposed architecture of the 787 is different from that of existing production (and retrofitted) airplanes. It allows connection to and access from external sources (the public Internet) and airline operator networks to the previously isolated Aircraft Control Domain and Airline Information Services Domain. The Aircraft Control Domain and the Airline Information Services Domain perform functions required for the safe operation of the airplane.
[1] http://rgl.faa.gov/Regulatory_and_Guidance_Library%5CrgSC.ns...
I believe this contradicts the "systems are entirely separate" statement from the parent comment.
This is part of the reason why I agree with you, because I don't see why the 787 would be unique by mixing avionics/mechatronics with the passenger systems but I don't know enough to say it with confidence. They would have designed the passenger systems to be independent and replaceable (especially with the knowledge gained from the legacies and upgrades of other planes like the 737).
Is there any public guides for 787 chassis and maintenance that you could point to as being reasonable things to read about this new style plane?
I was hoping that the person I commented to could point us at some fun manuals to describe how these configurations worked at a technical level.
Doing things, however, that increased the weight or changed aerodynamics of the airplane were a very big deal, causing a ripple effect that would be very expensive.
Freighter versions were commonplace, with the obvious omission of windows (weight savings) and interior fluff.
Doing a stretch, or a re-wing or re-engine is an enormous thing.
So, you're saying there's no shared components at all... boards, data lines/switches, power lines/switches... between entertainment and critical systems? They run separate, highly-filtered power wires with separate boards with separate data lines for the two? No shared components at all?
I'm obviously not going to attempt to exploit the firmware on an aircraft for obvious reasons, but the security researcher's notion that you can "pivot" from the in flight entertainment to anything to do with aircraft operation is pure fantasy.
These systems are entirely separate, including the electricity that controls the systems.
This guy is preying on individuals' lack of knowledge about aircraft mechanics in order to promote himself.