The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: charles.unix.pro@gmail.com (Charles Anthony)
Subject: [TUHS] Windows roots and Unix influence (was Re: Happy birthday, Ken Thompson!)
Date: Mon, 5 Feb 2018 15:10:05 -0800	[thread overview]
Message-ID: <CANV78LTy1HXiKi4fZ_-OUumP=LMf2LH_uTo6XHw7PLFQA4yGQg@mail.gmail.com> (raw)
In-Reply-To: <013001d39ecc$614dc500$23e94f00$@ronnatalie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 6406 bytes --]

On Mon, Feb 5, 2018 at 1:57 PM, Ron Natalie <ron at ronnatalie.com> wrote:

> I've not seen that in an airplane.   I'd like a cite.
>

comp.risks:



Interconnection of Three Previously Separated Networks in Boeing 737

Joe Loughry <joe.loughry at stx.ox.ac.uk>

Wed, 11 Jun 2014 19:06:37 +0000

"Special Conditions" refers to the fact that certification rules haven't

kept pace. The three network domains (aircraft control, operator

information, and passenger entertainment) used to run on physically separate

wires, primarily for historical reasons, but having obvious engineering

benefits as well. In recent years, first the computers and now the networks

have migrated to virtual machine separation on shared hardware, for the

equally obvious space, weight, and power savings. The *Federal Register*

rule published this week mentions interconnection between at least two of

the three domains; I hope they paid close attention to UC Berkeley's

"Experimental Security Analysis of a Modern Automobile" (2010).


> https://federalregister.gov/a/2014-13244


> Source: "Special Conditions: The Boeing Company, Models 737-700, -700C,

-800, -900ER, -7, -8, and -9 Series Airplanes; Airplane Electronic Systems

Security Protection From Unauthorized External Access" [*Federal Register*

vol. 79, no. 109, June 6, 2014, pp. 32640-32641].


> Joe Loughry, Doctoral Student in the Department of Computer Science

St Cross College, Oxford



and

Banned Researcher Commandeered a Plane (Kim Zetter)
>
> "Peter G. Neumann" <neumann at csl.sri.com>
>
> Fri, 15 May 2015 21:12:42 PDT
>
>   (Courtesy of Dan Farmer: Fly the unfriendly skies?)
>
>
>> Kim Zetter, Feds Say That Banned Researcher Commandeered a Plane
>
> http://www.wired.com/2015/05/feds-say-banned-researcher-commandeered-plane/
>
>
>> A security researcher kicked off a United Airlines flight last month after
>
> tweeting about security vulnerabilities in its system had previously taken
>
> control of an airplane and caused it to briefly fly sideways, according to
>
> an application for a search warrant filed by an FBI agent.
>
>
>> Chris Roberts, a security researcher with One World Labs, told the FBI
>> agent
>
> during an interview in February that he had hacked the in-flight
>
> entertainment system, or IFE, on an airplane and overwrote code on the
>
> plane's Thrust Management Computer while aboard the flight. He was able to
>
> issue a climb command and make the plane briefly change course, the
>> document
>
> states.
>
>
>> FBI Special Agent Mark Hurley: “He stated that he thereby caused one of
>> the
>
> airplane engines to climb resulting in a lateral or sideways movement of
>> the
>
> plane during one of these flights, He also stated that he used Vortex
>
> software after comprising/exploiting or hacking the airplane's networks. He
>
> used the software to monitor traffic from the cockpit system.''
>
>
>> Hurley filed the search warrant application last month after Roberts was
>
> removed from a United Airlines flight from Chicago to Syracuse, New York,
>
> because he published a facetious tweet suggesting he might hack into the
>
> plane's network. Upon landing in Syracuse, two FBI agents and two local
>
> police officers escorted him from the plane and interrogated him for
>> several
>
> hours. They also seized two laptop computers and several hard drives and
>> USB
>
> sticks. Although the agents did not have a warrant when they seized the
>
> devices, they told Roberts a warrant was pending.
>
>
>> A media outlet in Canada obtained the application for the warrant today
>> and
>
> published it online.
>
>
>>
>> http://aptn.ca/news/2015/05/15/hacker-told-f-b-made-plane-fly-sideways-cracking-entertainment-system/
>
>
>> The information outlined in the warrant application reveals a far more
>
> serious situation than Roberts has previously disclosed.
>
>
>> Roberts had previously told WIRED that he caused a plane to climb during a
>
> simulated test on a virtual environment he and a colleague created, but he
>
> insisted that he had not interfered with the operation of a plane while in
>
> flight.
>
>
>> He told WIRED that he did access in-flight networks about 15 times during
>
> various flights but had not done anything beyond explore the networks and
>
> observe data traffic crossing them. According to the FBI affidavit,
>> however,
>
> he mentioned this to agents as well last February but also added that he
>> had
>
> briefly commandeered a plane during one of those flights. He told the FBI
>> he
>
> accessed the flights in which he accessed the in-flight networks more than
>> a
>
> dozen times occurred between 2011 and 2014, but the affidavit does not
>
> indicate exactly which flight he allegedly caused to turn to the side.
>
>
>> 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.
>
>
>> Reaction in the security community to the new revelations in the affidavit
>
> have been harsh. Although Roberts hasn't been charged yet with any
>
> crime, and there are questions about whether his actions really did cause
>
> the plane to list or he simply thought they did, a number of security
>
> researchers have expressed shock that he attempted to tamper with a plane
>
> during a flight.
>
>
>> “I find it really hard to believe but if that is the case he deserves
>> going
>
> to jail,'' wrote Jaime Blasco, director of AlienVault Labs in a tweet.
>
>
>> Alex Stamos, chief information security officer of Yahoo, wrote in a
>> tweet,
>
> “You cannot promote the (true) idea that security research benefits
>
> humanity while defending research that endangered hundreds of innocents.''
>
>
>>   [Wonderful long item truncated for RISKS.  PGN]
>
>
> -- Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180205/dedf431b/attachment-0001.html>


  parent reply	other threads:[~2018-02-05 23:10 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  0:37 Dan Cross
2018-02-04  2:59 ` Nemo Nusquam
2018-02-04  5:06   ` Wesley Parish
2018-02-04  5:18     ` Warner Losh
2018-02-05 19:43     ` Paul Winalski
2018-02-05 21:19       ` Michael Kjörling
2018-02-06  0:37         ` Steve Nickolas
2018-02-06  0:45           ` Warner Losh
2018-02-06  9:14           ` Wesley Parish
2018-02-04  9:14   ` Angelo Papenhoff
2018-02-04 14:15     ` arnold
2018-02-04 17:21     ` Ron Natalie
2018-02-04 20:05       ` Dan Cross
2018-02-04 20:55         ` Nemo
2018-02-04 20:57           ` Warner Losh
2018-02-04 20:59           ` Jon Steinhart
2018-02-04 22:12             ` Clem Cole
2018-02-05  1:32             ` William Cheswick
2018-02-05  1:44               ` Dave Horsfall
2018-02-04 21:04         ` Toby Thain
2018-02-04 22:22           ` Andy Kosela
2018-02-04 22:43         ` Dave Horsfall
2018-02-04 22:54           ` George Michaelson
2018-02-05  3:35           ` Ron Natalie
2018-02-05  3:40           ` Dan Cross
2018-02-05 13:48             ` William Cheswick
2018-02-05 14:31               ` Ron Natalie
2018-02-05 21:51               ` Dave Horsfall
2018-02-05 21:57                 ` Ron Natalie
2018-02-05 22:31                   ` Grant Taylor
2018-02-05 23:16                     ` Arthur Krewat
2018-02-05 23:49                       ` Grant Taylor
2018-02-06 17:42                       ` Ron Natalie
2018-02-06 18:23                         ` Arthur Krewat
2018-02-05 23:10                   ` Charles Anthony [this message]
2018-02-05 23:20                   ` Arthur Krewat
2018-02-05 23:28                     ` Dave Horsfall
2018-02-05 23:36                       ` Arthur Krewat
2018-02-05 23:52                         ` George Michaelson
2018-02-06 14:52                 ` Steffen Nurpmeso
2018-02-05 23:18               ` Lyndon Nerenberg
2018-02-06 21:51               ` Dan Cross
2018-02-06 23:14                 ` Nemo Nusquam
2018-02-06 23:22                   ` Warner Losh
2018-02-07  3:03                     ` Dave Horsfall
2018-02-07  1:23                 ` Dave Horsfall
2018-02-07  1:33                   ` Clem Cole
2018-02-07  1:54                   ` Dan Cross
2018-02-07 18:01                     ` Tony Finch
2018-02-09  2:35                       ` Wesley Parish
2018-02-07 18:50                     ` Bakul Shah
2018-02-15 13:23                     ` Tim Bradshaw
2018-02-05  0:27         ` Kurt H Maier
2018-02-05  0:41     ` Robert Brockway
2018-02-04  9:11 ` Donald ODona
2018-02-04 23:25 ` Dave Horsfall
2018-02-04 23:46   ` Bakul Shah
2018-02-04 23:58     ` Dave Horsfall
2018-02-05  0:06 ` Robert Brockway
2018-02-05  5:37   ` Steve Johnson
2018-02-05  5:53     ` Greg 'groggy' Lehey
2018-02-05 10:49       ` Ron Natalie
2018-02-05  6:57     ` Robert Brockway
2018-02-05 15:20 Doug McIlroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANV78LTy1HXiKi4fZ_-OUumP=LMf2LH_uTo6XHw7PLFQA4yGQg@mail.gmail.com' \
    --to=charles.unix.pro@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).