Threat Model: Use consistent terminology
At 2013-07-13 21:42:57 None wrote: Synopsis
The threat model uses inconsistent terminology in some places, such as "Backend Operator" versus "oonib operator". Or "ooni-backend" versus "OONIB" versus "Ooni-B" versus "oonib".
Close Criteria
Find as many cases as possible and switch to consistent terminology. Some guidelines:
- Use the software name, rather than the project or human name. So
oonib
rather thanooni-backend
. - Use the software name in the roles.
ooni-probe Operator
instead ofProbe Operator
andoonib Operator
instead ofBackend Operator
An exception: We want to generalize mlab-ns
Operator to Directory Service Operator
. See #136 (moved). So another guideline:
- Make definitions general to any potential Ooni deployment, not specific to MLab.
This issue was automatically migrated from github issue https://github.com/TheTorProject/ooni-probe/issues/142