{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/496","repository_url":"https://api.github.com/repos/w3c/webrtc-pc","labels_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/496/labels{/name}","comments_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/496/comments","events_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/496/events","html_url":"https://github.com/w3c/webrtc-pc/issues/496","id":132649451,"number":496,"title":"Certificate API: Do we need certificate introspection?","user":{"login":"alvestrand","id":480893,"avatar_url":"https://avatars.githubusercontent.com/u/480893?v=3","gravatar_id":"","url":"https://api.github.com/users/alvestrand","html_url":"https://github.com/alvestrand","followers_url":"https://api.github.com/users/alvestrand/followers","following_url":"https://api.github.com/users/alvestrand/following{/other_user}","gists_url":"https://api.github.com/users/alvestrand/gists{/gist_id}","starred_url":"https://api.github.com/users/alvestrand/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alvestrand/subscriptions","organizations_url":"https://api.github.com/users/alvestrand/orgs","repos_url":"https://api.github.com/users/alvestrand/repos","events_url":"https://api.github.com/users/alvestrand/events{/privacy}","received_events_url":"https://api.github.com/users/alvestrand/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-10T09:40:03Z","updated_at":"2016-02-10T10:22:29Z","closed_at":null,"body":"At the moment, the certificate API we provide is this:\r\n\r\ninterface RTCCertificate {\r\n    readonly        attribute DOMTimeStamp expires;\r\n};\r\n\r\nA question was raised on whether we could tell if a given cert was RSA or ECDSA - there doesn't seem to be one.\r\n\r\nWould it be reasonable to require an introspection API that is able to tell something about it (possibly a subset of its keygen parameters)?"},"comment":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/comments/182296521","html_url":"https://github.com/w3c/webrtc-pc/issues/496#issuecomment-182296521","issue_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/496","id":182296521,"user":{"login":"martinthomson","id":67641,"avatar_url":"https://avatars.githubusercontent.com/u/67641?v=3","gravatar_id":"","url":"https://api.github.com/users/martinthomson","html_url":"https://github.com/martinthomson","followers_url":"https://api.github.com/users/martinthomson/followers","following_url":"https://api.github.com/users/martinthomson/following{/other_user}","gists_url":"https://api.github.com/users/martinthomson/gists{/gist_id}","starred_url":"https://api.github.com/users/martinthomson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/martinthomson/subscriptions","organizations_url":"https://api.github.com/users/martinthomson/orgs","repos_url":"https://api.github.com/users/martinthomson/repos","events_url":"https://api.github.com/users/martinthomson/events{/privacy}","received_events_url":"https://api.github.com/users/martinthomson/received_events","type":"User","site_admin":false},"created_at":"2016-02-10T10:22:29Z","updated_at":"2016-02-10T10:22:29Z","body":"I couldn't think of a reason that this would be needed in practice, hence my initial patch not including anything.  It's easy to implement, I think, but much harder to un-implement.  Does anyone have a use case?"}}