Hacker News new | ask | show | jobs
by wyldfire 3597 days ago

    > “Aren’t those the people who break into computers?”
    >
    > “Yes—also phones, cars, airplanes, and human bodies.”
    > 
    > “I thought that stuff was illegal.”
While I think they're truly innovative and inevitable, the advent of "secure CPUs" [1] over the last decade or two will eventually become the norm. And once they do -- lookout, brother. The woman who was having this conversation scoffs at how Def Con can even take place if the subject matter is what she thinks it is. In a short time, the computer attacks which cause embarrassing leaks and expensive losses will add up to legislators deciding something must be done. At that time, the number of us who will still like and prefer to be able to run whatever code on whatever processor we care to will be so small that it won't matter.

[1] by "secure CPUs" I'm referring to ones that support signed bootloaders, facilitating good things like more-difficult-to-pwn-by-attackers and bad things like DRM and limiting code to proprietary walled garden app stores.

2 comments

The trouble with "secure CPUs" is that they really only secure the boot process. It is then up to the OS (as usual) to secure itself which is where most failures of security occur anyway.

Consider all the phone "OSes" (aka ROMs) you can install on phones with locked boot loaders that just replace a few binaries/files here and there in an existing OS to change how it works/feels. The maker of said ROMs may not have the ability to replace the kernel but any vulnerability in said kernel will allow them to replace everything else which is precisely where userland security lives.

So the hardware may be "secure" from the perspective of the manufacturer but not from the perspective of the user. They can still be pwned.

Those are just restricted-boot CPU's, not secure CPU's. I agree secure CPU's will make attacks more difficult. Here's you a few examples of them with various tradeoffs:

http://www.crash-safe.org/assets/ieee-hst-2013-paper.pdf

https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/

https://web.archive.org/web/20150315020829/http://palms.ee.p...

https://theses.lib.vt.edu/theses/available/etd-10112006-2048...

Original one that ran businesses which is still immune to lots of attacks vectors and reliability issues:

http://www.smecc.org/The%20Architecture%20%20of%20the%20Burr...

So, spread word on things like those, esp CHERI given FreeBSD support, instead of that DRM garbage that uses the word security but is more about marketing & control. ;)