From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] can bus attack
Date: Fri, 14 Apr 2023 08:08:32 +0200 [thread overview]
Message-ID: <9232C347-0DAD-478E-AA98-9BFFEDCB5773@gmx.de> (raw)
In-Reply-To: <CAA93jw4-YMMw3WiU0QpPYT3c7SupnW2qWZHzSmRE1sK8hqpXgQ@mail.gmail.com>
Hi Dave,
> On Apr 14, 2023, at 06:04, Dave Taht via Cerowrt-devel <cerowrt-devel@lists.bufferbloat.net> wrote:
>
> The biggest bug with the early fq_codel deployment was that it dropped
> from head and fq'd which led to the prospect of messages sent out of
> order on the can protocol, which was not designed for that..
[SM] How did CAN react to this bug? Fixing its design or simply requiring in-order-delivery?
> After
> much thought, we ended up overriding the default fq_codel qdisc, for a
> fifo, for the can bus devices, but there were a few years there where
> fq_codel was the default for can, in openwrt, which sometimes keeps me
> awake at night.
[SM] How many critical CAN bus implementations actually use OpenWrt? I thought CAN is big in automobiles, so if any of those use OpenWrt that would be interesting news ;)
> This set of security bugs is bigger and essentially a message flood
> attack on a FIFO, making it possible to steal a car via accessing the
> headlamp, using a 10 dollar adaptor. Fascinating reading.
>
> https://kentindell.github.io/2023/04/03/can-injection/
[SM] It appears automobile designers assumed a non-adversarial environment, which is odd given that 3rd party diagnostic dongles that interface with the car network/bus have been a thing for years.
I guess the good thing is that we do have some well-tested techniques to harden such a design (that are unlikely to be retro-fitable into existing cars, assuming that vendors actually still care about older models anyway).
Regards
Sebastian
>
>
> --
> AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2023-04-14 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 4:04 [Bloat] " Dave Taht
2023-04-14 6:08 ` Sebastian Moeller [this message]
2023-04-14 6:25 ` [Bloat] [Cerowrt-devel] " Bill Woodcock
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9232C347-0DAD-478E-AA98-9BFFEDCB5773@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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