169
edits
CloudServices/Notifications/Server: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Notifications/Server (view source)
Revision as of 23:43, 15 April 2011
, 15 April 2011→Provide Mechanism to Move Client to a Different POST Office
| Line 52: | Line 52: | ||
== Cons == | == Cons == | ||
* Could have security implications? (if attacker took control of Mozilla's servers and moved all its users to another notification server, for example) | * Could have security implications? (if attacker took control of Mozilla's servers and moved all its users to another notification server, for example) | ||
= Make POST Office in Charge of Generating Subscription Token = | |||
== Pros == | |||
* One less thing clients can screw up (also prevents generation of insecure tokens such as AAAAAAA...A) | |||
== Cons == | |||
* If other users implemented a POST Office, they could assign tokens that are personally identifying (is this really something we need to worry about? Who would even bother doing this?) | |||