Meltdown, aka “Dear Intel, you suck”

Re:Meltdown, aka “Dear Intel, you suck” by madez on Saturday January 06, 2018 @09:41AM (#16085447)

Well, there is the ME for one, an omnipotent, mandatory backdoor. Then there are _many_ undocumented opcodes. What does 0f0d00 do? What 0f78c0? What dbe0? I can continue for a very long time. These are just some known unknowns. If you still need more reasons, they are uncooperative when it comes to certain other firmware blobs.

If you are open to arguments, there are many good reasons to take a negative stance towards Intel.

Fun fact: I sent an overview of unknown instructions in compressed text form to a gmail address, and Google rejected it citing potentially malicious content.

[ Parent | on HN ]

Re:Meltdown, aka “Dear Intel, you suck” by tomxor on Saturday January 06, 2018 @10:27AM (#16085623)

To be fair gmail flags basically any code, if it's zipped i've found it only needs to vaguely resemble code. basically gmail is only safe for sending image formats and document formats that it knows of and don't contain macros, then it's just a crapshoot that you don't get matched a false positive. Gmail is far from developer friendly anymore.

[ Parent | on HN ]

Re:Meltdown, aka “Dear Intel, you suck” by petre on Saturday January 06, 2018 @01:36PM (#16086720)

You can't even send encrypted 7zip archives through Gmail. Well, you can, but they'll block the download claiming it's not safe.

[ Parent | on HN ]

Re:Meltdown, aka “Dear Intel, you suck” by Indolat on Saturday January 06, 2018 @11:44AM (#16086006)

> Gmail is far from developer friendly anymore.

Was it ever?

[ Parent | on HN ]

Re:Meltdown, aka “Dear Intel, you suck” by tomxor on Saturday January 06, 2018 @11:46AM (#16086016)

Well, not positively, but there was a time when it didn't block you from zipping up a little snippet of code and sending it to someone or saving it a draft when your in a hurry.

[ Parent | on HN ]