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.

Sign up for GitHub

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

Jump to bottom

Adjust Aes128GcmEncodedContent and Aes128GcmEncoding so it can be used for Web Push Encryption #3

Closed
2 tasks done
tpeczek opened this issue Dec 21, 2017 · 0 comments
Closed
2 tasks done

Adjust Aes128GcmEncodedContent and Aes128GcmEncoding so it can be used for Web Push Encryption #3

tpeczek opened this issue Dec 21, 2017 · 0 comments
Assignees
@tpeczek
Labels
Enhancement High
Milestone
v1.1.0

Comments

@tpeczek
Copy link
Owner

tpeczek commented Dec 21, 2017 •
edited
Loading

The Web Push Encryption (RFC 8291) is using encrypted content encoding but some changes are needed in order for Aes128GcmEncodedContent and Aes128GcmEncoding to be used for this puspose:

  • Drop (probably incorrect) keying material size limit of 16 bytes (Web Push Encryption is using 32 bytes keying material)
  • Add option for providing keying material identificator as byte array.
@tpeczek tpeczek added this to the v1.1.0 milestone Dec 21, 2017
@tpeczek tpeczek self-assigned this Dec 21, 2017
@tpeczek tpeczek mentioned this issue Dec 21, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tpeczek tpeczek

Labels
Enhancement High
Projects
None yet
Milestone
v1.1.0
Development

No branches or pull requests
1 participant
@tpeczek