The "certificate-private key pair" use case, which Mountie just described in detail, is a well-known use case that requires multi-origin access to keys. I am not proposing we solve that problem in the first version of the API, but we should design the API so that it could support the "certificate-private key pair" use case in the future. This seems to require adding an input argument related to key access control to the generateKey() method. We could require that input argument be "same origin policy" in the first version of the API. Wan-TehReceived on Friday, 24 August 2012 19:11:39 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:01:25 UTC