You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The future is in aes128gcm encryption, aesgcm being deprecated. The changes are not big, but quite tricky to get right. There's no idea when aesgcm is going to be blocked by the browsers or which draft will be the one that works with Chrome and Firefox.
Anyways, you can follow and participate in the aes128gcm branch.
The text was updated successfully, but these errors were encountered:
Hello @pimeys, aesgcm seems to be blocked on the new Chromium-based version of Edge. Would you be able to update the package with support for aesgcm128?
I haven't been working on this field for the last two years, and I also do not have a Windows computer.
I followed the later specs, trying to get this working back then without success. The branch is still available if somebody wants to give it a try. The best docs are in the RFC for http-ece encryption.
The future is in aes128gcm encryption, aesgcm being deprecated. The changes are not big, but quite tricky to get right. There's no idea when aesgcm is going to be blocked by the browsers or which draft will be the one that works with Chrome and Firefox.
Anyways, you can follow and participate in the aes128gcm branch.
The text was updated successfully, but these errors were encountered: