26214 2014-06-26 22:32:42 +0000 Define consistent error when calling exportKey() with unsupported key format 2014-09-26 00:46:18 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC Linux RESOLVED FIXED P2 normal --- 1 ericroman sleevi public-webcrypto watsonm oldest_to_newest 108404 0 ericroman 2014-06-26 22:32:42 +0000 When calling importKey() with a "format" that is not applicable to the algorith, the spec says to return a NotSupportedError. So I would expect when calling exportKey() with a format that is not applicable for the key's algorithm, to similarly return a NotSupportedError. However as currently written there are per-algorithm inconsistencies: * The RSA and EC keys define it as returning NotSupported * AES-GCM defines it as DataError * AES-CTR leaves it undefined * AES-CBC leaves it undefined * AES-CMAC leaves it undefined Proposal: Fail with NotSupportedError in all cases. 111955 1 watsonm 2014-09-22 17:54:14 +0000 I agree with the proposal to always use NotSupportedError in this case. 112229 2 watsonm 2014-09-26 00:46:18 +0000 https://dvcs.w3.org/hg/webcrypto-api/rev/5b2b1e7a8d4c https://dvcs.w3.org/hg/webcrypto-api/rev/939143e3319f