6 ms·
Are Intel still disabling random features in the K versions of their processors for market segmentation reasons? Figuring out what processors had what features
by makomk 11y ago
Are Intel still disabling random features in the K versions of their processors for market segmentation reasons? Figuring out what processors had what features locked off was getting truly ridiculous.
- onli 11y agoYes: http://www.cpu-world.com/Compare_CPUs/Intel_CM8066201919901,Intel_CM8066201920103/ http://www.cpu-world.com/Compare_CPUs/Intel_CM8066201919901,... – Trusted Execution in this case.
- userbinator 11y agoIn the case of TXT I don't think everyone would consider it a desirable feature since it's part of the trusted computing stuff, but in the past they've also disabled more friendly features like virtualisation.
- onli 11y agoYou're right. Some of that happens in the current generation with the mainboard chipsets.
- delroth 11y agoIf you're not using TXT, your full disk encryption is completely useless if an attacker can get access to your laptop for 5 minutes¹. They can just backdoor the bootloader (or, on Linux, your kernel/initramfs which are not encrypted) to get a foot into your system at the highest level of privileges. If you're using TXT, maybe the NSA can still do that by getting the ACM signing keys from Intel. But that's still an improvement from just the standard FDE setup most people use, which could be trivially hacked by someone with the skill of an average university student. ¹ Make that 15min if you have a BIOS password and a static boot order that disallows booting on any kind of external device. It just requires a bit more preparation, but on most laptops it's not hard to put a clip on the NVRAM that stores BIOS settings and reset what needs to be reset.
- dogma1138 11y agoThis is simply not correct, TXT is not required for this, the TPM can still and does protect your OS and boot loader from tampering, it's also not required for Windows Secure Boot. TXT extends the chain of trust to the BIOS/UEFI by having the CPU take charge of some of the verification, secure boot supported UEFI's (if they meet the UEFI standard version 2.3.1c or higher) can also extend the protection envelope beyond the OS/MBR but the main function of TXT is to protect tampering with low level firmware not OS/bootloaders. "Intel TXT uses a Trusted Platform Module (TPM) and cryptographic techniques to provide measurements of software and platform components so that system software as well as local and remote management applications may use those measurements to make trust decisions. This technology is based on an industry initiative by the Trusted Computing Group (TCG) to promote safer computing. It defends against software-based attacks aimed at stealing sensitive information by corrupting system and/or BIOS code, or modifying the platform's configuration."
- delroth 11y agoSecure Boot's aim is mostly to protect against malware persisting through the boot process ("bootkits"). Given that it's anchored in the firmware and the firmware is unverified in almost all consumer x86 motherboards, an attacker with physical access can still bypass it in a trivial amount of time (it requires some preparation to figure out what to patch, but the patching itself is quick).
- dogma1138 11y agoIn theory anything can be bypassed including TXT, TXT on it's own does not provide any substantial amount of protection against tampering at least not over traditional TPM setups. What it does is centralizes all of the measurements in one place and adds DRM. It's not bad in any way but it's also not required to run a secure boot encryption setup. My 9 year old HP Compaq 6910p Centrino with TPM can offer almost the same level of protection as any modern Intel vPro laptop. Case for Bitlocker (one of the few FDE's that actually has good integrity checks) BIOS / UEFI modification (Update, revision, settings change etc.) - both will trigger recovery mode -Boot loader modification - both will trigger recovery mode -Boot order change - both will trigger recovery mode -Boot attempt number does match between TPM & HDD (e.g. when the HDD was removed and attempted to be booted in another device, or when the machine was booted not from the HDD) - both will trigger recovery mode -Data partition changed - both will trigger recovery mode The only difference is that if my device is in either S4 and S5 mode TXT can still continue to make measurements, and the measurements that TXT allows you to do are very generic unlike standard TPM/Secureboot which only checks for specific parameters. You also need to understand that FDE is not designed to protect your information in such cases where you lose control of the physical security of the device and do not treat it as untrustworthy afterwards, it's more or less excellent at protecting your data while it's in rest if the device is lost or stolen but that's it. And while yes secure boot can be bypassed and TPM's could also potentially be broken (which invalidates TXT as well since it uses the TPM as the cryptographic storage device for the signatures) an adversary that can bypass one could most likely bypass the others (you also need to remember that with TXT the measurement plan is stored in the UEFI flash/ram/nvram not in the TPM) and with any system your overall level of confidence should be as high as the weakest component.
- dogma1138 11y agoWith how overclocking is done on UEFI enabled motherboards TXT will not work anyhow. Virtually no OEM uses K series processors, the vast majority of computers that come with TPM's are laptops which use a different SKU family, the few workstations that do will not use the desktop K series of CPU's. Intel TXT is also not available on their more "workstation" oriented prosumer line of CPU's like the 5820 and the 5860's.
- flyinghamster 11y agoOne thing I've really hated about Intel in recent times has been that you can't really tell what you're getting based on the model number. I got bitten by this when I built up a system and picked a Core 2 Quad Q8200, only to discover after powering it on that it did NOT have virtualization support. The problem is only worse now; is that i7-xxxx dual-core or quad-core? Should I get i5-yyyy instead?
- lallysingh 11y agoYou have to look them up on ark: http://ark.intel.com/products/36547/Intel-Core2-Quad-Processor-Q8200-4M-Cache-2_33-GHz-1333-MHz-FSB http://ark.intel.com/products/36547/Intel-Core2-Quad-Process...
- speeder 11y agoWarning: ARK is not much safe either, I saw on reddit some days ago some guy complaining that he bought a I3 after checking it on ARK, and after the purchase, Intel disabled the feature on all i3 and changed ARK too, silently. (It was related to some feature Intel also tried to implement in the 2 previous generations but seemly is buggy) EDIT: I hit the post limit... Yes, I do think it was TSX
- lallysingh 11y agoWas it TSX?
- qb45 11y agoIntel Transactional Synchronization Extension. When it works, you get support for database-like transactions on RAM (only small transactions, it isn't black magic). When it fails, you get all kinds of random crashes at random times. Introduced in Haswell, turned out to be buggy and Intel famously disabled it with ucode update. Since then, they quietly disabled it also for several Broadwells and Skylakes which didn't fare much better than Haswell. edit: it seems I misread parent's post as "what is TSX"