3 ms·
All data brokered by the service must be encrypted to a keypair whose private key is held only by the end user's browser, using the scheme described in the webp
by callahad 11y ago
All data brokered by the service must be encrypted to a keypair whose private key is held only by the end user's browser, using the scheme described in the webpush-encryption IETF draft spec at https://tools.ietf.org/html/draft-ietf-webpush-encryption-01 https://tools.ietf.org/html/draft-ietf-webpush-encryption-01
- deleted 11y ago[deleted]
- drdaeman 11y agoThanks for all your comments! I wonder about metadata, though. While Mozilla doesn't know the contents of messages, it's still generally well aware of who (sender IP) is sending messages to whom (receiver IP) - is that correct? (I suppose this can be somewhat mitigated by running private self-hosted autopush instance and replacing dom.push.serverURL)