WebAPI/Security/FMRadioAPI: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
== FM Radio API==
==WebFM API==


Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=749053
References:
*https://bugzilla.mozilla.org/show_bug.cgi?id=749053
*https://groups.google.com/d/topic/mozilla.dev.webapi/PraULCQntqA/discussion


Brief purpose of API: FM radio feature.
Brief purpose of API: FM radio feature.
Line 22: Line 24:
Potential mitigations: An app or page can't access any of the radio API if another page/app is currently using it. Whenever a page/app uses the API for the first time since another page/app used it, always reset the current frequency to some specified value
Potential mitigations: An app or page can't access any of the radio API if another page/app is currently using it. Whenever a page/app uses the API for the first time since another page/app used it, always reset the current frequency to some specified value


=== Trusted (authenticated by publisher) ===
== Privileged (approved by app store) ==
Use cases for certified code: radio app
Use cases for privileged code: radio app


Authorization model: Implicit
Authorization model: Implicit
Line 29: Line 31:
Potential mitigations: Same as for unauthenticated.
Potential mitigations: Same as for unauthenticated.


=== Certified (vouched for by trusted 3rd party) ===
== Certified (system-critical apps) ==
Use cases for certified code:  radio app
Use cases for certified code:  radio app


Confirmed users
717

edits