Changes

Page history
use a name= instead of id= authored by anarcat's avatar anarcat 
back in 9d9aed39 (use <a id=""> instead of name, as name is not HTML5,
2023-06-01) we switched everything to id= but overlooked that id=
actually gets redacted by GitLab's sanitizer. With this, we should be
able to get the anchors through the filter even if it generates
non-conformant HTML5.
Show whitespace changes
Inline Side-by-side
doc/accounts.md
View page @ 0a71e7cb
...@@ -21,7 +21,7 @@ policy](https://gitweb.torproject.org/community/policies.git/plain/membership.tx ...@@ -21,7 +21,7 @@ policy](https://gitweb.torproject.org/community/policies.git/plain/membership.tx
in case of discrepancy between the two documents, the membership in case of discrepancy between the two documents, the membership
policy overrules this document. policy overrules this document.
## <a id="ldap-or-alias">Decision tree: LDAP account or email alias?</a> ## ## <a name="ldap-or-alias">Decision tree: LDAP account or email alias?</a> ##
Here is a simple decision tree to help you decide if a new contributor Here is a simple decision tree to help you decide if a new contributor
needs an LDAP account, or if an email alias will do. (All things being needs an LDAP account, or if an email alias will do. (All things being
...@@ -69,7 +69,7 @@ If none of the above cases apply: ...@@ -69,7 +69,7 @@ If none of the above cases apply:
See <a href="#aliases">Changing email aliases</a> for details. See <a href="#aliases">Changing email aliases</a> for details.
## <a id="new-account">New LDAP accounts</a> ## ## <a name="new-account">New LDAP accounts</a> ##
New accounts have to be sponsored by somebody who already has a torproject.org New accounts have to be sponsored by somebody who already has a torproject.org
account. If you need an account created, please find somebody in the project account. If you need an account created, please find somebody in the project
...@@ -135,7 +135,7 @@ and either approved or rejected. ...@@ -135,7 +135,7 @@ and either approved or rejected.
If the board indicates their assent, the sysadmin team will then create the If the board indicates their assent, the sysadmin team will then create the
account as requested. account as requested.
## <a id="retiring-account">Retiring accounts</a> ## ## <a name="retiring-account">Retiring accounts</a> ##
If you won't be using your LDAP account for a while, it's good security If you won't be using your LDAP account for a while, it's good security
hygiene to have it disabled. Disabling an LDAP account is a simple hygiene to have it disabled. Disabling an LDAP account is a simple
...@@ -151,7 +151,7 @@ are sufficient to confirm a disable request." ...@@ -151,7 +151,7 @@ are sufficient to confirm a disable request."
and accept that email forwarding for the person will stop working too, and accept that email forwarding for the person will stop working too,
or add a new line in the email alias so email keeps working.) or add a new line in the email alias so email keeps working.)
## <a id="get-access">Getting added to an existing group/Getting access to a specific host</a> ## ## <a name="get-access">Getting added to an existing group/Getting access to a specific host</a> ##
Almost all privileges in our infrastructure, such as account on a particular Almost all privileges in our infrastructure, such as account on a particular
host, sudo access to a role account, or write permissions to a specific host, sudo access to a role account, or write permissions to a specific
...@@ -183,14 +183,14 @@ Then you can run: ...@@ -183,14 +183,14 @@ Then you can run:
See also: the `"Host specific passwords"` section below See also: the `"Host specific passwords"` section below
## <a id="aliases">Changing email aliases</a> ## ## <a name="aliases">Changing email aliases</a> ##
Create a ticket specifying the alias, the new address to add, and a Create a ticket specifying the alias, the new address to add, and a
brief motivation for the change. brief motivation for the change.
For specifics, see the "The sponsor will create a ticket" section above. For specifics, see the "The sponsor will create a ticket" section above.
### <a id="new-aliases">Adding a new email alias</a> ### ### <a name="new-aliases">Adding a new email alias</a> ###
#### Personal Email Aliases #### #### Personal Email Aliases ####
...@@ -204,13 +204,13 @@ Contributors. ...@@ -204,13 +204,13 @@ Contributors.
Tor Project Inc and Core Contributors can request group email aliases for new Tor Project Inc and Core Contributors can request group email aliases for new
functions or projects. functions or projects.
### <a id="existing-aliases">Getting added to an existing email alias</a> ### ### <a name="existing-aliases">Getting added to an existing email alias</a> ###
Similar to being added to an LDAP group, the right way to get added Similar to being added to an LDAP group, the right way to get added
to an existing email alias is by getting somebody who is already on to an existing email alias is by getting somebody who is already on
that alias to file a ticket asking for you to be added. that alias to file a ticket asking for you to be added.
## <a id="password-reset">Changing/Resetting your passwords</a> ## ## <a name="password-reset">Changing/Resetting your passwords</a> ##
### LDAP ### ### LDAP ###
...@@ -281,7 +281,7 @@ you don't need to nor can use sudo.) ...@@ -281,7 +281,7 @@ you don't need to nor can use sudo.)
Do mind the delays in LDAP and sudo passwords change, mentioned in the Do mind the delays in LDAP and sudo passwords change, mentioned in the
previous section. previous section.
## <a id="key-rollover">Changing/Updating your OpenPGP key</a> ## ## <a name="key-rollover">Changing/Updating your OpenPGP key</a> ##
If you are planning on migrating to a new OpenPGP key and you also want to If you are planning on migrating to a new OpenPGP key and you also want to
change your key in LDAP, or if you just want to update the copy of your key change your key in LDAP, or if you just want to update the copy of your key
... ...
......