Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe the risk of exposing additional hardware clocks #164

Open
jyasskin opened this issue Oct 16, 2023 · 0 comments
Open

Describe the risk of exposing additional hardware clocks #164

jyasskin opened this issue Oct 16, 2023 · 0 comments
Assignees

Comments

@jyasskin
Copy link
Member

Clock Around the Clock: Time-Based Device Fingerprinting (https://doi.org/10.1145/3243734.3243796) discusses fingerprinting particular chips based on tiny variations in their quartz clock crystals. This can distinguish different copies of the same model of chip, not just different models of chip. They describe their attack as comparing the frequency of two different crystals in the same machine, but I think they're actually extracting NTP's precise measurement of a single clock crystal's frequency (by comparing with clocks over the network).

As we allow code to run on new processors like GPUs, we naturally expose additional clock crystals that can be compared against each other, which makes the fingerprint more precise. This is probably unavoidable and not something HR-Time can address. But there's currently a proposal to read timestamps on a GPU. If that's based on a new hardware crystal, it'll improve the fingerprint. If it's just calibrated against the same NTP measurement as the CPU, it won't. I think HR-Time should say something about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants