The Web Crypto API available in most browsers supports both AES-GCM and AES-KW for key wrapping.
There are examples for AES-KW and AES-GCM performing key wrapping, and a popular live table indicates without any supporting reference that both are "recommended".
Is there a practical or theoretical reason why one might choose GCM over KW and vice-versa?
ivis not needed for AES-KW, however the examples for the API for WebCrypto seems to use aniv. The WebCrypto standard seems to indicate thatwrapKeydoes not require any arguments. Does it look like anivcan safely be omitted? – Brian M. Hunt Oct 17 '18 at 13:43