> It would be great if the spec also specified that the phone needs to
> provide a resource consumption manager.

Perhaps "should" rather than "needs to".  This is a non-trivial thing
to do, in general.  Not that we shouldn't do it, but I don't think we
should say that we're in violation of the spec if we don't.

On Tue, Apr 17, 2012 at 12:26 AM, Adrienne Porter Felt <a...@berkeley.edu> 
wrote:
> It would be great if the spec also specified that the phone needs to
> provide a resource consumption manager.  That way concerned users could see
> which trusted/certified apps are responsible for a short battery life, if
> the phone is being drained too fast.
>
> On Sun, Apr 15, 2012 at 11:18 PM, Lucas Adamski <ladam...@mozilla.com>wrote:
>
>> Please reply-to dev-weba...@lists.mozilla.org
>>
>> Name of API: Resource Lock API
>> Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=697132
>>
>> Brief purpose of API: Prevent the screen from being dimmed or switched off
>> General Use Cases: Request a lock to stop the screen from being dimmed,
>> even if the user is idle (eg. watching a movie)
>>
>> Inherent threats: Drain power, annoyances
>>
>> Threat severity: Low
>>
>> == Regular web content (unauthenticated) ==
>> Use cases for unauthenticated code: Same as General
>> Authorization model for normal content: Explicit
>> Authorization model for installed content:Implicit
>> Potential mitigations:
>>
>> == Trusted (authenticated by publisher) ==
>> Use cases for authenticated code: Same as General
>> Authorization model:
>> Potential mitigations:
>>
>> == Certified (vouched for by trusted 3rd party) ==
>> Use cases for certified code:  Same as General
>> Authorization model:
>> Potential mitigations:
>>
>> _______________________________________________
>> dev-security mailing list
>> dev-security@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-security
>>
> _______________________________________________
> dev-b2g mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-security mailing list
dev-security@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security

Reply via email to