I have revised the wiki page [1] with:

1. A more detailed assessment of the "captured signing key" threat, including a 
breakdown of the theft-detected and theft-not-detected scenario.

2. A first cut at revocation and receipt-reissuance, which would be required 
when a signing key theft is detected.  Notably, receipt reissuance will require 
new behavior in the user agent (since only it is empowered to go back to the 
Marketplace and ask for a new receipt).  This will need to be vetted by the 
apps team for desktop, Android, and B2G.

m

[1] https://wiki.mozilla.org/Apps/WebApplicationReceipt/GenerationService

On Mar 28, 2012, at 2:55 PM, Mike Hanson wrote:

> They're in the text, just not wikified.  I'll fix it.
> 
> m
> 
> On Mar 28, 2012, at 1:21 PM, Michael Coates wrote:
> 
>> There is a reference in the wiki to appendices. Can we add those?
>> 
>> -Michael
>> 
>> On 3/28/12 10:54 AM, Raymond Forbes wrote:
>>> Hello,
>>> 
>>> We are in the process of defining and review the process we use
>>> for generating and revoking receipts.  This is a complicated
>>> process that involves signing with a Hardware Security Module.
>>> Please take a look at the spec that we have so far and give any
>>> feed back you have.  I have included the architect of the spec and
>>> developers who are responsible for implementing if you have any
>>> questions.  Let's have a discussion on how we can make this as
>>> secure as possible.
>>> 
>>> I will keep the wiki updated from this discussion.
>>> 
>>> https://wiki.mozilla.org/Apps/WebApplicationReceipt/GenerationService
>>> 
>>> thanks! -Raymond
> 
> _______________________________________________
> dev-webapps mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-webapps

_______________________________________________
dev-security mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security

Reply via email to