Skip to content

Remove sentence on Spectre to avoid confusion #38

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 21, 2025
Merged

Remove sentence on Spectre to avoid confusion #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions resource-timing-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -402,9 +402,7 @@ its security considerations.

As covered in the resource timing specification, the main security concern is
the use of high resolution timers. The timing field of the resource timing is
defined to use high resolution timers. However, if malicious actors gain access
to high resolution timers, they could use the exposed fields as a part of
Spectre attack to inspect any memory accesses. In addition, this could expose
defined to use high resolution timers. In addition, this could expose
timing information about how the other origins loaded as well, leading to
inferring information about the user's activity across origins.

Expand Down