From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Windows roots and Unix influence (was Re: Happy birthday, Ken Thompson!)
Date: Mon, 5 Feb 2018 18:20:58 -0500 [thread overview]
Message-ID: <5a838d87-4acb-e2f4-f09e-458d6c5eae49@kilonet.net> (raw)
In-Reply-To: <013001d39ecc$614dc500$23e94f00$@ronnatalie.com>
The CAN network is bi-directional, and I don't think it has any
security. So any node on the CAN can read-write whatever the heck it
wants to.
Plug in an OBD-II device, and using the right software (like Forscan)
you can read/write all sorts of locations in the body-control module,
flash new software into the PCM (powertrain control module), etc.
I suspect that if you have the entertainment system that has the ability
to read PIDs in the PCM, for example, road speed, that same interface
could be used to write values as well.
My 2013 Taurus SHO came with Sync 2 - which ran Windows CE. Thankfully,
it wasn't a "server" and WiFi wasn't enabled. Now my 2016 Taurus SHO has
Sync 3 running QNX. I am not amused ;)
On 2/5/2018 4:57 PM, Ron Natalie wrote:
> There's certainly been demonstrations of vehicles being taken over via the entertainment system; why the stereo needs to talk to the engine computer I'll never know... I know, wind up the volume the faster you go etc, but surely it ought to be one-way?
next prev parent reply other threads:[~2018-02-05 23:20 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
2018-02-05 23:20 ` Arthur Krewat [this message]
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=5a838d87-4acb-e2f4-f09e-458d6c5eae49@kilonet.net \
--to=krewat@kilonet.net \
/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).