This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24056 - Algorithms supporting encrypt/decrypt should also support wrap/unwrap
Summary: Algorithms supporting encrypt/decrypt should also support wrap/unwrap
Status: RESOLVED FIXED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Mark Watson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-10 18:54 UTC by Mark Watson
Modified: 2014-01-25 01:26 UTC (History)
1 user (show)

See Also:

Attachments

Description Mark Watson 2013-12-10 18:54:09 UTC 
With our definition of wrap == export + encrypt and unwrap == decrypt + import, any encryption/decryption algorithm can be used for wrap / unwrap.
Comment 1 Alexey Proskuryakov 2013-12-13 18:10:43 UTC 
There could be some complications with JWK import/export here. My understanding is that in JOSE, the sets of algorithms used for encryption and for key wrapping are disjoint (see e.g. A128GCM vs. A128GCMKW).

This is not an objection, just something to consider.
Comment 2 Mark Watson 2014-01-24 23:44:02 UTC 
This was apparently agreed in Shenzhen. There will be no custom padding defined for the case where the export step produces output of a size that the encryption algorithm does not support.
Comment 3 Mark Watson 2014-01-24 23:44:02 UTC 
This was apparently agreed in Shenzhen. There will be no custom padding defined for the case where the export step produces output of a size that the encryption algorithm does not support.