Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:59:00Zhttps://gitlab.torproject.org/legacy/trac/-/issues/31771bugs.torproject.org has some issue with the certificate2020-06-13T16:59:00ZAntonelaantonela@torproject.orgbugs.torproject.org has some issue with the certificateWhen I want to visit https://bugs.torproject.org/ Firefox says:
"Error code: SEC_ERROR_UNKNOWN_ISSUER"
OS: MacOS Mojave 10.14
Chrome https://share.riseup.net/#CYonUWZTp0NFD7xUGnqKwg
Firefox https://share.riseup.net/#oGJLGO3dncEzfaqZfrEhFgWhen I want to visit https://bugs.torproject.org/ Firefox says:
"Error code: SEC_ERROR_UNKNOWN_ISSUER"
OS: MacOS Mojave 10.14
Chrome https://share.riseup.net/#CYonUWZTp0NFD7xUGnqKwg
Firefox https://share.riseup.net/#oGJLGO3dncEzfaqZfrEhFgJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31760swati needs a trac account2020-06-13T16:59:00ZGabagaba@torproject.orgswati needs a trac accountHi!
Swati, our technical writer for the google season of docs is in needs of a trac account. Can somebody create one for her? Her email is swati.kgp13 at gmail.
Thanks!Hi!
Swati, our technical writer for the google season of docs is in needs of a trac account. Can somebody create one for her? Her email is swati.kgp13 at gmail.
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31746Ticket application keeps hanging2020-06-13T16:58:59ZTracTicket application keeps hangingI submitted two tickets for the same issue because it said that my ticket was not submitted so I apologize for the redundancy
**Trac**:
**Username**: MagikI submitted two tickets for the same issue because it said that my ticket was not submitted so I apologize for the redundancy
**Trac**:
**Username**: MagikJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31733Add gus@tpo as moderator for community team mailing list2020-06-13T16:58:58ZGusAdd gus@tpo as moderator for community team mailing listJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31690study trac.torproject.org archival possibilities2020-06-13T16:58:54Zanarcatstudy trac.torproject.org archival possibilitiesthis is a split out of #30857 to discuss specifically the question of if/how to archive trac.torproject.org.
As mentioned in that ticket, there are a few options on how to deal with trac, provided we have another system we want to use:
...this is a split out of #30857 to discuss specifically the question of if/how to archive trac.torproject.org.
As mentioned in that ticket, there are a few options on how to deal with trac, provided we have another system we want to use:
1. **the golden redirect set**: every migrated ticket and wiki page has a corresponding ticket/wiki page in GitLab and a gigantic set of redirection rules makes sure they are mapped correctly. probably impractical, but solves the maintenance problem possibly forever.
2. **read-only Trac**: user creation is disabled and existing users are locked from making any change to the site. only a temporary or intermediate measure.
3. **fossilization**: Trac is turned into a static HTML site that can be mirrored like any other site. can be a long term solution and a good compromise with a possibly impossible to design and therefore failing (because incomplete) set of redirection rules.
4. **destruction**: we hate the web and pretend link rot is not a problem and just get rid of the old site, assuming everything is migrated and people will find their stuff eventually. probably not an option.
5. **redirect to the wayback machine**: like **fossilization**, but delegate to the internet archive and hope for the best
== Archive team work
With my archive team hat, I was able to coordinate a first archival of the website during the summer of 2019, as documented in #30857. This is an attempt at doing "3. **fossilization**".
All those jobs end up populating the wayback machine at web.archive.org, but are also available as WARC files, an archival format for web pages.
A first archival of all tickets up to #30856 has been performed here:
https://archive.fart.website/archivebot/viewer/job/5vytc
It's about 600MB of compressed HTML (more or less).
Then a full archival job of the entire site was performed here:
https://archive.fart.website/archivebot/viewer/job/bpu6j
It created about 10GB of WARC files, crawled over 730,000 links (including external sites linked from Trac) and 105.34GiB of data. It took over 5 days:
```
2019-06-17 01:49:02,514 - wpull.application.tasks.stats - INFO - Duration: 5 days, 7:32:55. Speed: 0.0 B/s.
2019-06-17 01:49:02,514 - wpull.application.tasks.stats - INFO - Downloaded: 732488 files, 105.4 GiB.
```
== Other statistics
Archiving the server itself means dealing with:
* ~1GB of attachments
* 4GB PostgreSQL database
The actual server uses around 25GB of disk space because of random junk here and there but that's the very minimum it can be trimmed down to. naturally, we can keep *that* data forever, the problem is keeping the app running on top of that... That would be some incarnation of "4. **destruction**".Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31411trac having a "two generals" problem2020-06-13T16:58:38ZTractrac having a "two generals" problemwhen i created an account to make my bug reports trac identified me as spam [? probably set to default here] and so made me do a captcha. after doing captcha i got two little infobars. one said capcha failed, one said success account cre...when i created an account to make my bug reports trac identified me as spam [? probably set to default here] and so made me do a captcha. after doing captcha i got two little infobars. one said capcha failed, one said success account created. somethings getting hung up in the inbetween here and somebody aint getting their "message received" message. now im an amateur so i have NO clue as to the root of the issue but it sure is a weird one from the outset
**Trac**:
**Username**: nullbulousJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31381Cannot close the ticket #243512020-06-13T16:58:37ZcypherpunksCannot close the ticket #24351https://trac.torproject.org/projects/tor/ticket/24351https://trac.torproject.org/projects/tor/ticket/24351Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31355admin password to the ux mailing list2020-06-13T16:58:35ZAntonelaantonela@torproject.orgadmin password to the ux mailing listhi! i'm listed as an admin at the ux list but i the password i've been using is not working. Could i have a recovery email?
https://lists.torproject.org/cgi-bin/mailman/listinfo/uxhi! i'm listed as an admin at the ux list but i the password i've been using is not working. Could i have a recovery email?
https://lists.torproject.org/cgi-bin/mailman/listinfo/uxJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31323Add sponsor 44 to trac2020-06-13T16:58:33ZPili GuerraAdd sponsor 44 to tracHi,
Can someone please add sponsor 44 to trac:
- sponsor44
Thanks!
PiliHi,
Can someone please add sponsor 44 to trac:
- sponsor44
Thanks!
PiliJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31150i can create a ticket2020-06-13T16:58:16ZTraci can create a ticketi am not a spammer i swear
**Trac**:
**Username**: fakeanarcati am not a spammer i swear
**Trac**:
**Username**: fakeanarcatJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31052Guest accounts in the ticketing system2020-06-13T16:58:11ZGabagaba@torproject.orgGuest accounts in the ticketing systemRelated to the possible migration from trac into gitlab we have been talking about guest accounts. There was a conversation in irc about having them or not. We need to come to an agreement on what to do about it.
Options in gitlab:
1)...Related to the possible migration from trac into gitlab we have been talking about guest accounts. There was a conversation in irc about having them or not. We need to come to an agreement on what to do about it.
Options in gitlab:
1) Having 'guest accounts' like <name>-guest
Pros:
- anybody can report problems/features and there are less barriers for contribution
Cons:
- spam
2) Opening registration
Pros:
- anybody can report problems/features and there are less barriers for contribution
Cons:
- spam
3) Having accounts by 'invitation only'.
Pros:
- no spam
Cons:
- one more barrier to contribute to TorJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30887Make new network-health@lists.tpo list2020-06-13T16:58:05ZRoger DingledineMake new network-health@lists.tpo listThere is no 'network health' team yet, but there are plenty of tasks that need doing, so let's make a mailing list so we can stay synchronized.
For context, the task areas for this team are in this mail:
https://lists.torproject.org/pip...There is no 'network health' team yet, but there are plenty of tasks that need doing, so let's make a mailing list so we can stay synchronized.
For context, the task areas for this team are in this mail:
https://lists.torproject.org/pipermail/tor-project/2018-December/002138.html
I would like this list to have public archives. I can configure it once it exists. I plan to make listowner (i.e. including me) and dgoulet be the list owners.
I'm going to start out using it as the cc for a whole bunch of mails to relay operators to ask how things are going and to tell them they're running an abandoned version of Tor.
If we need a short description of the list, we could use something like "Tor Network Health Team coordination list".
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30757Add new sponsor to trac2020-06-13T16:57:53ZGabagaba@torproject.orgAdd new sponsor to tracAdd a new sponsor to trac:
* sponsor30-must
* sponsor30-can
* sponsor30
Thanks!Add a new sponsor to trac:
* sponsor30-must
* sponsor30-can
* sponsor30
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30669add new sponsor to trac2020-06-13T16:57:48ZGabagaba@torproject.orgadd new sponsor to tracAdd a new sponsor to trac:
* sponsor28-must
* sponsor28-can
* sponsor28
Thanks!Add a new sponsor to trac:
* sponsor28-must
* sponsor28-can
* sponsor28
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30621remove abuse attachment2020-06-13T16:57:45Zcypherpunksremove abuse attachmentplease remove abuse attachments of wiki site: http://ea5faa5po25cf7fb.onion/projects/tor/wiki/doc/DnsResolver/maraDeadwoodDns
just remove. don't open.please remove abuse attachments of wiki site: http://ea5faa5po25cf7fb.onion/projects/tor/wiki/doc/DnsResolver/maraDeadwoodDns
just remove. don't open.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30603cypherpunks account has been without a privilege to leave tickets for a long ...2020-06-13T16:57:43Zcypherpunkscypherpunks account has been without a privilege to leave tickets for a long timecypherpunks account has been without a privilege to leave tickets for a long time. Even though in the Wiki it had been written it had it. Any questions about this in blog.torproject.org have been censored to prevent people from knowing a...cypherpunks account has been without a privilege to leave tickets for a long time. Even though in the Wiki it had been written it had it. Any questions about this in blog.torproject.org have been censored to prevent people from knowing about that.
What the hell have it been? This was definitely inacceptable behavior for such a project. It had prevented people from reporting vulnerabilities. I now consider Tor Project as hijacked by NSA, CIA, FBI, GCHQ, MI5, MI6, BND and other similar orgs.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30528please create a l10n mailing list2020-06-13T16:57:41Zemmapeelplease create a l10n mailing listit would be nice to have a mailing list for l10n issues.
can be called tor-l10n so it is in line with the irc channel.
i want to administer it and invite people to join the mailing list to know more about translations and also we could...it would be nice to have a mailing list for l10n issues.
can be called tor-l10n so it is in line with the irc channel.
i want to administer it and invite people to join the mailing list to know more about translations and also we could use the address for 'reporting errors on translations' or other things people wants to know.
It will be a public list.
Pili also thinks it is a good idea.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30513Add {arlolra, cohosh, dcf, phw} to default Cc of Circumvention/Snowflake tickets2020-06-13T16:57:40ZDavid Fifielddcf@torproject.orgAdd {arlolra, cohosh, dcf, phw} to default Cc of Circumvention/Snowflake ticketsRecently the Obfuscation/Snowflake component was renamed to Circumention/Snowflake. The change seems to have lost the default Cc that was set up in #23860. See comment:1:ticket:30510 for example. Is it possible to have these users Cced b...Recently the Obfuscation/Snowflake component was renamed to Circumention/Snowflake. The change seems to have lost the default Cc that was set up in #23860. See comment:1:ticket:30510 for example. Is it possible to have these users Cced by default in new Circumvention/Snowflake tickets?
```
arlolra cohosh dcf phw
```Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30408Please create "Sponsor 48" on trac2020-06-13T16:57:37ZPili GuerraPlease create "Sponsor 48" on tracCan we add a "Sponsor48" entry in the Sponsor field in trac?
This is for Google Season of Docs.Can we add a "Sponsor48" entry in the Sponsor field in trac?
This is for Google Season of Docs.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30165Please create an anti-censorship-team@ list2020-06-13T16:57:30ZPhilipp Winterphw@torproject.orgPlease create an anti-censorship-team@ list```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi sysadmins,
Can you please create the following mailing list for the anti-censorship team?
* List name: anti-censorship-team@lists.torproject.org
* Email address of list maintainer...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi sysadmins,
Can you please create the following mailing list for the anti-censorship team?
* List name: anti-censorship-team@lists.torproject.org
* Email address of list maintainer: phw@torproject.org
* List description: Anti-censorship team discussion list
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCAAdFiEEvWUVvXkFpAp3gtRWD9lfHTpZekgFAlywv1gACgkQD9lfHTpZ
ekgwugwAgjFyiC4VtRAlm6tHy42/b3efNPWz7QSrONyLQEE1maP3mX1bgJks6LwI
3RfKFljXswTosVBNPgmlS0QKyhtSyAh/+jTldglH+l5CFYan1eIjwc6qUELUxCr4
LaW8+Y2FZ5LuBzh9xZVNW1V/lWYF+ZF9eTvd/zK4+soRLnd8B1PliIgdOUWnrmFV
2X9ruwE7RKxaFzJE3lzMme/aIjWuFp2qRg4ASJd3l4573D2dm4Pnu4PwdPeV84aD
Tc4NO3wV6iPmKqs2SOlxkA7BSONbNabXornG9gzbin09Uq/0iLT0yjujUU/vea0H
hTpXTAJLPHlFUNOATvjmpwqlQr7wUYrsMRrmYr/Ke2CqqTvb/lF8y9mSdsfGJ1Hs
vU8IZu4tjzNAvi7s2Wwq1VcRvZUCmkHrx5bA97je2j0PTCs1lqPzKglxKZFfohnB
DLnjcXeEkNq/UzbRrOoaMkxo3Ig46yTpVBwVDCNvcLSRxZyC8Dk1Nj5UI+YksJPM
FM9echsk
=8rgZ
-----END PGP SIGNATURE-----
```Jens KubiezielJens Kubieziel