Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:28:49Zhttps://gitlab.torproject.org/legacy/trac/-/issues/2048Make repository syncing from cupani to jepsonii smarter2020-06-13T16:28:49ZSebastian HahnMake repository syncing from cupani to jepsonii smarterWe currently sync all git repositories from cupani to jepsonii, but instead we should only sync those listed in /srv/git.torproject.org/projects.list on cupani. Also, we should make sure that don't exist on cupani/aren't listed in its pr...We currently sync all git repositories from cupani to jepsonii, but instead we should only sync those listed in /srv/git.torproject.org/projects.list on cupani. Also, we should make sure that don't exist on cupani/aren't listed in its projects.list file anymore are removed on jepsonii, as well.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/2023please provision a server/VM for Thandy testing2010-10-27T20:52:23ZErinn Clarkplease provision a server/VM for Thandy testingWe're going to start working on Thandy (https://trac.torproject.org/projects/tor/wiki/projects/Thandy) and need a server to begin testing distribution, roles, and other such things. Having a URL like thandy-test.torproject.org would be g...We're going to start working on Thandy (https://trac.torproject.org/projects/tor/wiki/projects/Thandy) and need a server to begin testing distribution, roles, and other such things. Having a URL like thandy-test.torproject.org would be good too.
Some requirements:
* three separate accounts: one for timestamping, one for me to use and upload stuff, and one to run the webserver. I'll suggest these as names: thandy-admin, thandy-upload, and thandy-www. Maybe someone (Nick) will have better suggestions.
* admin-level permissions for Sebastian and I to be able to change server configuration. For this reason it might be better to have a separate VM dedicated to Thandy stuff, though given the currently minimal resource requirements, it could be a pretty small one.
* ability to serve stuff over http/https.
Thanks!Deliverable-Mar2011weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1986migrate vidalia's trac into tor's trac2020-06-13T00:07:35ZRoger Dingledinemigrate vidalia's trac into tor's tracVidalia's bugs are getting lonely because people don't look at them much.
If they were in tor's trac, I would help prioritize them and nag people to fix the important usability issues.
Bug we don't just want to import all the vidalia t...Vidalia's bugs are getting lonely because people don't look at them much.
If they were in tor's trac, I would help prioritize them and nag people to fix the important usability issues.
Bug we don't just want to import all the vidalia trac entries into our trac, because the numbers won't line up.
Maybe the best answer is to let the old trac die, and put it up somewhere in a read-only way, and add a new Vidalia component to our trac and cherry-pick the bugs we want to keep active?weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1985Migrate vidalia's svn2010-10-11T10:58:40ZRoger DingledineMigrate vidalia's svnhttps://ganymede.vidalia-project.net/~edmanm/vidalia-svn.tar.gz{,.asc}
Weasel said he'd import the svn given the svn dump. We should import it as svn to start with.https://ganymede.vidalia-project.net/~edmanm/vidalia-svn.tar.gz{,.asc}
Weasel said he'd import the svn given the svn dump. We should import it as svn to start with.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1977Please upgrade bahri to Squeeze2010-10-01T11:08:05ZChristian FrommePlease upgrade bahri to Squeezeweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1932Add serra and porrum to nagios2010-10-01T11:33:29ZAndrew LewmanAdd serra and porrum to nagiosPlease add serra and porrum to nagios.Please add serra and porrum to nagios.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1858Please dedicate a vm for torbel2010-10-01T11:09:05ZSebastian HahnPlease dedicate a vm for torbelWe need a vm for torbel and related services (check can move there eventually too). Do we have one sitting around, or can we repurpose another one? I expect high cpu load and moderate memory requirements (256mb should be fine).We need a vm for torbel and related services (check can move there eventually too). Do we have one sitting around, or can we repurpose another one? I expect high cpu load and moderate memory requirements (256mb should be fine).weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1735Decide what to do with the debian/ directory in Tor2020-06-13T14:05:15ZSebastian HahnDecide what to do with the debian/ directory in TorDuring the dev mtg, it was suggested to keep the debian/ directory more up to date by merging weasel's changes more often. The alternative idea was to remove it entirely to make sure people don't find a debian directory and expect it to ...During the dev mtg, it was suggested to keep the debian/ directory more up to date by merging weasel's changes more often. The alternative idea was to remove it entirely to make sure people don't find a debian directory and expect it to work.Tor: 0.2.2.x-finalweasel (Peter Palfrader)weasel (Peter Palfrader)https://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/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/1707We need a howto for running oprofile properly2020-06-13T14:05:11ZNick MathewsonWe need a howto for running oprofile properlyI hear that we don't have a good description of the best way to oprofile Tor and get useful results. It would be great to have a patch to doc/HACKING explaining how to do this. Weasel said that he could, if he were reminded. This task...I hear that we don't have a good description of the best way to oprofile Tor and get useful results. It would be great to have a patch to doc/HACKING explaining how to do this. Weasel said that he could, if he were reminded. This task exists to remind him.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1704please give website push privileges to the following people2010-10-11T10:58:48ZErinn Clarkplease give website push privileges to the following peopleMe (erinn), Sebastian, and Runa.Me (erinn), Sebastian, and Runa.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1702backup pg on jepsonii2011-12-16T21:54:14Zweasel (Peter Palfrader)backup pg on jepsoniiHi helix,
I notice jepsonii has these files:
weasel@jepsonii:/srv/trac.torproject.org/trac/tor/db$ ls -la
total 191984
drwxr-sr-x 2 erinn tracadm 4096 Jul 19 15:20 ./
drwxrwsr-x 11 tracweb tracadm 4096 Jul 19 15:21 ../
-rw-r...Hi helix,
I notice jepsonii has these files:
weasel@jepsonii:/srv/trac.torproject.org/trac/tor/db$ ls -la
total 191984
drwxr-sr-x 2 erinn tracadm 4096 Jul 19 15:20 ./
drwxrwsr-x 11 tracweb tracadm 4096 Jul 19 15:21 ../
-rw-r--r-- 1 erinn tracadm 26523873 Apr 23 08:35 postgres.21.1272011675.bak.gz
-rw-r--r-- 1 erinn tracadm 55822963 Jun 9 05:16 postgres.21.1276060556.bak.gz
-rw-r--r-- 1 erinn tracadm 55823056 Jun 9 05:19 postgres.21.1276060710.bak.gz
-rw-r--r-- 1 erinn tracadm 58190324 Jul 19 15:21 postgres.21.1279552818.bak.gz
It seems to me this is exactly what we want anyway. How did you cause these files to be created?weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/1701torperf https2010-10-01T11:37:03Zweasel (Peter Palfrader)torperf httpshttps everywhere redirects *.tpo (with exception of archive) to https, so we should do https on torperf.https everywhere redirects *.tpo (with exception of archive) to https, so we should do https on torperf.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/12520.2.1.23 deb can't do tls renegotiation2020-06-13T14:03:52ZRoger Dingledine0.2.1.23 deb can't do tls renegotiationzzz_> Hello, I am using Debian Sid with Tor 0.2.1.23 and Vidalia 0.2.7. When
I try to connect to the Tor network, Vidalia shows this error: [Warning] TLS
error: unexpected close while renegotiating. Is this is a known problem?
> zzz_: a...zzz_> Hello, I am using Debian Sid with Tor 0.2.1.23 and Vidalia 0.2.7. When
I try to connect to the Tor network, Vidalia shows this error: [Warning] TLS
error: unexpected close while renegotiating. Is this is a known problem?
> zzz_: are you using tor as a client, and it's failing?
zzz_> arma: Yes, I am running as a client only. It has started to give this
error very recently.
zzz_> arma: Actually the Debian changelog might give us a hint:
http://packages.debian.org/changelogs/pool/main/t/tor/tor_0.2.1.23-1/changelog
See also http://archives.seul.org/or/talk/Feb-2010/msg00159.html which is another
person reporting this problem.
[Automatically added by flyspray2trac: Operating System: All]weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/949Tor server can't bind itself to a ip address and dies.2020-06-13T14:01:29ZTracTor server can't bind itself to a ip address and dies.I am using Tor version 0.2.0.34 (r18423).
I have set up Tor to bind the server to the localhost loopback and to a local network ip address.
By default the daemon is configured to start in runlevel 2 with S20tor.
When the system starts, t...I am using Tor version 0.2.0.34 (r18423).
I have set up Tor to bind the server to the localhost loopback and to a local network ip address.
By default the daemon is configured to start in runlevel 2 with S20tor.
When the system starts, there is a race condition of the daemons on the same run-level and if the kernel
hasn't yet registered the ip address of the local network
interface because it's querying in dhcp mode,
tor puts a message on stdout on boot that it wasn't able to bind itself to the LAN address specified and dies.
This is very annoying,because I often start the system and then I don't find the expected instance of tor running,
even if the interface and the local ip address are working.
For me it's better if the started instance of tor,keep polling for specified ip address instead of die.
Also moving the name of the file to something like S90tor on all runlevels seems to help partially as the problem seems just to slightly
decrease.(this confirm the race condition problem)
I can't attach any log output as it does not output nothing relevant in the logs...it just dies.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: maviorweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/217wml-ize the gui pages2020-06-13T17:18:11ZTracwml-ize the gui pagesThe GUI competition pages aren't in WML and have become outdated (the headers have a couple of errors).
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: nileThe GUI competition pages aren't in WML and have become outdated (the headers have a couple of errors).
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: nileweasel (Peter Palfrader)weasel (Peter Palfrader)