Webpush encryption draft changes

[PascalReintjens]

Hello @Minishlink,

I don't know if you have seen the new draft from yesterday, but to me it seems like it modified some things which could require changes in the web-push-php lib: https://www.ietf.org/rfcdiff?url2=draft-ietf-webpush-encryption-05

Thanks for your work :)

[Minishlink]

Newest draft is https://tools.ietf.org/html/draft-ietf-webpush-encryption-08

@jrconlin @gauntface Are there any deadlines for Firefox or Chrome?

[jrconlin]

It's best to consider that your target may be running older versions. There are still quite a few installs of older firefox out there even though we do our best to make sure folks upgrade.

Mozilla is a bit "resource constrained" at the moment, and we've not yet implemented "aes128gcm" draft for desktop.

[Minishlink]

Ok, thanks! I guess the endpoint versions will change when the "aes128gcm" content coding is implemented?

[jrconlin]

Probably not, since the push service doesn't do the decryption. It passes the information through opaquely. More than likely, there would be some bit of information passed along via the User Agent registration call.

I've proposed a modification to the working group to get buy in. (It's a good idea so that various vendors standardize on something.)

https://mailarchive.ietf.org/arch/msg/webpush/uDR2PzpChfn24TwNWZBfR6fuKp0

thanks!

[Minishlink]

I see, thanks for the info :)

[Minishlink]

Available in v4.0.0 :)