@jduck @s7ephen @XipiterSec That's also stupid. If the system has no write access to any sensitive buses, then it should not matter
-
-
Replying to @azonenberg
@jduck@s7ephen@XipiterSec IOW, it should be on the same subnet as passenger wifi with no access to anything else1 reply 0 retweets 1 like -
Replying to @azonenberg
@jduck@s7ephen@XipiterSec If that's the case, then there should be no safety concerns w/ patching. If not, somebody done goofed2 replies 0 retweets 1 like -
Replying to @azonenberg
@azonenberg@jduck@s7ephen@XipiterSec indeed there is generally no safety concern on such systems by design so the example is not relevant1 reply 0 retweets 0 likes -
Replying to @AndreaBarisani
@azonenberg@jduck@s7ephen@XipiterSec also those embedded systems tend to have SoC with full Linux env employing NX + ASLR, ssp and so on1 reply 0 retweets 1 like -
Replying to @4Dgifts
@4Dgifts@azonenberg@jduck@s7ephen@XipiterSec I speak from experience1 reply 0 retweets 0 likes -
Replying to @4Dgifts
@4Dgifts@azonenberg@jduck@s7ephen@XipiterSec primary takeway is that safety impact is NULL, so ideally not to worry about the rest3 replies 0 retweets 1 like
@4Dgifts @azonenberg @jduck @s7ephen @XipiterSec yet topological placement and network design is an essential factor
-
-
Replying to @4Dgifts
@4Dgifts@azonenberg@jduck@s7ephen@XipiterSec correct, but they tend not to resolve names and have absolutely strict roles and code paths0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.