259
edits
CloudServices/Notifications/Push/Security: Difference between revisions
CloudServices/Notifications/Push/Security (view source)
Revision as of 00:42, 2 December 2011
, 2 December 2011→Security Considerations
| Line 57: | Line 57: | ||
Along with a mailbox URL, the <b>Device</b> will call the <tt>requestPermission</tt> callback with a secret key. If the <b>App (Server)</b> stores both the URL and the secret key, it can use symmetric encryption to encrypt the message, which will be decrypted on the client. | Along with a mailbox URL, the <b>Device</b> will call the <tt>requestPermission</tt> callback with a secret key. If the <b>App (Server)</b> stores both the URL and the secret key, it can use symmetric encryption to encrypt the message, which will be decrypted on the client. | ||
=== Security Checklist === | |||
These questions should be answered by the defenses listed above. | |||
* How does the push service know it's talking to the right device? | |||
* How does the push service know this message is really from <domain>? | |||
* How does the user trust that a message is from <domain>? | |||
* How does a site prevent the push service from reading its messages on the server? | |||
== Prior Art == | == Prior Art == | ||