Preview is one of the things mac os got right. it’s hard to copy. If you think about it, it does not make sense that a tool called preview that most people use to quickly read pdf (and other) files, is also a lightweight pdf editor, which is often more useful than acrobat or pdfedit or whatever you use.

It’s not logical. no one will make a clone of it.

you’ll have to get used to other tools.

yes, i meant x86

Actually, most devices today run an amd64 kernel (amd or intel cpus in typical desktops or servers) or arm (phones, some modern notebooks). Those architectures never supported 486 cpus.

I assume, the code removed is in the x86 branch, excluded when compiling for other architectures. As others said, I guess this is mostly about maintainance effort and testing.

(But then i don’t know much about the kernels. Maybe there’s some interplay between amd64 and x64 x86 architectures.)

There are several ways to exploit LogoFAIL. Remote attacks work by first exploiting an unpatched vulnerability in a browser, media player, or other app and using the administrative control gained to replace the legitimate logo image processed early in the boot process with an identical-looking one that exploits a parser flaw. The other way is to gain brief access to a vulnerable device while it’s unlocked and replace the legitimate image file with a malicious one.

In short, the adversary requires elevated access to replace a file on the EFI partition. In this case, you should consider the machine compromised with or without this flaw.

You weren’t hoping that Secure Boot saves your ass, were you?

Summary does not contain the actual vulnerability or exploit.