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

Update js content to use aes128gcm standard encryption #16

Closed
jrconlin opened this issue May 18, 2020 · 1 comment · Fixed by #18
Closed

Update js content to use aes128gcm standard encryption #16

jrconlin opened this issue May 18, 2020 · 1 comment · Fixed by #18
Assignees
@jrconlin
Labels
Low priority While still a valid issue, this is very low priority.

Comments

@jrconlin
Copy link
Member

Currently, the page uses the old "aesgcm" encoding. We should update to use the RFC compliant aes128gcm.

Page should also:

  • update to use new DOM subscription requirements
  • use more modern calls.
    etc.
@jrconlin jrconlin self-assigned this May 18, 2020
This was referenced Sep 22, 2020
Open
Open
@jrconlin jrconlin added the Low priority While still a valid issue, this is very low priority. label Oct 12, 2020
@saschanaz
Copy link

saschanaz commented Oct 31, 2024 •
edited
Loading

Might want to steal from my WPT implementation: https://phabricator.services.mozilla.com/D222665#change-GCzxUM80jDsK

@p1gp1g p1gp1g mentioned this issue Mar 12, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jrconlin jrconlin

Labels
Low priority While still a valid issue, this is very low priority.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Follow RFC8291 and RFC8292 p1gp1g/WebPushDataTestPage
2 participants
@jrconlin @saschanaz