/me goes and looks at PKCS#5 <http://tools.ietf.org/html/rfc2898#section-6.2>
Indeed, PBES2 is very generally defined. To summarize: 1. Derive key with PBKDF2 2. Encrypt content with some encryption algorithm That's exactly what we're doing here (with AES-KW as they encryption algorithm), so PBES seems appropriate. On Mon, Aug 26, 2013 at 1:28 PM, Matt Miller (mamille2) <[email protected]>wrote: > On Aug 19, 2013, at 4:10 PM, jose issue tracker < > [email protected]> wrote: > > > #182: PBSE2 should be PBKDF2 > > > > In going back and scanning RFC 2898, PBES2 combines a password-based key > > derivation function, which shall be PBKDF2 (Section 5.2) for this version > > of PKCS #5, with an underlying encryption scheme. > > > > However we are just using it as a KDF function rather than the combined > > function. > > > > That is not correct. The (encrypt) algorithm expects a Content Encryption > Key as an input, and the output is the wrapped Content Encryption Key, not > the derived key. > > > - m&m > > Matt Miller < [email protected] > > Cisco Systems, Inc. > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose > >
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
