Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:45:11Zhttps://gitlab.torproject.org/legacy/trac/-/issues/1371Report 8 does not show Mine First2020-06-13T16:45:11ZTracReport 8 does not show Mine Firstsee https://trac.torproject.org/projects/tor/report/8
**Trac**:
**Username**: kebsee https://trac.torproject.org/projects/tor/report/8
**Trac**:
**Username**: kebhttps://gitlab.torproject.org/legacy/trac/-/issues/1516trac testing ticket2020-06-13T16:45:11ZErinn Clarktrac testing ticketFor checking mail, formatting, wiki, attachments, or anything else.For checking mail, formatting, wiki, attachments, or anything else.https://gitlab.torproject.org/legacy/trac/-/issues/1527Add trac plugins2020-06-13T16:45:12ZAndrew LewmanAdd trac pluginsPlease add in the following Trac plugins:
* http://trac-hacks.org/wiki/TracWysiwygPlugin
* http://trac-hacks.org/wiki/MasterTicketsPlugin
* http://trac-hacks.org/wiki/BatchModifyPlugin
* http://trac-hacks.org/wiki/NewsFlashMacro
* ...Please add in the following Trac plugins:
* http://trac-hacks.org/wiki/TracWysiwygPlugin
* http://trac-hacks.org/wiki/MasterTicketsPlugin
* http://trac-hacks.org/wiki/BatchModifyPlugin
* http://trac-hacks.org/wiki/NewsFlashMacro
* http://trac-hacks.org/wiki/ProgressMeterMacro
I'd like these to better use trac for project management. Thanks!Tor: unspecifiedErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1565Identify reason for low dirreq-v3-shares in May and June 20102020-06-13T16:45:13ZKarsten LoesingIdentify reason for low dirreq-v3-shares in May and June 2010The directory mirrors trusted, blutmagie, and vallenator all report very low dirreq-v3-share values in their extra-info descriptors since late May 2010 (see [here](https://trac.torproject.org/projects/tor/ticket/1518#comment:5)).
We wer...The directory mirrors trusted, blutmagie, and vallenator all report very low dirreq-v3-share values in their extra-info descriptors since late May 2010 (see [here](https://trac.torproject.org/projects/tor/ticket/1518#comment:5)).
We were able to identify the introduction of bandwidth-weight values in consensuses as cause for these low directory request shares. See the graph in the attachment. The more consensuses on a given day contain bandwidth-weights (up to 24), the lower are the reported dirreq-v3-shares.
A fix is suggested in #1564. In addition to that, we should calculate shares from descriptors archives rather than believing in what relays say.https://gitlab.torproject.org/legacy/trac/-/issues/1617Stop new bugs from getting added to dead components2020-06-13T16:45:13ZNick MathewsonStop new bugs from getting added to dead componentsThe following components make no sense, and it shouldn't be possible to make bug reports for them:
"None - Backend/Core"
"Tor - Tor Control Panel"The following components make no sense, and it shouldn't be possible to make bug reports for them:
"None - Backend/Core"
"Tor - Tor Control Panel"https://gitlab.torproject.org/legacy/trac/-/issues/1619Trac lists too many TorButton versions.2020-06-13T16:45:13ZTracTrac lists too many TorButton versions.TorButton versions up to 1.4 are listed, while the latest version is 1.3.0-alpha-dev.
**Trac**:
**Username**: katmagicTorButton versions up to 1.4 are listed, while the latest version is 1.3.0-alpha-dev.
**Trac**:
**Username**: katmagichttps://gitlab.torproject.org/legacy/trac/-/issues/1662Separate regular account permissions and dev/admin account permissions2020-06-13T16:45:14ZNick MathewsonSeparate regular account permissions and dev/admin account permissionsI think we need to separate accounts further into "user" and "developer", with basically everybody who works on a project getting called "developer".
In particular, I think that regular users shouldn't have the ability to close bugs, ...I think we need to separate accounts further into "user" and "developer", with basically everybody who works on a project getting called "developer".
In particular, I think that regular users shouldn't have the ability to close bugs, assign bugs, modify bugs, and so on; some of the
If it's at all possible, I'd like users to be able to edit and close bugs that they themselves opened, but not other bugs. I don't know if this is possible with Trac, but it might be neat to check it out.
This proposal should get discussed some and not just implemented on my say-so; If some dev disagrees with me, they should have a chance to object.
See this history of Bug 1656 as an example of why we might want to do this.https://gitlab.torproject.org/legacy/trac/-/issues/1682wikipedia2020-06-13T16:45:14ZTracwikipediaHi!!!!!!!!!!
I wrote again the articles about my BeeFree TorButton and FireFox on this wikipedia!!!!!!!
I did it in the past too!!!!!! i don't know why the pages then disappeared!! I don't know how that's possible!!! Once they're saved,...Hi!!!!!!!!!!
I wrote again the articles about my BeeFree TorButton and FireFox on this wikipedia!!!!!!!
I did it in the past too!!!!!! i don't know why the pages then disappeared!! I don't know how that's possible!!! Once they're saved, they're supposed to stay saved!!!!!!!!
~bee!!!!!!!!!!
**Trac**:
**Username**: beehttps://gitlab.torproject.org/legacy/trac/-/issues/1708please create trac-test2020-06-13T16:45:15ZErinn Clarkplease create trac-testWe need a trac playground so I can test plugins for brokenness without breaking production trac.We need a trac playground so I can test plugins for brokenness without breaking production trac.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1711Clean up Trac components2020-06-13T16:45:15ZKarsten LoesingClean up Trac componentsWe should clean up the Trac components a bit. I just tried out renaming components and it seems to work fine as long as we update reports manually.
I already renamed:
- Tor - Metrics -> Metrics
- Tor - Torbutton -> Torbutton (and upda...We should clean up the Trac components a bit. I just tried out renaming components and it seems to work fine as long as we update reports manually.
I already renamed:
- Tor - Metrics -> Metrics
- Tor - Torbutton -> Torbutton (and updated report 14)
I suggest we rename the following components:
- Android (Orbot)-Backend / Core -> Orbot
- Polipo-Backend / Core -> Polipo
- Tor - BridgeDB -> BridgeDB
- Tor - Company -> Company
- Tor - Distribution -> Distribution
- Tor - Tor VM -> Tor VM
- Tor - Tor bundles/installation -> Tor Bundles/installation
- Tor - Torctl -> Torctl
- Tor - Torify -> Torify
- Tor - Website -> Website
This affects reports 8, 10, 11, 12, and 20, as far as I can see.
I'm happy to make the changes unless some objects.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/1712Archive Mixminion-* tasks2020-06-13T16:45:16ZKarsten LoesingArchive Mixminion-* tasksWe should archive the tasks belonging to the Mixminion-Server, -Client, and -Other components. I talked to Nick and he said he's fine taking them out if they're archived and available somewhere (with a not yet specified definition of som...We should archive the tasks belonging to the Mixminion-Server, -Client, and -Other components. I talked to Nick and he said he's fine taking them out if they're archived and available somewhere (with a not yet specified definition of somewhere). It looks like the three Mixminion-* components are the only components we're not likely to do any work on in the future.
Is there an easy way to export tasks belonging to these three components?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1713Make some other component than Android (Orbot)-Backend / Core the default2020-06-13T16:45:16ZKarsten LoesingMake some other component than Android (Orbot)-Backend / Core the defaultThe current default component for new tickets is "Android (Orbot)-Backend / Core". It happens quite often that people forget to change the component, so that new tickets are added to that component. Should we a) pick something else as de...The current default component for new tickets is "Android (Orbot)-Backend / Core". It happens quite often that people forget to change the component, so that new tickets are added to that component. Should we a) pick something else as default, like "Tor client", or b) create a new "Please select a component" or "Unspecified" component and make that the default, so that we can easily see when someone forgets to pick a component?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1714Stats/Code page is broken2020-06-13T16:45:16ZKarsten LoesingStats/Code page is brokenWhen I go to Stats and select "Code", I get the following error message:
Trac detected an internal error:
DataError: value too long for type character varying(20)When I go to Stats and select "Code", I get the following error message:
Trac detected an internal error:
DataError: value too long for type character varying(20)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1717teach account manager about cracklib2020-06-13T16:45:17Zweasel (Peter Palfrader)teach account manager about cracklibweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1736Trac should have a "needs code-review" status2020-06-13T16:45:17ZNick MathewsonTrac should have a "needs code-review" statusWe've discussed using trac to remember which pending Tor branches need code review. This is mostly necessary for Tor itself, where our current documented process (mention the branch in a git-branches file) is at odds with the most effec...We've discussed using trac to remember which pending Tor branches need code review. This is mostly necessary for Tor itself, where our current documented process (mention the branch in a git-branches file) is at odds with the most effective process (bug nickm on IRC until he reviews/merges your branch).
This is apparently possible with versions of Trac since 0.11 : see http://trac.edgewall.org/wiki/TracWorkflow for details how. Doing this is complicated enough that we should try it out on the testing trac installation before we do it in the main one.Sebastian HahnSebastian Hahnhttps://gitlab.torproject.org/legacy/trac/-/issues/1738Trac compnent for arm2020-06-13T16:45:18ZDamian JohnsonTrac compnent for armMind adding arm to the trac bug report components list or pointing how how I do it? If arm is becoming an official project I should stop doing bug reporting via email. Cheers! -DamianMind adding arm to the trac bug report components list or pointing how how I do it? If arm is becoming an official project I should stop doing bug reporting via email. Cheers! -DamianAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/1743Version numbers should be sorted2020-06-13T16:45:18ZJens KubiezielVersion numbers should be sortedThere are some Tor versions at the end of Versions:-field in trac. It would be better if all were sorted. Also the last entry is missing "Tor: " in front.There are some Tor versions at the end of Versions:-field in trac. It would be better if all were sorted. Also the last entry is missing "Tor: " in front.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1785add translation portal as a component to trac2020-06-13T16:45:18ZTracadd translation portal as a component to tracwould be useful for me & runa :)
**Trac**:
**Username**: carolynwould be useful for me & runa :)
**Trac**:
**Username**: carolynErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1788Logins are Case-Sensitive2020-06-13T16:45:19ZTracLogins are Case-SensitiveThey should not be
**Trac**:
**Username**: BarkerJrThey should not be
**Trac**:
**Username**: BarkerJrErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/1897Make report "My Tickets (all)" case-insensitive2020-06-13T16:45:19ZKarsten LoesingMake report "My Tickets (all)" case-insensitiveI noticed that there are tickets owned by karsten and tickets owned by Karsten. The latter don't show up in report 7 "My Tickets (all)". How about we make username comparison in that query case-insensitive? I created a new report 25 whic...I noticed that there are tickets owned by karsten and tickets owned by Karsten. The latter don't show up in report 7 "My Tickets (all)". How about we make username comparison in that query case-insensitive? I created a new report 25 which is a copy of 7 but which ignores case. Should 25 replace 7?Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/2032current version not selectable in trac2020-06-13T16:45:20ZTraccurrent version not selectable in tracnothing after 0.2.2.12-alpha is in the Version field
**Trac**:
**Username**: kebnothing after 0.2.2.12-alpha is in the Version field
**Trac**:
**Username**: kebErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/2098Tor Trac sets cookies over HTTPS that can be sent over cleartext HTTP2020-06-13T16:45:20ZRobert RansomTor Trac sets cookies over HTTPS that can be sent over cleartext HTTPBoth the `trac_auth` and `trac_form_token` cookies are described in Firefox's ‘Cookies’ dialog as “Send For: Any type of connection”. The Tor Project should not do this.Both the `trac_auth` and `trac_form_token` cookies are described in Firefox's ‘Cookies’ dialog as “Send For: Any type of connection”. The Tor Project should not do this.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/2259The "new ticket" page should contain good advice on how to write good tickets.2020-06-13T16:45:21ZNick MathewsonThe "new ticket" page should contain good advice on how to write good tickets.The text could be something like,
>Hi, and thank you for helping to make Tor better!
>
>Before you post your ticket, please check it against this checklist to make sure it includes all the info we need to figure out how to solve the pro...The text could be something like,
>Hi, and thank you for helping to make Tor better!
>
>Before you post your ticket, please check it against this checklist to make sure it includes all the info we need to figure out how to solve the problem.
>
>* If there was an error message, please make sure to copy it exactly.
>* If this is crash bug, or there is an assertion failure, or Tor just won't start, make sure to include a stack trace if possible
>* Are you logged in using an account with a working email? of course, we are fine with anonymous bug reports, but if we questions for you, it will help if the bug tracker has some way to contact you about them.
I don't think that's the sum of what we want to say here; it would be nice to be terse but friendly.
How to do this? A little googling turned up http://trac.edgewall.org/ticket/2021 which seems to talk about introducing the relevant feature, and and http://trac.edgewall.org/wiki/TracInterfaceCustomization , which seem to give instructions.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/2426Disable inline image support in Trac tickets and wiki pages2020-06-13T16:45:21ZRobert RansomDisable inline image support in Trac tickets and wiki pagesTicket #2425 (a spam ticket which should be deleted as soon as a Trac admin sees it) contains two HTML IMG tags linking to off-site images. This allows the sites hosting the images to determine who is viewing the page and how many times...Ticket #2425 (a spam ticket which should be deleted as soon as a Trac admin sees it) contains two HTML IMG tags linking to off-site images. This allows the sites hosting the images to determine who is viewing the page and how many times the page is viewed. We cannot allow this, in either bug tracker tickets or wiki pages.Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/2441We need the antispam plugin (or some kind of moderation plugin) for trac2020-06-13T16:45:22ZNick MathewsonWe need the antispam plugin (or some kind of moderation plugin) for tracLooks like the spammers have finally found and automated our upload-a-ticket interface. I've scrubbed and closed 3 in the last couple of hours. (See #2440 for an example.) We really need to look into possible upgrades here.
Options a...Looks like the spammers have finally found and automated our upload-a-ticket interface. I've scrubbed and closed 3 in the last couple of hours. (See #2440 for an example.) We really need to look into possible upgrades here.
Options are:
* Looking into the TicketModerator plugin
* Looking into the SpamFilter plugin (the latest versions of which require Trac 0.12)
* Looking into other related plugins
* Looking into some way to close user accounts in a way that blacklists their credentials immediately rather than just preventing them from logging in again if ever log out.Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/2546zomg, ioerror and the mikeperry cannot upload files to trac2020-06-13T16:45:23ZAndrew Lewmanzomg, ioerror and the mikeperry cannot upload files to tracoh noes!!!!1111 quick, increase file attachment sizes! darn the torpedos! batten down the hatches! let the uploads commence!oh noes!!!!1111 quick, increase file attachment sizes! darn the torpedos! batten down the hatches! let the uploads commence!Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/2560Trac notifies people of their own changes.2020-06-13T16:45:23ZTracTrac notifies people of their own changes.Trac will send people emails about their own changes to tickets they've subscribed to. Obviously, they already know about such changes, and thus needn't be notified of them.
**Trac**:
**Username**: katmagicTrac will send people emails about their own changes to tickets they've subscribed to. Obviously, they already know about such changes, and thus needn't be notified of them.
**Trac**:
**Username**: katmagicErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/2609Make trac send less mail2020-06-13T16:45:24ZMike PerryMake trac send less mailTrac is very noisy. Right now, it is sending everybody mail every time every field changes. This is insane. We should tell it that some field changes should only send mail to the ticket owner, if that.
It looks like the trac people trie...Trac is very noisy. Right now, it is sending everybody mail every time every field changes. This is insane. We should tell it that some field changes should only send mail to the ticket owner, if that.
It looks like the trac people tried to document this, but hit a fail wall: http://trac.edgewall.org/wiki/TracNotification#Customizingthee-mailcontent
I have no idea what the hell is going on in that file format. I don't even know where to start. Are those comments in there? What is up with that indentation? and the field names??
I think someone actually has to send a mail to the trac mailinglists to figure this out.. That, or perform a ton of experiments tweaking the format and seeing what changes, in an attempt to reverse engineer it... :/Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/2996‘Tor Browser’ Trac ‘component’ confuses users2020-06-13T16:45:24ZRobert Ransom‘Tor Browser’ Trac ‘component’ confuses usersSee #2982 for an example of a user who thought ‘Tor Browser’ was the right component for a Tor Browser Bundle bug.See #2982 for an example of a user who thought ‘Tor Browser’ was the right component for a Tor Browser Bundle bug.Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/3408Broken link on wiki main page2020-06-13T16:45:25ZRobert RansomBroken link on wiki main pageThe following link on the main page ([WikiStart]) is now broken:
* [Active projects in progress](uploads/projects) Feel free to take a task or contact the owner if you want to help out.The following link on the main page ([WikiStart]) is now broken:
* [Active projects in progress](uploads/projects) Feel free to take a task or contact the owner if you want to help out.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/3470Reduced Exit Policy IM Expansion2020-06-13T16:45:25ZDamian JohnsonReduced Exit Policy IM ExpansionThe reduced exit policy [1] is missing ports for some instant messaging protocols, for instance Gadu-Gadu which is popular in Poland. The following are the entries we'd need to cover all the TCP based IM protocols provided by Pidgin...
...The reduced exit policy [1] is missing ports for some instant messaging protocols, for instance Gadu-Gadu which is popular in Poland. The following are the entries we'd need to cover all the TCP based IM protocols provided by Pidgin...
ExitPolicy accept *:531 # IRC/AIM
ExitPolicy accept *:1533 # Sametime
ExitPolicy accept *:1677 # GroupWise
ExitPolicy accept *:2102-2104 # Zephyr
ExitPolicy accept *:8074 # Gadu-Gadu
Also one of the IRC entries...
ExitPolicy accept *:6666-6667 # IRC
should be the 6660-6669 range according to the wiki on port assignments [2]. Ports 6668 and 6669 in particular are within the officially assigned range so if we can't include them we should cite why on the reduced policy wiki.
Cheers! -Damian
[1] https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy
[2] https://secure.wikimedia.org/wikipedia/en/wiki/List_of_TCP_and_UDP_port_numbersMike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3519Determine why project tickets don't display their child tickets2020-06-13T16:45:26ZNick MathewsonDetermine why project tickets don't display their child ticketsI tried changing the type of #1865 to "project". When I did, it no longer had a list of its child tickets at the bottom of its description. That's undesirable: Projects are _especially_ likely to have child tickets.I tried changing the type of #1865 to "project". When I did, it no longer had a list of its child tickets at the bottom of its description. That's undesirable: Projects are _especially_ likely to have child tickets.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4054Absence of a 'MAT' component in trac2020-06-13T16:45:27ZJulien VoisinAbsence of a 'MAT' component in tracTrac bugs don't have a 'MAT' component, it would be nice to have one.Trac bugs don't have a 'MAT' component, it would be nice to have one.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4190No versions options for HTTPS Everywhere when creating a new ticket2020-06-13T16:45:27ZcypherpunksNo versions options for HTTPS Everywhere when creating a new ticketThe version dropdown is populated but none of the choices are 1.0.3The version dropdown is populated but none of the choices are 1.0.3Peter EckersleyPeter Eckersleyhttps://gitlab.torproject.org/legacy/trac/-/issues/4193make trac timeline be the frontpage for bugs.torproject.org2020-06-13T16:45:28ZRoger Dingledinemake trac timeline be the frontpage for bugs.torproject.orgRight now we send people to bugs.torproject.org if they have a bug to report.
But bugs.torproject.org sends them to the frontpage of our wiki. Wiki and bug tracker are not the same thing.
How about we point them to https://trac.torproj...Right now we send people to bugs.torproject.org if they have a bug to report.
But bugs.torproject.org sends them to the frontpage of our wiki. Wiki and bug tracker are not the same thing.
How about we point them to https://trac.torproject.org/projects/tor/timeline ? That has the advantage that if a bunch of users are showing up to report the same bug, they are shown a list of recently opened bugs. See for example bug #4118 which had over a dozen duplicates filed.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/4382Test deleting ticket changes2020-06-13T16:45:29ZKarsten LoesingTest deleting ticket changesThis ticket is a test of our "Delete Ticket Changes" feature for deleted versions. Here's the test:
- Create this ticket, assign it to version "Mixminion: 0.0.4rc1."
- Delete that version.
- Change the version field in this ticket...This ticket is a test of our "Delete Ticket Changes" feature for deleted versions. Here's the test:
- Create this ticket, assign it to version "Mixminion: 0.0.4rc1."
- Delete that version.
- Change the version field in this ticket to something else, e.g., "Mixminion: 0.0.4rc2." This change cannot be undone by changing the version field back, because the deleted version is not available anymore.
- Delete the last ticket change using our "Delete Ticket Change" feature. See whether the version is back at "Mixminion: 0.0.4rc1."Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4384Trac is fascist about child ticket types2020-06-13T16:45:30ZRobert RansomTrac is fascist about child ticket typesA user who commented on #3869 changed the ticket's ‘Type’ from ‘defect’ to ‘task’, and said Trac forced him to. I tried to change the ‘Type’ back, and Trac refused:
> **Warning:** The parent ticket (#3561) has type enhancement which do...A user who commented on #3869 changed the ticket's ‘Type’ from ‘defect’ to ‘task’, and said Trac forced him to. I tried to change the ‘Type’ back, and Trac refused:
> **Warning:** The parent ticket (#3561) has type enhancement which does not allow child type 'defect'. Must be one of : bug-fix,task.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4409trac migration lost wysiwyg editing2020-06-13T16:45:31ZAndrew Lewmantrac migration lost wysiwyg editingWe lost the wysiwyg functionality for trac descriptions/comments when we migrated trac. Please re-install.We lost the wysiwyg functionality for trac descriptions/comments when we migrated trac. Please re-install.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4422Don't report trac user registrations in tor-bugs.2020-06-13T16:45:31ZGeorge KadianakisDon't report trac user registrations in tor-bugs.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4435Trac no longer allows child tickets of ‘defect’s.2020-06-13T16:45:32ZRobert RansomTrac no longer allows child tickets of ‘defect’s.See [ticket:3832#comment:5].See [ticket:3832#comment:5].Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4553Let's have a new ticket status: needs_revision?2020-06-13T16:45:32ZNick MathewsonLet's have a new ticket status: needs_revision?Right now, needs_review means one of two things: either a ticket that actually needs code review of some kind, or a ticket that has _received_ code review and is waiting for somebody to revise the code.
This makes it harder for me to fi...Right now, needs_review means one of two things: either a ticket that actually needs code review of some kind, or a ticket that has _received_ code review and is waiting for somebody to revise the code.
This makes it harder for me to figure out which tickets I actually need to review, which ones I need to bug somebody to finish up, and so on. It also sometimes makes people think that their code is waiting on me for review, when it is actually waiting on them to fix up.
(Why not just re-assign the ticket back to them, and remove it from needs_review? Because I find that it's really important to keep tickets with fixable code separate, so I can remember to bug the people to finish up the code, and so I can jump in and do the final cleanups if the aren't to big and the person who did the first version can't finish the patch.)
This should probably get a little discussion before anybody goes and implements it; I don't know whether anybody but me thinks it's a great idea. But I do think that it's a great idea!Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4632Trac does not allow a ticket in ‘needs_information’ to be set directly to ‘ne...2020-06-13T16:45:33ZRobert RansomTrac does not allow a ticket in ‘needs_information’ to be set directly to ‘needs_review’Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4871I can edit ticket descriptions2020-06-13T16:45:33ZRobert RansomI can edit ticket descriptionsI now have the ability to edit ticket descriptions. Is there a reason for this change?I now have the ability to edit ticket descriptions. Is there a reason for this change?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4876Stem trac component2020-06-13T16:45:34ZDamian JohnsonStem trac componentHi, I'd appreciate a "Stem" trac component for bug reports.
Thanks! -DamianHi, I'd appreciate a "Stem" trac component for bug reports.
Thanks! -DamianErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4945Trac won't allow ticket to change from "needs_information" to "needs_review"2020-06-13T16:45:35ZTracTrac won't allow ticket to change from "needs_information" to "needs_review"Trac does not appear to give the option for a ticket to change to needs_review status once it has been set to needs_information status. This behavior can be seen in bug ticket [https://trac.torproject.org/projects/tor/ticket/3842]
**Tra...Trac does not appear to give the option for a ticket to change to needs_review status once it has been set to needs_information status. This behavior can be seen in bug ticket [https://trac.torproject.org/projects/tor/ticket/3842]
**Trac**:
**Username**: blackpawErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5030Stop auto-assigning Trac tickets based on the component2020-06-13T16:45:36ZKarsten LoesingStop auto-assigning Trac tickets based on the componentTrac assigns new tickets to the component owner if no ticket owner is specified. But in my understanding the ticket owner is the person who's supposed to work on a ticket. This requires a commitment from the person. Auto-assigning a t...Trac assigns new tickets to the component owner if no ticket owner is specified. But in my understanding the ticket owner is the person who's supposed to work on a ticket. This requires a commitment from the person. Auto-assigning a ticket is the wrong concept here.
Should we remove component owners to stop auto-assigning tickets based on the component?
The question is: how we can ensure that the right persons learn about new tickets. Can we assume that current "component owners" know how to filter their tor-bugs email?
(Cc'ing all component owners.)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5240spoiler plugin2020-06-13T16:45:36Zproperspoiler pluginCan you please install the spoiler plugin?
A spoiler enhances the wiki. You can hide text with a spoiler which will be revealed after pressing a button.
There is a [video demonstration](https://www.youtube.com/watch?v=TyuelS_e0Js) avai...Can you please install the spoiler plugin?
A spoiler enhances the wiki. You can hide text with a spoiler which will be revealed after pressing a button.
There is a [video demonstration](https://www.youtube.com/watch?v=TyuelS_e0Js) available (html5, only 9 seconds). It does not need javascript. [Here](http://trac-hacks.org/wiki/SpoilerMacro) are instructions how to install it and the source code. If there are technical questions, the author of the plugin is very friendly and [answers fast](https://groups.google.com/group/trac-users/browse_thread/thread/f55ceee3a26abaa9).
This plugin would be very useful for [my project](https://trac.torproject.org/projects/tor/wiki/doc/TorBOX).Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5395Change owner of HTTPS Everywhere Chrome to pde2020-06-13T16:45:37ZaaronswChange owner of HTTPS Everywhere Chrome to pdeI don't maintain this anymore, it's been picked up officially.I don't maintain this anymore, it's been picked up officially.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5513Trac wiki disclaimer2020-06-13T16:45:37ZDamian JohnsonTrac wiki disclaimerTrac's domain and tor logo lends it an air of being official but, as we all know, the vast majority of its content is either provided from people outside the core community and/or vastly out of date.
We could use a disclaimer on trac's ...Trac's domain and tor logo lends it an air of being official but, as we all know, the vast majority of its content is either provided from people outside the core community and/or vastly out of date.
We could use a disclaimer on trac's wiki pages, something to the effect of "This is a community supported wiki. Content may not be accurate nor reviewed by Tor's developers."
I have somewhat mixed feelings about where to put this. It would be eye jarring in the header, but barely noticeable in the footer. Thoughts?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5777Create ‘component’ for Excito B3 Tor configurator bugs or close tickets2020-06-13T16:45:38ZRobert RansomCreate ‘component’ for Excito B3 Tor configurator bugs or close ticketsSomeone created #5770, #5771, #5772, and #5774 for bugs in the Excito B3 Tor configuration interface, and #5775 for a bug in the Excito B3 configuration interface in general. If these bugs belong in Tor's bug tracker, someone should cre...Someone created #5770, #5771, #5772, and #5774 for bugs in the Excito B3 Tor configuration interface, and #5775 for a bug in the Excito B3 configuration interface in general. If these bugs belong in Tor's bug tracker, someone should create a Trac ‘component’ for them; if they don't belong here, someone should close the tickets and send the reports upstream.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5800Please deprecate the "HTTPS Everywhere: Chrome" component2020-06-13T16:45:38ZPeter EckersleyPlease deprecate the "HTTPS Everywhere: Chrome" componentIt seems to be saner for us just to use the EFF-HTTPS Everywhere component for now.It seems to be saner for us just to use the EFF-HTTPS Everywhere component for now.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5924Ticket creators don't get mail about ticket updates2020-06-13T16:45:39ZRoger DingledineTicket creators don't get mail about ticket updatesIf you make a ticket, and then somebody else comments on it, you don't get email about the comment.
Once you have commented on your ticket, you start getting emails about updates.
Workaround is to set yourself as cc to all the tickets ...If you make a ticket, and then somebody else comments on it, you don't get email about the comment.
Once you have commented on your ticket, you start getting emails about updates.
Workaround is to set yourself as cc to all the tickets you make. That works for me (now that I've realized it), but most new ticket creators won't realize it.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6332add blockfinder component2020-06-13T16:45:46ZJacob Appelbaumadd blockfinder componentWe need a blockfinder componentWe need a blockfinder componentAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/6365Use keywords like SponsorG20120930 for sponsor deliverables instead of milest...2020-06-13T16:45:47ZKarsten LoesingUse keywords like SponsorG20120930 for sponsor deliverables instead of milestonesWe're currently using Trac's milestone field for two things: version milestone and sponsor milestone. It would be good to assign a ticket to both a version like Tor 0.2.4.x-final and to a sponsor milestone like Sponsor G, September 30, ...We're currently using Trac's milestone field for two things: version milestone and sponsor milestone. It would be good to assign a ticket to both a version like Tor 0.2.4.x-final and to a sponsor milestone like Sponsor G, September 30, 2012. Mike and Nick suggested to use Trac keywords for this purpose.
Two questions:
- Is SponsorG20120930 a good format for such keywords?
- Is there an easy way to modify existing tickets in bulk? I don't mind so much doing it manually, but it's going to generate a lot of emails.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/6403Make a Stegotorus trac component?2020-06-13T16:45:52ZRoger DingledineMake a Stegotorus trac component?Zack (and others),
Is now a good time to make a Stegotorus component in Tor's trac? Or do you still prefer keeping your tickets elsewhere?Zack (and others),
Is now a good time to make a Stegotorus component in Tor's trac? Or do you still prefer keeping your tickets elsewhere?Roger DingledineRoger Dingledinehttps://gitlab.torproject.org/legacy/trac/-/issues/6405Merge torclient/torrelay/torbridge/etc into one Tor component2020-06-13T16:45:53ZRoger DingledineMerge torclient/torrelay/torbridge/etc into one Tor componentNick has been asking for a long time now for us to make a single Tor component, and use keywords to mark them as TorClient, TorBridge, etc. Using different components to describe what sort of Tor category a ticket is for drives him nuts....Nick has been asking for a long time now for us to make a single Tor component, and use keywords to mark them as TorClient, TorBridge, etc. Using different components to describe what sort of Tor category a ticket is for drives him nuts.
Roger and Robert were pushing back because trac's search feature is abysmal, and our way of finding a ticket was to guess its Tor component and then look at the list of tickets under that component. But we should be able to do the same thing just narrowing by keyword.
Ultimately, since Nick is the primary user of this component, I think it makes the most sense to let him pick the conventions.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/6477"Newest 50 tickets" shows 500 hits2020-06-13T16:45:54Zbastik"Newest 50 tickets" shows 500 hitsI like this category and found it always strange that "50 tickets" finds 500 tickets.
I suggest renaming it to "500 tickets". It just looks better when it matches each other. Please see the attached pictures.I like this category and found it always strange that "50 tickets" finds 500 tickets.
I suggest renaming it to "500 tickets". It just looks better when it matches each other. Please see the attached pictures.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6497Allow track users to mange their self-originated ticket content2020-06-13T16:45:55ZgrarpampAllow track users to mange their self-originated ticket contentTrac users should be able to edit/delete their own ticket content that they added.
Such as the Subject, 'Description' and 'Comment's they created in any given ticket.
It can yield more concise tickets by reducing spoken corrections.
And ...Trac users should be able to edit/delete their own ticket content that they added.
Such as the Subject, 'Description' and 'Comment's they created in any given ticket.
It can yield more concise tickets by reducing spoken corrections.
And quicker/safer handling of errantly included data.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6574Cant create new page in wiki2020-06-13T16:45:57ZTracCant create new page in wikiI would like to create a page with information on how to prevent bittorrent through Tor, but I have no way of creating a new page.
Its the result of research after an altercation with Paramount Pictures :)
**Trac**:
**Username**: ker...I would like to create a page with information on how to prevent bittorrent through Tor, but I have no way of creating a new page.
Its the result of research after an altercation with Paramount Pictures :)
**Trac**:
**Username**: kerruptErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6723Vidalia's milestones in Trac are outdated2020-06-13T16:46:02ZKarsten LoesingVidalia's milestones in Trac are outdatedThere's an open milestone "Vidalia: 0.2.15" in Trac, even though I'm using 0.2.20. Should I close that milestone and create a new milestone "Vidalia: 0.2.x"?There's an open milestone "Vidalia: 0.2.15" in Trac, even though I'm using 0.2.20. Should I close that milestone and create a new milestone "Vidalia: 0.2.x"?Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/6854logout button is not working proberly?2020-06-13T16:46:05ZTraclogout button is not working proberly?Hi,
just observed the following (reproduceable) behavior:
1. login to trac
2. click logout
3. click login => you are logged in without providing any user credentials (with the user used in step 1)
expected behavior:
step 3 should req...Hi,
just observed the following (reproduceable) behavior:
1. login to trac
2. click logout
3. click login => you are logged in without providing any user credentials (with the user used in step 1)
expected behavior:
step 3 should require user and password
**Trac**:
**Username**: cypherpunkxErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/7034How to recover forgotten Trac password ?2020-06-13T16:46:06ZTracHow to recover forgotten Trac password ?I finally managed to remember my Trac password, but was not able to find a way to recover a forgotten password ? What can be done about this?
**Trac**:
**Username**: joergentI finally managed to remember my Trac password, but was not able to find a way to recover a forgotten password ? What can be done about this?
**Trac**:
**Username**: joergentErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/7088trac and blog should support openid and browserid2020-06-13T16:46:07ZAndrew Lewmantrac and blog should support openid and browseridA number of users are willing to not be wholly anonymous. We shouldn't force everyone into our own paranoia world and if someone has an openid and/or browserid account, they can use it on trac and the blog (and forthcoming forums).
Ther...A number of users are willing to not be wholly anonymous. We shouldn't force everyone into our own paranoia world and if someone has an openid and/or browserid account, they can use it on trac and the blog (and forthcoming forums).
There is an openid auth plugin for trac at https://github.com/dairiki/authopenid-plugin
There is not yet a browserid auth plugin for trac, but I bet we can find someone to write one for us.
As for the blog, we'll need to upgrade to current drupal, or find new blog software, to get openid and browserid support.https://gitlab.torproject.org/legacy/trac/-/issues/7186Non-admins can't change ticket status2020-06-13T16:46:08ZDamian JohnsonNon-admins can't change ticket status08:38 < neena> btw, I'm unable to change bug attributes on trac... http://codesurfers.net/~neena/trac.png
08:39 < atagar> I heard this from Sukhbir, evidently Mike changed something in response to some spam. We need to change it back.
08...08:38 < neena> btw, I'm unable to change bug attributes on trac... http://codesurfers.net/~neena/trac.png
08:39 < atagar> I heard this from Sukhbir, evidently Mike changed something in response to some spam. We need to change it back.
08:39 < atagar> One sec, I'll open a ticket.
I've heard from both Ravi and Sukhbir that they can't change ticket statuses. We should revert whatever changed recently (... or make everyone who helps admins). This is getting in the way of them helping.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/7209Unable to login with cypherpunk account2020-06-13T16:46:08ZMatthew FinkelUnable to login with cypherpunk accountA user mentioned on #tor that they were unable to log in with the cypherpunk account. I verified that I was also not able to.A user mentioned on #tor that they were unable to log in with the cypherpunk account. I verified that I was also not able to.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/7301Merge EFF-HTTPS Everywhere and HTTPS Everywhere: Chrome Trac components2020-06-13T16:46:09ZKarsten LoesingMerge EFF-HTTPS Everywhere and HTTPS Everywhere: Chrome Trac componentsCan we merge these two components? There are currently two tickets in HTTPS Everywhere: Chrome, and it seems they could also be in the EFF-HTTPS Everywhere component.Can we merge these two components? There are currently two tickets in HTTPS Everywhere: Chrome, and it seems they could also be in the EFF-HTTPS Everywhere component.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/7307diff renderer in ticket view doesn't work right2020-06-13T16:46:09ZTracdiff renderer in ticket view doesn't work rightI constructed a diff processor block in ticket #7306 using instructions at http://trac.edgewall.org/wiki/WikiProcessors. Your WikiProcessors looks different, but it also mentions that #!diff is available. It does get parsed as a diff, bu...I constructed a diff processor block in ticket #7306 using instructions at http://trac.edgewall.org/wiki/WikiProcessors. Your WikiProcessors looks different, but it also mentions that #!diff is available. It does get parsed as a diff, but doesn't render the way it should. Don't know what the cause is, maybe missing one of the modules that does the coloring? The same block copy-pasted into my personal trac repo renders fine.
**Trac**:
**Username**: ultramageErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/7841Please Remove TorCtl Component2020-06-13T16:46:16ZDamian JohnsonPlease Remove TorCtl ComponentTorCtl is becoming a part of TorFlow, as per...
https://blog.torproject.org/blog/torctl-deprecation-and-stem-plans
I've resolved or reassigned all present TorCtl tickets. Please remove its trac component.
Thanks!TorCtl is becoming a part of TorFlow, as per...
https://blog.torproject.org/blog/torctl-deprecation-and-stem-plans
I've resolved or reassigned all present TorCtl tickets. Please remove its trac component.
Thanks!Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/8497TorBirdy tickets ownership2020-06-13T16:46:24ZSukhbir SinghTorBirdy tickets ownershipIt would be good if I can be set as the co-owner of the TorBirdy component (and henceforth the tickets associated with it) as I don't get notifications for new tickets. ioerror is the current component owner.It would be good if I can be set as the co-owner of the TorBirdy component (and henceforth the tickets associated with it) as I don't get notifications for new tickets. ioerror is the current component owner.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/8581trac's useradmin plugin is horribe2020-06-13T16:46:28ZSebastian Hahntrac's useradmin plugin is horribeAfter using the user admin thing in trac, trac became unresponsive. I checked the load, it sat at 17 with a machine swapping heavily. Perhaps we could find a way to debug that/give the VM appropriate resources/optimize the webserver to u...After using the user admin thing in trac, trac became unresponsive. I checked the load, it sat at 17 with a machine swapping heavily. Perhaps we could find a way to debug that/give the VM appropriate resources/optimize the webserver to use less ram or something?Sebastian HahnSebastian Hahnhttps://gitlab.torproject.org/legacy/trac/-/issues/8586Add ability to watch wiki pages2020-06-13T16:46:29ZLunarAdd ability to watch wiki pagesIt would be useful if support assistants could be notified when support templates are updated. It looks like core Trac does not offer to _watch_ or _subscribe_ to wiki pages.
It looks like the [AnnouncerPlugin](http://trac-hacks.org/wik...It would be useful if support assistants could be notified when support templates are updated. It looks like core Trac does not offer to _watch_ or _subscribe_ to wiki pages.
It looks like the [AnnouncerPlugin](http://trac-hacks.org/wiki/AnnouncerPlugin) offers this feature, and also other improvements to ticket notifications.
Please consider adding that plugin to trac.tpo.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9016[meta] Can't reset password on trac2020-06-13T16:46:38ZTrac[meta] Can't reset password on tracI have an old account here and I can't find a way to reset the password. I couldn't create a new account because it said the e-mail address was already in use, so I had to use a second e-mail address.
**Trac**:
**Username**: usualityI have an old account here and I can't find a way to reset the password. I couldn't create a new account because it said the e-mail address was already in use, so I had to use a second e-mail address.
**Trac**:
**Username**: usualityErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9079Create Trac component for whatever #9078 is about?2020-06-13T16:46:40ZRobert RansomCreate Trac component for whatever #9078 is about?#9078 is a bug in something related to Gitian (perhaps git.tpo/user/mikeperry/gitian-builder.git, but I can't tell because neither the ticket description nor the Trac component nor the patch itself say what it's about). There will be ot...#9078 is a bug in something related to Gitian (perhaps git.tpo/user/mikeperry/gitian-builder.git, but I can't tell because neither the ticket description nor the Trac component nor the patch itself say what it's about). There will be other tickets related to the same entity that #9078 is about. Perhaps there should be a Trac component for whatever that is.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9360increase font size in trac2020-06-13T16:46:46ZJens Kubiezielincrease font size in tracWhenever I visit trac I find the fonts hard to read. The file https://trac.torproject.org/tor.css has the following lines inside:
```
body, th, td {
font: normal 13px Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;
}
```
So t...Whenever I visit trac I find the fonts hard to read. The file https://trac.torproject.org/tor.css has the following lines inside:
```
body, th, td {
font: normal 13px Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;
}
```
So the font-size is set to 13px. I would propose to change it to `1.0em`. This sets the font-size to the value the users has set for normal texts. So it should reflect the users choice.
Maybe can also change the font sizes of the headings. The current setting in tor.css is:
```
h1 { font-size: 19px; margin: .15em 1em 0.5em 0 }
h2 { font-size: 16px }
h3 { font-size: 14px }
```
In relative terms the settings should be like:
```
h1 { font-size: 1.5em; margin: .15em 1em 0.5em 0 }
h2 { font-size: 1.2em }
h3 { font-size: 1.1em }
```Griffin BoyceGriffin Boycehttps://gitlab.torproject.org/legacy/trac/-/issues/9513Populate "Version" with entries that match the selected component.2020-06-13T16:46:47ZbastikPopulate "Version" with entries that match the selected component.While looking for HTTPS-E 3.3.2, which does not exist, I noticed (well I noticed before) that there are entries that make no sense for the selected component.
For example, after selecting "Trac" as component I can pick HTTPS-E as versio...While looking for HTTPS-E 3.3.2, which does not exist, I noticed (well I noticed before) that there are entries that make no sense for the selected component.
For example, after selecting "Trac" as component I can pick HTTPS-E as version. That can be confusing. It is also difficult to find what you are looking for.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9514Order component and version entrires alphabetically2020-06-13T16:46:47ZbastikOrder component and version entrires alphabeticallyFor some part the component entries are sorted alphabetically, but not completely.
Version is totally messy.For some part the component entries are sorted alphabetically, but not completely.
Version is totally messy.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9542Cannot login as cypherpunks on HS version of trac.torproject.org2020-06-13T16:46:51ZcypherpunksCannot login as cypherpunks on HS version of trac.torproject.orgEvery time I try to log in to the hidden service version of this site:
http://vwp5zrdfwmw4avcq.onion/projects/tor
it accepts the usual account name and password,
but it does __not__ show status as `logged in as cypherpunks`.
What give...Every time I try to log in to the hidden service version of this site:
http://vwp5zrdfwmw4avcq.onion/projects/tor
it accepts the usual account name and password,
but it does __not__ show status as `logged in as cypherpunks`.
What gives?
`nonick`Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9586Trac lacks component for TorBrowserBundle TBB2020-06-13T16:46:56ZTracTrac lacks component for TorBrowserBundle TBBTrac lacks component for TorBowserBundle. There are various outdated components but for TBB (one of the most important pieces of tor) there is none.
**Trac**:
**Username**: torlandTrac lacks component for TorBowserBundle. There are various outdated components but for TBB (one of the most important pieces of tor) there is none.
**Trac**:
**Username**: torlandErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9604Trac switches back to default local after logging out2020-06-13T16:46:57ZbastikTrac switches back to default local after logging outNow Trac gets localized, what might be useful or not (well the content is still English).
I logged in to change the language setting to English and the interface changed. Right after logging out the interface changed to my default langu...Now Trac gets localized, what might be useful or not (well the content is still English).
I logged in to change the language setting to English and the interface changed. Right after logging out the interface changed to my default language again.
To me, personally, a localized Trac does not make sense. I don't even know where to click to get me where I want.
Can we (read I) have some way to have it like it was before?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9605Choose alignment of tickets2020-06-13T16:46:58ZbastikChoose alignment of ticketsThe alignment of tickets now it is centered.
Would it be possible to have a setting for this?
(I'd opt for left alignment.)The alignment of tickets now it is centered.
Would it be possible to have a setting for this?
(I'd opt for left alignment.)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9620No "download link" for attachments2020-06-13T16:46:58ZNick MathewsonNo "download link" for attachmentsGo to a ticket with an attachment (Try #1922). There used to be a link to click to download the attachment, I think. Now you can only see it in the viewer, without an obvious way to get the original file. Any tips?Go to a ticket with an attachment (Try #1922). There used to be a link to click to download the attachment, I think. Now you can only see it in the viewer, without an obvious way to get the original file. Any tips?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9706Missing "To" header triggers Spamassassin2020-06-13T16:46:59ZSteven MurdochMissing "To" header triggers SpamassassinWith the new Trac, mails sent do not have a "To" header. This triggers the MISSING_HEADERS and REPLYTO_WITHOUT_TO_CC Spamassassin rules and got the messages classified as spam. Previously mails had the header "To: undisclosed-recipients:;".With the new Trac, mails sent do not have a "To" header. This triggers the MISSING_HEADERS and REPLYTO_WITHOUT_TO_CC Spamassassin rules and got the messages classified as spam. Previously mails had the header "To: undisclosed-recipients:;".Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9749Include Link to Gitweb in MainNav again2020-06-13T16:47:02ZbastikInclude Link to Gitweb in MainNav againBefore the update/upgrade to the new Trac version there was a link in the MainNav linking to gitweb.torproject.org
Apparently there's a single line of code
```
<li><a href="gitweb.torproject.org">Git</a></li>
```
that has to be added t...Before the update/upgrade to the new Trac version there was a link in the MainNav linking to gitweb.torproject.org
Apparently there's a single line of code
```
<li><a href="gitweb.torproject.org">Git</a></li>
```
that has to be added to be like this:
```
<ul> <li class="first"><a href="/projects/tor/report">View Tickets</a></li><li><a href="/projects/tor/browser">Browse Source</a></li><li><a href="gitweb.torproject.org">Git</a></li><a href="/projects/tor/roadmap">Roadmap</a></li><li><a href="/projects/tor/timeline">Timeline</a></li><li class="active"><a href="/projects/tor/wiki">Wiki</a></li><li><a href="/projects/tor/search">Search</a></li><li class="last"><a href="/projects/tor/tags">Tags</a></li> </ul>
```
To show you what it looks like I'll attack a partial screen shot. You can place the link somewhere else in the MainNav bar if you like, of course.
(I'm unable to apply these changes locally as it seems, if there's a way, maybe it will work out for me, though it would be nice to have the link back for anyone)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10010Make infinity0 a ‘developer’ in Trac2020-06-13T16:47:11ZRobert RansomMake infinity0 a ‘developer’ in TracSee [ticket:10008#comment:2].See [ticket:10008#comment:2].Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10018Create a Trac component for DocTor2020-06-13T16:47:11ZKarsten LoesingCreate a Trac component for DocTorDamian, should we create a Trac component for your consensus-health checker DocTor? I'd like to move #8164, #8797, and #9103 to it. Any preference how to spell the component (like, is "DocTor" okay)? Want to become the component owner?Damian, should we create a Trac component for your consensus-health checker DocTor? I'd like to move #8164, #8797, and #9103 to it. Any preference how to spell the component (like, is "DocTor" okay)? Want to become the component owner?Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/10075Make an outreach component for new trac tickets2020-06-13T16:47:13ZMatt PaganMake an outreach component for new trac ticketsThis will become especially useful as tackle more of the SponsorOtter deliverables.This will become especially useful as tackle more of the SponsorOtter deliverables.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10132Trac Timeline broken2020-06-13T16:47:15ZbastikTrac Timeline brokenhttps://trac.torproject.org/projects/tor/timeline
Shows the following Trac Error:
> Event provider ChangesetModule failed for filters "Changesets in all repositories", " - arm", " - torbutton", " - stem", " - pluggable-transports/o...https://trac.torproject.org/projects/tor/timeline
Shows the following Trac Error:
> Event provider ChangesetModule failed for filters "Changesets in all repositories", " - arm", " - torbutton", " - stem", " - pluggable-transports/obfsproxy", " - tor", " - torbrowser", " - builders/tor-browser-bundle": ValueError: need more than 0 values to unpack
https://trac.torproject.org/projects/tor/timeline?wiki=on&ticket=on&milestone=on works (changesets are not enabled here)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10253Date cut-off in Timeline "input#fromdate"2020-06-13T16:47:19ZbastikDate cut-off in Timeline "input#fromdate"The default time setting displays the current date as "Nov 29, 2013", where the "3" is cut off.
The trick seems to be to increase the width for the input fields via css.
>#prefs input, #prefs select {
> font-size: 9px;vertical-align: ...The default time setting displays the current date as "Nov 29, 2013", where the "3" is cut off.
The trick seems to be to increase the width for the input fields via css.
>#prefs input, #prefs select {
> font-size: 9px;vertical-align: middle;**width: 65px**;
The bold indicates what I added to the trac.css, 60px worked fine for me, but I thought it to be safer to use some higher value. Note that this increases all input fields of the right selection menu, but not the search bar. This change is untested, so it could have very well impacts on other input fields, also it shifts the descriptions of the check-boxes farther away from them.
Alternatively the default way of displaying all dates on trac is to use the ISO thingy, to make dates appear like 2013-11-29. (Logged in users can override it)https://gitlab.torproject.org/legacy/trac/-/issues/10294Give Yan Zhu trac admin access2020-06-13T16:47:21ZPeter EckersleyGive Yan Zhu trac admin accessYan Zhu (trac.tpo username zyan) should have trac admin access so that she can create HTTPS Everywhere milestones and versions.Yan Zhu (trac.tpo username zyan) should have trac admin access so that she can create HTTPS Everywhere milestones and versions.https://gitlab.torproject.org/legacy/trac/-/issues/10321Add new Trac component for ExoneraTor2020-06-13T16:47:23ZKarsten LoesingAdd new Trac component for ExoneraTorSee summary. I'm going to do this myself, this ticket is just here to document this.See summary. I'm going to do this myself, this ticket is just here to document this.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/10359Create a new Trac component for Globe and make rndm the component owner2020-06-13T16:47:29ZKarsten LoesingCreate a new Trac component for Globe and make rndm the component ownerKarsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/10373Remove pyonionoo component and close all its tickets as wontfix2020-06-13T16:47:30ZKarsten LoesingRemove pyonionoo component and close all its tickets as wontfixThere are seven open tickets in the pyonionoo component, all of which haven't been touched in the past 14 months:
https://trac.torproject.org/projects/tor/query?status=!closed&component=pyonionoo
Is it safe to assume that the Onionoo r...There are seven open tickets in the pyonionoo component, all of which haven't been touched in the past 14 months:
https://trac.torproject.org/projects/tor/query?status=!closed&component=pyonionoo
Is it safe to assume that the Onionoo rewrite in Python won't happen, and can we remove the pyonionoo component and close all its tickets as wontfix?
Happy to do that, but I'd like to hear gsathya's opinion on it first.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/10375Remove blockfinder Trac component2020-06-13T16:47:30ZKarsten LoesingRemove blockfinder Trac componentBlockfinder is hosted on GitHub and has actively discussed issues there. No need to have a component for it in our Trac. There are no tickets in the blockfinder component (anymore). I'm going to remove the component.Blockfinder is hosted on GitHub and has actively discussed issues there. No need to have a component for it in our Trac. There are no tickets in the blockfinder component (anymore). I'm going to remove the component.https://gitlab.torproject.org/legacy/trac/-/issues/10376Bugs in Trac don't get a default owner anymore2020-06-13T16:47:30ZGeorg KoppenBugs in Trac don't get a default owner anymoreBugs in Trac used to have a default owner. When creating bugs they don't get owned by anyone by default anymore, now.Bugs in Trac used to have a default owner. When creating bugs they don't get owned by anyone by default anymore, now.https://gitlab.torproject.org/legacy/trac/-/issues/10377testing component owner to see if it's fixed2020-06-13T16:47:31ZErinn Clarktesting component owner to see if it's fixedfor #10376for #10376Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10404Trac permission for CCing users2020-06-13T16:47:31ZSukhbir SinghTrac permission for CCing usersI had like to have the necessary permissions to add people to tickets (CC) for the TorBirdy component. Thank you!I had like to have the necessary permissions to add people to tickets (CC) for the TorBirdy component. Thank you!Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10590Give mttp developer privileges on trac2020-06-13T16:47:38ZMatt PaganGive mttp developer privileges on tracI promise not to ruin everything.I promise not to ruin everything.https://gitlab.torproject.org/legacy/trac/-/issues/10690Trac error on password change2020-06-13T16:47:41ZTracTrac error on password changeTrac causes this error when trying to change my password:
```
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/trac/web/api.py", line 514, in send_error
data, 'text/html')
File "/usr/lib/python2.7/dist-p...Trac causes this error when trying to change my password:
```
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/trac/web/api.py", line 514, in send_error
data, 'text/html')
File "/usr/lib/python2.7/dist-packages/trac/web/chrome.py", line 976, in render_template
data = self.populate_data(req, data)
File "/usr/lib/python2.7/dist-packages/trac/web/chrome.py", line 882, in populate_data
'context': web_context(req) if req else None,
File "/usr/lib/python2.7/dist-packages/trac/web/chrome.py", line 292, in web_context
perm = req.perm
File "/usr/lib/python2.7/dist-packages/trac/web/api.py", line 316, in __getattr__
value = self.callbacks[name](self)
File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 264, in _get_perm
return PermissionCache(self.env, self.authenticate(req))
File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 135, in authenticate
authname = authenticator.authenticate(req)
File "build/bdist.linux-x86_64/egg/acct_mgr/util.py", line 82, in wrap
return func(self, *args, **kwds)
File "build/bdist.linux-x86_64/egg/acct_mgr/web_ui.py", line 374, in authenticate
return auth.LoginModule.authenticate(self, req)
File "/usr/lib/python2.7/dist-packages/trac/web/auth.py", line 91, in authenticate
req.incookie['trac_auth'])
File "build/bdist.linux-x86_64/egg/acct_mgr/web_ui.py", line 448, in _get_name_for_cookie
name = auth.LoginModule._get_name_for_cookie(self, req, cookie)
File "/usr/lib/python2.7/dist-packages/trac/web/auth.py", line 238, in _get_name_for_cookie
name = self._cookie_to_name(req, cookie)
File "/usr/lib/python2.7/dist-packages/trac/web/auth.py", line 234, in _cookie_to_name
for name, in self.env.db_query(sql, args):
File "/usr/lib/python2.7/dist-packages/trac/db/api.py", line 122, in execute
return db.execute(query, params)
File "/usr/lib/python2.7/dist-packages/trac/db/util.py", line 121, in execute
cursor.execute(query, params)
File "/usr/lib/python2.7/dist-packages/trac/db/util.py", line 65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
InternalError: current transaction is aborted, commands ignored until end of transaction block
```
Supposedly, some characters in the new password are trickling down to the SQL level where the SQL statement responsible for setting the password has not been authored correctly. This may pose a potential **security** hole.
**Trac**:
**Username**: GITNEErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/10956Please create a component for deb.tpo2020-06-13T16:47:45ZLunarPlease create a component for deb.tpoIt's the second time that I wanted to report an issue about deb.tpo and I had no proper component to use. I think that's a sign we need one.
weasel, what do you think of adding one? Would you be fine owning that component?It's the second time that I wanted to report an issue about deb.tpo and I had no proper component to use. I think that's a sign we need one.
weasel, what do you think of adding one? Would you be fine owning that component?Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/10961Create a TIMB and a PCPHS component2020-06-13T16:47:46ZKarsten LoesingCreate a TIMB and a PCPHS componentWe need two new components for two products that will come out of Sponsor O. One is the Tor Instant Messaging Bundle (TIMB), and another is Point-click-publish Hidden Services which I'm going to abbreviate with PCPHS. We can still rena...We need two new components for two products that will come out of Sponsor O. One is the Tor Instant Messaging Bundle (TIMB), and another is Point-click-publish Hidden Services which I'm going to abbreviate with PCPHS. We can still rename components later if we want better names. I'm creating these components myself. This ticket is only for documentation purposes.Karsten LoesingKarsten Loesing