The problem is not crypto at all. The system serial info (96 bits) is provided upon request by executing a CPUID instruction. This instruction is nonpriveleged so the kernel will have a hard time trapping it.
Thus the problem centers around how to get the kernel to trap this request and emulate, fake, or mangle it.
Does anyone know a work around?
here's some URL's that Phil Karn provides in his patch: (AP-485) , (AP-909), a href = "http://www.amd.com/K6/k6docs/pdf/20734j.pdf"> AMD K6
Slashdot Mirror
Another great upshot of IBM going with Linux is
that were all one step closer to a world without AIX.
The problem is not crypto at all. The system serial info (96 bits) is provided upon request by executing a CPUID instruction. This instruction is nonpriveleged so the kernel will have a hard time trapping it.
Thus the problem centers around how to get the kernel to trap this request and emulate, fake, or mangle it.
Does anyone know a work around?
here's some URL's that Phil Karn provides in his patch:
(AP-485) , (AP-909), a href =
"http://www.amd.com/K6/k6docs/pdf/20734j.pdf"> AMD K6
More ideas on spoofing:
1) all use the same PSN as a protest.
2) use PSN's of machines at Intel.
3) echo back the PSN from the requesting machine.
How is the serial number request negotiated? Is it encrypted?
-D