Confirmed users
1,018
edits
Identity/EngPlan/VESEngPlan: Difference between revisions
→External Dependencies
| Line 109: | Line 109: | ||
|mostLikely= 2 days | |mostLikely= 2 days | ||
}} | }} | ||
==== Security Review ==== | |||
====== Checklist ===== | |||
''Product Goal'': | |||
Provide authenticated email addresses as signed identity certificates to client libraries. | |||
''Solutions and Approaches considered'': | |||
The application uses the [https://wiki.mozilla.org/Identity/Verified_Email_Protocol Verified Email Protocol]. Internally, the library uses the following components: | |||
* Services core architecture: | |||
** nginx, python2.6, gunicorn, webob, beaker, etc. | |||
* M2Crypto (contains centralized rsa, Crypto and wraps OpenSSL library) | |||
* python-cjson (high speed json serializer) | |||
''Rationale for final solution'': | |||
M2Crypto was chosen for two reasons: | |||
1. It wraps OpenSLL, meaning that it's not trying to implement function independently of a proven library | |||
2. It's fast. | |||
cjson was chosen because it was far faster than native python JSON libraries, and this library does a LOT of JSON. | |||
We are using redis as our back-end storage because it provides simple key::data storage. The data storage mechanism is abstracted, and can be replaced with another system if need be. | |||
''Known security threats and issues'': | |||
Currently, the "admin" portions (providing the page to allow users to add and disable accounts) is meant to be called only from locally served pages, but could be spoofed. There is currently a stubbed local check function, however no method has yet been implemented. | |||
We are working with ops to identify methods to provide adequate protection from XSS. | |||
''Summary'': | |||
{{WorkItem | {{WorkItem | ||