After the dust has settled can we please have a serious discussion how intransparency from actors like @intel is harming security? I mean... they ship microcode updates without changelogs. @tehjh + @anders_fogh had to guess how their processors work. They don't comment on ME.
-
Show this thread
-
I fear that's wishful thinking. There aren't any competitors that try to go down the "more transparency" route. And it's not just a CPU issue, that basically affects "all hardware". think about the broadpwn and wifi firmware mess etc.
2 replies 0 retweets 5 likes -
For non-cpu case it mostly comes down to missing isolation. Who cares about wifi or baseband vulns if the chips are isolated & the network layer is untrusted?
1 reply 1 retweet 8 likes -
Replying to @RichFelker @dzxi and
this is a good approach, yet my latest state on this was something like "ok, this chipset can do IOMMU, but for unclear reasons
@Qualcomm has disabled it and they don't comment on it"2 replies 0 retweets 7 likes -
Replying to @hanno @RichFelker and
plus: the isolation depends on secure drivers without buffer overflows. and there we are again with the transparency issue and proprietary drivers without sourcecode...
1 reply 0 retweets 5 likes -
Yes but now it's a sw issue not a hw one.
1 reply 0 retweets 1 like -
Replying to @RichFelker @hanno and
How about your WiFi chip being hijacked and used for nefarious things? Entirely possible with your OS knowing about it. Just saying
1 reply 0 retweets 0 likes -
Replying to @fhuberts @RichFelker and
if your main system is properly isolated (by iommu or by using usb wifi) this doesn't matter a lot. the attacker can mess with wifi traffic, but there's tls to prevent that and you can't trust the network anyway.
2 replies 0 retweets 2 likes -
Replying to @hanno @RichFelker and
Except that it now is YOUR machine doing those things.
1 reply 0 retweets 0 likes
Yes but it's largely indistinguishable from a separate malicious box that just spoofed your MAC address, which is always a possibility.
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.