[SystemSafety] A Fire Code for Software?
Peter Bernard Ladkin
ladkin at rvs.uni-bielefeld.de
Tue Mar 20 15:14:19 CET 2018
On 2018-03-20 14:43 , Martyn Thomas wrote:
>
> Suppose the linux vulnerability was in the radio, which happens to share
> a communications channel with safty critical components.
Either the components share an OS instance, in which case what I wrote goes, or the OS governing the
radio app is different from that governing the safety-critical components. In the latter case, there
will be no access from the root permission over the radio app to root permission over either the
network or the safety-critical components. The radio could try to mount a DoS attack on the network,
but as far as I know the existing automotive-network protocols defend adequately against such a
possibility.
I know these assumptions/conclusions can be violated, but only on pain of negligence/gross
negligence. If we are talking automotive, doesn't product safety come in here?
PBL
Prof. Peter Bernard Ladkin, Bielefeld, Germany
MoreInCommon
Je suis Charlie
Tel+msg +49 (0)521 880 7319 www.rvs-bi.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 525 bytes
Desc: OpenPGP digital signature
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20180320/d0afe330/attachment.sig>
More information about the systemsafety
mailing list