I think there is some confusion. We support this for encryption + integrity now.
I think the question in the room was should we add a way in JWE to HMAC the message body with a key that is sent in the same message that is signed by another key. I think the questions to the list are not entirely consistent with what was discussed in the room in some cases. Perhaps others can clarify if my recollection is wrong. John B. On 2012-08-29, at 9:04 AM, prateek mishra <[email protected]> wrote: > YES, this is a significant use-case, wherein a server is provisioned with a > certificate and clients generate a symmetric key > (per session or transaction). Said key is encrypted using the server public > key and used for integrity protection and > encryption during the session/transaction. >> <CHAIR> >> >> If you voted at the face-2-face please do not vote again. If you want to >> provide comments please change the title from POLL to DISCUSS. >> >> Should we add the ability to have a randomly generated MAC key protected by >> a different key? The other key could be either a pre-shared symmetric key >> or a public key. >> >> >> >> Room vote: 3 yes, 5 no, 3 discuss >> >> >> _______________________________________________ >> jose mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/jose > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
