Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Applicability of authenticated encryption? #36

Open
troyronda opened this issue Jan 20, 2020 · 4 comments
Open

Applicability of authenticated encryption? #36

troyronda opened this issue Jan 20, 2020 · 4 comments

Comments

@troyronda
Copy link

I am curious about the applicability of authenticated encryption to this spec. E.g., ECDH-1PU IETF draft.

@llorllale
Copy link

And if that, then relax the reliance on nested jwts for jwms

@tplooker
Copy link
Member

tplooker commented Jan 20, 2020

In what context in particular? I think ECDH-1PU is a great draft and implementers of JWM can easily employ the encryption technique outlined?

@llorllale I agree, when authenticated encryption is employed, a digital signature over the internal payload (achieved as a nested JWM with a JWE wrapping a JWS) isn't needed.

The reason I would regard nested JWMs as still a valid concept in this draft is for instances where authenticated encryption is not employed but authenticating the sender is still advantageous.

@troyronda
Copy link
Author

I agree, when authenticated encryption is employed, a digital signature over the internal payload (achieved as a nested JWM with a JWE wrapping a JWS) isn't needed.

Agree.

The reason I would regard nested JWMs as still a valid concept in this draft is for instances where authenticated encryption is not employed but authenticating the sender is still advantageous.

Makes sense - there are still use cases where someone wants to nest a JWS.

@llorllale
Copy link

Yes. Example: Alice forwards to Bob a JWS produced by Carol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants