ISSUE-34: Representation of certificates
certificate-format
Representation of certificates
- State:
- POSTPONED
- Product:
- next for Web Crypto API
- Raised by:
- Ryan Sleevi
- Opened on:
- 2012-08-28
- Description:
- Filed as a separate issue from ISSUE-15, which relates to the discovery of certificates once a Key handle is obtained.
If certificates are supported a first-class object, whether for origin-authorized keys (eg: pre-existing certificates) or for certificates related to keys generated by the origin, what is the form these certificates should take? - Related Actions Items:
- No related actions
- Related emails:
- W3C Web Crypto WG - classifying issues (from Virginie.GALINDO@gemalto.com on 2013-02-18)
- PROPOSAL: CLOSE ISSUE-40: How should we define key discovery, noting asynchronicity (from Virginie.GALINDO@gemalto.com on 2013-02-11)
- Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (from watsonm@netflix.com on 2013-02-11)
- Re: W3C Web Crypto WG - classifying issues (from sleevi@google.com on 2013-02-07)
- Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (from sleevi@google.com on 2013-02-07)
- Re: PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
- PROPOSAL: ??? ISSUE-24: Defining a synchronous API (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
- PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
- PROPOSAL: Postpone ISSUE-26: Should key generation be allowed to specify multi-origin access (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
- PROPOSAL: Move ISSUE-30: How does the application know where the key is stored? (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
- PROPOSAL: Postpone ISSUE-34: Representation of Certificates (was Re: W3C Web Crypto WG - classifying issues) (from sleevi@google.com on 2013-02-07)
- PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (from sleevi@google.com on 2013-02-07)
- W3C Web Crypto WG - classifying issues (from Virginie.GALINDO@gemalto.com on 2013-02-07)
- Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from watsonm@netflix.com on 2013-02-04)
- RE: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Asad.Ali@gemalto.com on 2013-02-04)
- Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from S.Durbha@cablelabs.com on 2013-02-04)
- W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-02-04)
- PROPOSAL: Close ISSUE-34 - Representation of certificates (from sleevi@google.com on 2013-01-31)
- crypto-ISSUE-34 (certificate-format): Representation of certificates [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-28)
Related notes:
No additional notes.
Display change log
