WebAPI/Security/Vibration: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 21: Line 21:


== Privileged (approved by app store) ==
== Privileged (approved by app store) ==
<p>Use cases for authenticated code: [Same]
Use cases for privileged code: [Same]
</p><p>Authorization model: Implicit
</p><p>Potential mitigations:
</p>


== Privileged (approved by app store) ==
Authorization model: Implicit
Use cases for privileged code:
 
Potential mitigations:
 
== Certified (system-critical apps) ==
Use cases for certified code: [Same]


Authorization model: Implicit
Authorization model: Implicit
Line 33: Line 34:
Potential mitigations:
Potential mitigations:


NotesThis API may be implicitly granted.  User can deny from Permission Manager to over-ride an abusive app.
==Notes==
This API may be implicitly granted.  User can deny from Permission Manager to over-ride an abusive app.
Since only foreground content can trigger vibrator, this seems equivalent to other potentially annoying feedback mechanisms and should be implicit for uninstalled web content.
Since only foreground content can trigger vibrator, this seems equivalent to other potentially annoying feedback mechanisms and should be implicit for uninstalled web content.


== Certified (system-critical apps) ==
__NOTOC__
Same as Privileged
Confirmed users
717

edits

Navigation menu