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.

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

Jump to bottom

Codec stats reveal hardware information which could be used for fingerprinting #674

Open
henbos opened this issue Sep 13, 2022 · 1 comment
Open

Codec stats reveal hardware information which could be used for fingerprinting #674

henbos opened this issue Sep 13, 2022 · 1 comment
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Comments

@henbos
Copy link
Collaborator

henbos commented Sep 13, 2022

This was previously discussed in #550.

The reason for creating a separate issue specifically for codec is that this information is already exposed in RTCRtpSender/RTCRtpReceiver.getCapabilities(kind).codecs. Therefore it is likely that getCapabilities and getStats codecs will and should be resolved the same way and at the same time.
This was referenced Sep 13, 2022
Closed
Closed
@henbos
Copy link
Collaborator Author

henbos commented Sep 13, 2022

Compare RTCCodecCapability with RTCCodecStats.

Also note that even without these two APIs, the codec information is in either way exposed the SDP (RTCPeerConnection.createOffer() and RTCPeerConnection.createAnswer()).

This makes this issue not just a stats issue, and we may consider moving it to webrtc-pc which is the source of all codec information.

@henbos henbos added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Sep 13, 2022
@w3cbot w3cbot mentioned this issue Sep 13, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@henbos