Timing attack privacy consideration
Open
Nobody has claimed this yet.
editorial
privacy-needs-resolution
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
As discussed in the privacy review, timing attacks allow for profiling of the users machine.
As highlighted by @kdzwinel - This could be an increased exposure to other CPU profiling exposed via other methods as the codecs will allow for granular GPU hardware acceleration
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified. Start by reviewing the referenced privacy review and the WebCodecs codec and hardware-acceleration behavior; the issue is done only when the project has an agreed mitigation or documented resolution for timing-based CPU and GPU profiling exposure.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100