TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Intel PIII: Is Big Brother Inside? (1999)

156 pointsby erjiangabout 4 years ago

8 comments

marcan_42about 4 years ago
I&#x27;d forgotten tech reporting was just as bad in 1999 as it is today. Here&#x27;s the important part missing from the article: that serial number is available from userspace, and cannot be intercepted by the kernel in any way. They provided a way to disable it, but not to report, control, or intercept how it is accessed. It is returned by the unprivileged, untrappable* CPUID instruction.<p>Every single UEFI computer sold today has a unique serial number (GUID). There are MAC addresses. There are HDD serial numbers. There are zillions of unique identifiers accessible to the <i>operating system</i>. Various copy protection schemes use one or more of these. But what they all have in common is that they are under the control of the OS. A privacy-conscious OS can forbid access to these identifiers for userspace applications, or can fake them to something else. This is how e.g. sandbox environments like the App Store can force apps to use some kind of &quot;advertising ID&quot; for this stuff, and ensure that apps aren&#x27;t sneakily fetching some true unique system ID.<p>But with the PIII serial number, userspace apps can fetch it without the OS knowing about it. And the disable bit is a one-time operation, so it is not possible to grant serial number access to some apps and not others. This leads to a situation where any arbitrary unprivileged userspace app can uniquely identify your machine, and where vendors relying on this feature might compel you to leave it enabled (e.g. DRM). Now random apps running under an untrusted user can fingerprint your machine, just because you want to watch Netflix.<p>And <i>that</i> is why this design was utterly broken and a privacy nightmare. Not because it&#x27;s a unique ID. We have tons of those.<p>* VMs can trap CPUID, but of course VM support came later anyway.
评论 #26455464 未加载
JohannMacabout 4 years ago
Common to have unique SN in a processor. Let the SW vendors do copy protection too. E.g. at Sonos we used them to associate with the software signed certificate such that you couldn&#x27;t run a given Players software on another Player without the same SN. When making products via contract manufactures, especially in China, it was a wise procedure.
评论 #26452157 未加载
评论 #26451007 未加载
dehrmannabout 4 years ago
&gt; But didn&#x27;t you say it&#x27;d help to prevent counterfeiting of chips?<p>The stolen part I get, but did it used to be easier to counterfeit chips? There&#x27;s a lot that goes into making something that looks like a PIII, and even then, I assume Intel had state-of-the-art fabs, so I&#x27;m surprised this was a concern.<p>The hardware scams I&#x27;ve heard of stamping better specs on something, for hard drives, a firmware hack that makes it appear to be higher capacity, and unauthorized hardware made in off-hours on the same production line.
评论 #26450257 未加载
评论 #26450228 未加载
评论 #26450421 未加载
CodeWriter23about 4 years ago
The wedge used to drive home even more draconian privacy infringement like the Intel Management Engine.
illysabout 4 years ago
&quot;Big Brother Inside&quot; for just a unique id? What should we say now about Intel Management Engine?
评论 #26450216 未加载
评论 #26450794 未加载
评论 #26450100 未加载
beervirusabout 4 years ago
Oh man, I remember this. What a simpler time.
评论 #26452018 未加载
musicaleabout 4 years ago
Yes, and he seems to be there to stay. :(
monocasaabout 4 years ago
&gt; Q: I&#x27;ve never heard of software &quot;expiring.&quot; How is that possible?<p>What a beautiful world that was
评论 #26450094 未加载
评论 #26449995 未加载
评论 #26450610 未加载
评论 #26449756 未加载
评论 #26451172 未加载
评论 #26450025 未加载