Loading tsa/howto/grafana.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -13,7 +13,7 @@ Puppet implementation Grafana was installed with Puppet using the upstream Debian package, following a debate regarding the merits of Debian packages versus Docker containers when neither are trusted, see [this comment](https://bugs.torproject.org/29684#comment:3) for a summary. comment](https://gitlab.torproject.org/legacy/trac/-/issues/29684#note_2316840) for a summary. Some manual configuration was performed after the install. An admin password reset on first install, stored in `tor-passwords.git`, in Loading tsa/howto/irc.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -175,7 +175,7 @@ automatically regenerate it every ~90 days :) They don't need to put the cert/keys anywhere special for you as long as the ircbouncer user can access them. See how in [this ticket comment](https://bugs.torproject.org/32532#comment:5) [this ticket comment](https://gitlab.torproject.org/legacy/trac/-/issues/32532#note_2342136) ... root@chives:~# ls -al /etc/ssl/private/ircbouncer.torproject.org.* /etc/ssl/torproject/certs/ircbouncer.torproject.org.crt* Loading tsa/howto/puppet.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -589,7 +589,7 @@ as well. Revocation procedures problems were discussed in [33587][] and [33446][]. [33587]: https://bugs.torproject.org/33587 [33446]: https://bugs.torproject.org/33446#comment:17 [33446]: https://gitlab.torproject.org/legacy/trac/-/issues/33446#note_2349434 1. Clean the certificate on the master Loading tsa/howto/submission.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -90,7 +90,7 @@ much problem, their emails often get dropped to the floor when It is suspected that users are having those problems because the originating servers are not in the `torproject.org` domain. The hope is that setting up a new server inside that domain would help with delivery. There's anecdotal evidence (see [this comment](https://bugs.torproject.org/30608#comment:8) for delivery. There's anecdotal evidence (see [this comment](https://gitlab.torproject.org/legacy/trac/-/issues/30608#note_2325187) for example) that delivery emails from existing servers (over SSH to `iranicum`, in that example) improves reliability of email delivery significantly. Loading tsa/howto/upgrades.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -32,7 +32,7 @@ upgrade, however. Team policies: * anti-censorship: TBD * metrics: one or two work-day advance notice ([source](https://bugs.torproject.org/32998#comment:2)) * metrics: one or two work-day advance notice ([source](https://gitlab.torproject.org/legacy/trac/-/issues/32998#note_2345807)) * funding: schedule a maintenance window * git: TBD * gitlab: TBD Loading Loading
tsa/howto/grafana.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -13,7 +13,7 @@ Puppet implementation Grafana was installed with Puppet using the upstream Debian package, following a debate regarding the merits of Debian packages versus Docker containers when neither are trusted, see [this comment](https://bugs.torproject.org/29684#comment:3) for a summary. comment](https://gitlab.torproject.org/legacy/trac/-/issues/29684#note_2316840) for a summary. Some manual configuration was performed after the install. An admin password reset on first install, stored in `tor-passwords.git`, in Loading
tsa/howto/irc.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -175,7 +175,7 @@ automatically regenerate it every ~90 days :) They don't need to put the cert/keys anywhere special for you as long as the ircbouncer user can access them. See how in [this ticket comment](https://bugs.torproject.org/32532#comment:5) [this ticket comment](https://gitlab.torproject.org/legacy/trac/-/issues/32532#note_2342136) ... root@chives:~# ls -al /etc/ssl/private/ircbouncer.torproject.org.* /etc/ssl/torproject/certs/ircbouncer.torproject.org.crt* Loading
tsa/howto/puppet.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -589,7 +589,7 @@ as well. Revocation procedures problems were discussed in [33587][] and [33446][]. [33587]: https://bugs.torproject.org/33587 [33446]: https://bugs.torproject.org/33446#comment:17 [33446]: https://gitlab.torproject.org/legacy/trac/-/issues/33446#note_2349434 1. Clean the certificate on the master Loading
tsa/howto/submission.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -90,7 +90,7 @@ much problem, their emails often get dropped to the floor when It is suspected that users are having those problems because the originating servers are not in the `torproject.org` domain. The hope is that setting up a new server inside that domain would help with delivery. There's anecdotal evidence (see [this comment](https://bugs.torproject.org/30608#comment:8) for delivery. There's anecdotal evidence (see [this comment](https://gitlab.torproject.org/legacy/trac/-/issues/30608#note_2325187) for example) that delivery emails from existing servers (over SSH to `iranicum`, in that example) improves reliability of email delivery significantly. Loading
tsa/howto/upgrades.mdwn +1 −1 Original line number Diff line number Diff line Loading @@ -32,7 +32,7 @@ upgrade, however. Team policies: * anti-censorship: TBD * metrics: one or two work-day advance notice ([source](https://bugs.torproject.org/32998#comment:2)) * metrics: one or two work-day advance notice ([source](https://gitlab.torproject.org/legacy/trac/-/issues/32998#note_2345807)) * funding: schedule a maintenance window * git: TBD * gitlab: TBD Loading