Hacker News Reader

Comment by ryandrake | Hacker News Reader

I’ve worked on (non-safety critical) airborne systems that ran Windows Embedded, as freightening as it sounds.

And there's evidence the "non-safety critical" airborne systems are not nearly as well isolated from the flight control systems as most people assume:

https://www.wired.com/2015/05/feds-say-banned-researcher-com...

"He obtained physical access to the networks through the Seat Electronic Box, or SEB. These are installed two to a row, on each side of the aisle under passenger seats, on certain planes. After removing the cover to the SEB by "wiggling and Squeezing the box," Roberts told agents he attached a Cat6 ethernet cable, with a modified connector, to the box and to his laptop and then used default IDs and passwords to gain access to the inflight entertainment system. Once on that network, he was able to gain access to other systems on the planes."

That one might just be a security researcher big-noting himself, but combined with this next one, I do not have a great deal of confidence in Boeing (or any of the airline industry's) software security teams...

https://nakedsecurity.sophos.com/2017/11/15/dhs-says-it-remo...

I wonder what we'd find if Tavis Ormandy were seconded to Boeing for six months? (And can I have a heads-up if that happens? I've got some stock I'd like to short...)

That bullshit story being pushed by this bullshitter for years does not constitute evidence. There was no way for him to send data to any of the safety critical systems.

> freightening

So it was on a cargo plane, then?

If they are non-safety critical, you could use TempleOS and it still doesn't sound all that frightening.

TempleOS is airtight, so I don't really understand the comment you're trying to make about it.

Reply on news.ycombinator.com