Interpolating the rest of the thread, I think what is meant here is the " A128CBC-HS256" algorithm in JWA, which synthesizes an authenticated encryption algorithm out of AES-CBC and HMAC: < http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11#section-4.8.3 >
The CMS parallel that Russ raised is actually RFC 6476, which adapts the TLS A&E scheme to CMS: <http://tools.ietf.org/html/rfc6476> The obvious counter-argument to including this in WebCrypto is that the whole point of the algorithm is that it's easy to polyfill. In fact, an application could implement it today using the existing AES-CBC and HMAC functions. The only trouble would be getting the wrapped key out with wrapKey, since the key for the overall operation would be the concatenation of the two individual keys. --Richard On Fri, Jul 5, 2013 at 10:02 PM, Ryan Sleevi <[email protected]> wrote: > On Fri, July 5, 2013 2:31 pm, Jim Schaad wrote: > > Are we going to lobby to get this algorithm adopted as an algorithm by > the > > WebCrypto group? > > > > > > > > Jim > > > > > > > > _______________________________________________ > > jose mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/jose > > > > Can you explain what you mean, Jim? > > AES-CBC has been listed in the Web Cryptography API since the FPWD. > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose >
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
