The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-27T14:17:35Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29691Builds from master fail on Jenkins mingw builder2020-06-27T14:17:35ZTracBuilds from master fail on Jenkins mingw builderOn https://jenkins.torproject.org/view/tor/ the builds from git master for tor-ci-mingwcross-master builder are failing for a long time (Last successful build (# 2226), 2 mo 20 days ago )
A failing build log e.g. https://jenkins.torproj...On https://jenkins.torproject.org/view/tor/ the builds from git master for tor-ci-mingwcross-master builder are failing for a long time (Last successful build (# 2226), 2 mo 20 days ago )
A failing build log e.g. https://jenkins.torproject.org/view/tor/job/tor-ci-mingwcross-master/lastCompletedBuild/ARCHITECTURE=amd64,SUITE=stretch/consoleFull#-16059184715da2eb1d-1267-4376-8b22-f5f143383dc7
```
21:28:05 + cp src/test/test-child.exe /srv/jenkins-workspace/workspace/tor-ci-mingwcross-master/ARCHITECTURE/amd64/SUITE/stretch/RESULT/bin/
21:28:05 cp: cannot stat 'src/test/test-child.exe': No such file or directory
21:28:05 + rc=1
```
There are no usable artifacts as a result, for those who wish to use them. Aside, no artifacts are kept on Appveyor too.
**Trac**:
**Username**: harigTor: 0.4.0.x-finalAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29697archive.tpo is soon running out of space2020-06-27T14:17:34Zboklmarchive.tpo is soon running out of spaceThe machine hosting archive.tpo will soon be running out of space.
Possible solutions include:
* adding more resources to it. According to weasel, it seems doing this would require a new host, which would be quite expensive.
* removin...The machine hosting archive.tpo will soon be running out of space.
Possible solutions include:
* adding more resources to it. According to weasel, it seems doing this would require a new host, which would be quite expensive.
* removing some of the less useful files from archive.tpo. For example we could remove Tor Browser versions that are more than 4 years old. Or alpha versions that are more than 2 years old.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/team/-/issues/29709install smartd2020-06-27T14:17:34Zweasel (Peter Palfrader)install smartdfind out where to run smartmontools (e.g. bungei) and then install it with puppetfind out where to run smartmontools (e.g. bungei) and then install it with puppetanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29764Accessing this bug tracker via TorBrowser results in endless loop of captchas2020-06-27T14:17:34ZTracAccessing this bug tracker via TorBrowser results in endless loop of captchasTrac always thinks submission is spam, even on successful authentication and captcha replies.
**Trac**:
**Username**: DNiedTrac always thinks submission is spam, even on successful authentication and captcha replies.
**Trac**:
**Username**: DNiedJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29774Please create 2019.www.torproject.org2020-06-27T14:17:34ZHiroPlease create 2019.www.torproject.orgThis should serve as archive for the current website.This should serve as archive for the current website.https://gitlab.torproject.org/tpo/tpa/team/-/issues/29781Adding Fundraising Team page to https://trac.torproject.org home page2020-06-27T14:17:34ZalsmithAdding Fundraising Team page to https://trac.torproject.org home pageThe Fundraising Team now has a Wiki page, hooray! It's here: https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam
I don't have the permissions to edit the trac.torproject.org home page and add the Fundraising Team und...The Fundraising Team now has a Wiki page, hooray! It's here: https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam
I don't have the permissions to edit the trac.torproject.org home page and add the Fundraising Team under the 'Teams' header.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29788Create email alias to core contributor Vinícius Zavam (egypcio)2020-06-27T14:17:34ZGusCreate email alias to core contributor Vinícius Zavam (egypcio)Hello, please create the email alias for our core contributor Vinicius Zavam (egypcio):
egypcio@tpo to egypcio@riseup.net
thanks!
GusHello, please create the email alias for our core contributor Vinicius Zavam (egypcio):
egypcio@tpo to egypcio@riseup.net
thanks!
Gushttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29796synchronize puppet and LDAP hosts2020-06-27T14:17:34Zanarcatsynchronize puppet and LDAP hostsWe have hosts that are in Puppet and not in LDAP and vice versa. Every host in LDAP should be in Puppet and vice versa.
We have 78 hosts in LDAP and 74 in Puppet, with 73 hosts in common. This is the current diff:
```
$ diff puppet lda...We have hosts that are in Puppet and not in LDAP and vice versa. Every host in LDAP should be in Puppet and vice versa.
We have 78 hosts in LDAP and 74 in Puppet, with 73 hosts in common. This is the current diff:
```
$ diff puppet ldap
29a30,31
> geyeri.torproject.org
> gillii.torproject.org
36d37
< hyalinum.torproject.org
74a76,78
> weissii.torproject.org
> winklerianum.torproject.org
> woronowii.torproject.org
```
That is, right now, we have the following hosts in LDAP but not in Puppet:
* geyeri.torproject.org
* gillii.torproject.org
* weissii.torproject.org
* winklerianum.torproject.org
* woronowii.torproject.org
The following is in Puppet, but not LDAP:
* hyalinum.torproject.org
The two lists (`puppet` and `ldap`) were obtain using the following commands:
```
ssh -t pauli.torproject.org 'sudo -u postgres psql puppetdb -P pager=off -A -t -c "SELECT c.certname FROM certnames c WHERE c.deactivated IS NULL"' | tee puppet
tail -n +2 puppet | sort | sponge puppet
ssh alberti.torproject.org 'ldapsearch -h db.torproject.org -x -ZZ -b dc=torproject,dc=org -LLL "hostname=*.torproject.org" hostname | awk "\$1 == \"hostname:\" {print \$2}" | sort' > ldap
```
... as detailed in the [new Puppet docs](https://help.torproject.org/tsa/howto/puppet/).
I'm not exactly sure how to resolve this. When weasel saw a previous version of this list, he said:
```
12:30:00 <weasel> from a quick glance, all but the arm hosts can go.
12:30:06 <weasel> best to double-check with ldap.
12:30:19 <weasel> if they are not in ldap, and they haven't done a puppet run in a while, they should be removed from puppet also.
12:30:45 <weasel> gillii and geyeri are the old CRM hosts. I think linus wants to kill them soon but maybe keep them around (and offline) for now.
```
According to nagios, hyalinum has not checked into Puppet since 2018-02-12T08:53:13.339Z, over a month ago. So presumably that should be removed from puppet, and we should double-check the retirement procedure to see if it was completed correctly.
The hosts in LDAP and not in Puppet should probably be added to puppet, carefully (--noop is your friend) to see if it breaks anything.
In the future, we might want to add a Nagios check on the Puppet server to make sure this is synchronized.https://gitlab.torproject.org/tpo/tpa/team/-/issues/29817dead disk on moly2020-06-27T14:17:33Zanarcatdead disk on molyone of the hard drives on moly has died. this was spotted by cymru's staff and confirmed when smartd was installed (legacy/trac#29709).
i have done some research on the machine to figure out what's up, and wrote the following reply to C...one of the hard drives on moly has died. this was spotted by cymru's staff and confirmed when smartd was installed (legacy/trac#29709).
i have done some research on the machine to figure out what's up, and wrote the following reply to Cymru's people:
> [...] I can confirm that one of the hard drives in Moly has failed, according to SMART metrics we have available.
>
> According to smartd, that disk is:
>
> [SEAGATE ST3600057SS 0008], lu id: 0x5000c5003b5bc36f, S/N: 6SL1G7Q60000N1497K0E, 600 GB
>
> It's a 600GB SAS drive. It's part of a megaraid RAID-10 array that has marked the drive as "Firmware state: Failed". I'll go under the assertiont his means the drive is dead.
>
> Being new here, I'm not familiar with the machine either. From what I can tell, it's a Supermicro X8DTU motherboard, and possibly an iXsystems iX1204-R700UB case. Does it look like this this picture?
>
> https://static.ixsystems.co/uploads/2017/08/1204h-t_front.png
>
> If so, the only datasheet I could find is this limited PDF:
>
> https://www.ixsystems.com/wp-content/uploads/2017/09/Server_Line_2017_WEB.pdf
>
> It *does* say the hard drives are hot-swappable, so in theory, it should just be a matter of replacing the hard drive.
>
> It looks like each drive has its own LED, hopefully the one with the amber warning light should be the dead disk. I've issued a command to the RAID controller to make it "flash" the drive LED, so hopefully that will allow you to locate it better.
>
> I *think* the disk controller is new enough for you to simply hot swap the drive with a new one without any other intervention on our part. But it might be better if we are available during the operation. [...]
I've created some documentation on the hardware RAID stuff here:
https://help.torproject.org/tsa/howto/raid/
we're at the waiting step now - we'll see if Cymru can do the replacement and when. i'm still not quite certain we can just hotswap the drive, but I'm hoping we can.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29820Change PGP key for ahf2020-06-27T14:17:33ZLinus Nordberglinus@torproject.orgChange PGP key for ahfLinus Nordberglinus@torproject.orgLinus Nordberglinus@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29822prometheus server cannot reach build-arm* boxes2020-06-27T14:17:33Zanarcatprometheus server cannot reach build-arm* boxesThe `build-arm-0[None..None](../compare/None...None).torproject.org` boxes are behind NAT (or some sort of firewall?) which makes them unreachable from the global internet. They are therefore not monitored from the Prometheus server righ...The `build-arm-0[None..None](../compare/None...None).torproject.org` boxes are behind NAT (or some sort of firewall?) which makes them unreachable from the global internet. They are therefore not monitored from the Prometheus server right now, although they *are* reachable from the Nagios server.
We need to setup a similar configuration to have those boxes scraped like the other ones.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/team/-/issues/29841ipsec VPN generates gigantic logs2020-06-27T14:17:33Zanarcatipsec VPN generates gigantic logsSerious yak shaving night...
To try to silence this seemingly innocuous warning:
```
/etc/cron.daily/logrotate:
error: Compressing program wrote following message to stderr when compressing log /var/log/syslog.1:
gzip: stdin: file size...Serious yak shaving night...
To try to silence this seemingly innocuous warning:
```
/etc/cron.daily/logrotate:
error: Compressing program wrote following message to stderr when compressing log /var/log/syslog.1:
gzip: stdin: file size changed while zipping
```
... I have looked at the logrotate configuration deployed through Puppet, and it seems slightly out of date compared to the one available in stretch. This is the configuration left over from the stretch upgrade on eugeni, for example:
```
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
invoke-rc.d syslog-ng reload > /dev/null
endscript
}
/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
/var/log/error
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
invoke-rc.d syslog-ng reload > /dev/null
endscript
}
```
Out of those, we're not doing the `syslog-ng reload`, the `delaycompress`, `notifempty` and each logfile is in a separate block which makes it harder to read. So I looked at doing the postrotate action, but then I realized it was happening on the syslog logfile which *is* correctly reloaded. so then i figured the `delaycompress` might be the bit missing.
but before enabling that blindly, I figured I would check if this would blow up the disk space on a server. how to do that you ask? well with our shiny new Cumin tool of course:
```
anarcat@curie:~(master)$ cumin -p 0 '*' 'for log in /var/log/*.log ; do if [ `du -b "$log" | cut -f1` -gt 1000000000 ] ; then echo "logfile $log larger than 1GB"; exit 1 ; fi; done'
74 hosts will be targeted:
alberti.torproject.org,arlgirdense.torproject.org,bracteata.torproject.org,brulloi.torproject.org,build-arm-[None..None](../compare/None...None).torproject.org,build-x86-[None..None](../compare/None...None).torproject.org,bungei.torproject.org,carinatum.torproject.org,cdn-backend-sunet-01.torproject.org,chamaemoly.torproject.org,chiwui.torproject.org,colchicifolium.torproject.org,corsicum.torproject.org,crispum.torproject.org,crm-ext-01.torproject.org,crm-int-01.torproject.org,cupani.torproject.org,dictyotum.torproject.org,eugeni.torproject.org,fallax.torproject.org,forrestii.torproject.org,gayi.torproject.org,getulum.torproject.org,gitlab-01.torproject.org,henryi.torproject.org,hetzner-hel1-[None..None](../compare/None...None).torproject.org,hetzner-nbg1-01.torproject.org,hyalinum.torproject.org,iranicum.torproject.org,kvm[None..None](../compare/None...None).torproject.org,listera.torproject.org,macrum.torproject.org,majus.torproject.org,materculae.torproject.org,meronense.torproject.org,moly.torproject.org,neriniflorum.torproject.org,nevii.torproject.org,nova.torproject.org,nutans.torproject.org,omeiense.torproject.org,oo-hetzner-03.torproject.org,opacum.torproject.org,orestis.torproject.org,oschaninii.torproject.org,palmeri.torproject.org,pauli.torproject.org,peninsulare.torproject.org,perdulce.torproject.org,polyanthum.torproject.org,rouyi.torproject.org,rude.torproject.org,savii.torproject.org,saxatile.torproject.org,scw-arm-ams-01.torproject.org,scw-arm-par-01.torproject.org,staticiforme.torproject.org,subnotabile.torproject.org,textile.torproject.org,togashii.torproject.org,troodi.torproject.org,unifolium.torproject.org,vineale.torproject.org,web-cymru-01.torproject.org,web-hetzner-01.torproject.org
Confirm to continue [y/n]? y
|██████████████▌ | 12% (9/74) [00:47<08:25, 7.78s/hosts]
===== NODE GROUP ===== |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
(3) build-arm-[None..None](../compare/None...None).torproject.org |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
----- OUTPUT of 'for log in /var/...xit 1 ; fi; done' ----- |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
Connection timed out during banner exchange |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
===== NODE GROUP ===== |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
(5) hetzner-hel1-01.torproject.org,kvm4.torproject.org,macrum.torproject.org,textile.torproject.org,unifolium.torproject.org |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
----- OUTPUT of 'for log in /var/...xit 1 ; fi; done' ----- |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
logfile /var/log/daemon.log larger than 1GB |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
===== NODE GROUP ===== |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
(1) hyalinum.torproject.org |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
----- OUTPUT of 'for log in /var/...xit 1 ; fi; done' ----- |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
ssh: Could not resolve hostname hyalinum.torproject.org: No address associated with hostname |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
================ PASS |████████████████████████████████████████████████████████████████████████████████████████████████████████▌ | 88% (65/74) [00:52<00:07, 1.23hosts/s]
FAIL |██████████████▌ | 12% (9/74) [00:52<08:25, 7.78s/hosts]
12.2% (9/74) of nodes failed to execute command 'for log in /var/...xit 1 ; fi; done': build-arm-[None..None](../compare/None...None).torproject.org,hetzner-hel1-01.torproject.org,hyalinum.torproject.org,kvm4.torproject.org,macrum.torproject.org,textile.torproject.org,unifolium.torproject.org
87.8% (65/74) success ratio (>= 0.0% threshold) for command: 'for log in /var/...xit 1 ; fi; done'.: alberti.torproject.org,arlgirdense.torproject.org,bracteata.torproject.org,brulloi.torproject.org,build-x86-[None..None](../compare/None...None).torproject.org,bungei.torproject.org,carinatum.torproject.org,cdn-backend-sunet-01.torproject.org,chamaemoly.torproject.org,chiwui.torproject.org,colchicifolium.torproject.org,corsicum.torproject.org,crispum.torproject.org,crm-ext-01.torproject.org,crm-int-01.torproject.org,cupani.torproject.org,dictyotum.torproject.org,eugeni.torproject.org,fallax.torproject.org,forrestii.torproject.org,gayi.torproject.org,getulum.torproject.org,gitlab-01.torproject.org,henryi.torproject.org,hetzner-hel1-[None..None](../compare/None...None).torproject.org,hetzner-nbg1-01.torproject.org,iranicum.torproject.org,kvm5.torproject.org,listera.torproject.org,majus.torproject.org,materculae.torproject.org,meronense.torproject.org,moly.torproject.org,neriniflorum.torproject.org,nevii.torproject.org,nova.torproject.org,nutans.torproject.org,omeiense.torproject.org,oo-hetzner-03.torproject.org,opacum.torproject.org,orestis.torproject.org,oschaninii.torproject.org,palmeri.torproject.org,pauli.torproject.org,peninsulare.torproject.org,perdulce.torproject.org,polyanthum.torproject.org,rouyi.torproject.org,rude.torproject.org,savii.torproject.org,saxatile.torproject.org,scw-arm-ams-01.torproject.org,scw-arm-par-01.torproject.org,staticiforme.torproject.org,subnotabile.torproject.org,togashii.torproject.org,troodi.torproject.org,vineale.torproject.org,web-cymru-01.torproject.org,web-hetzner-01.torproject.org
87.8% (65/74) success ratio (>= 0.0% threshold) of nodes successfully executed all commands.: alberti.torproject.org,arlgirdense.torproject.org,bracteata.torproject.org,brulloi.torproject.org,build-x86-[None..None](../compare/None...None).torproject.org,bungei.torproject.org,carinatum.torproject.org,cdn-backend-sunet-01.torproject.org,chamaemoly.torproject.org,chiwui.torproject.org,colchicifolium.torproject.org,corsicum.torproject.org,crispum.torproject.org,crm-ext-01.torproject.org,crm-int-01.torproject.org,cupani.torproject.org,dictyotum.torproject.org,eugeni.torproject.org,fallax.torproject.org,forrestii.torproject.org,gayi.torproject.org,getulum.torproject.org,gitlab-01.torproject.org,henryi.torproject.org,hetzner-hel1-[None..None](../compare/None...None).torproject.org,hetzner-nbg1-01.torproject.org,iranicum.torproject.org,kvm5.torproject.org,listera.torproject.org,majus.torproject.org,materculae.torproject.org,meronense.torproject.org,moly.torproject.org,neriniflorum.torproject.org,nevii.torproject.org,nova.torproject.org,nutans.torproject.org,omeiense.torproject.org,oo-hetzner-03.torproject.org,opacum.torproject.org,orestis.torproject.org,oschaninii.torproject.org,palmeri.torproject.org,pauli.torproject.org,peninsulare.torproject.org,perdulce.torproject.org,polyanthum.torproject.org,rouyi.torproject.org,rude.torproject.org,savii.torproject.org,saxatile.torproject.org,scw-arm-ams-01.torproject.org,scw-arm-par-01.torproject.org,staticiforme.torproject.org,subnotabile.torproject.org,togashii.torproject.org,troodi.torproject.org,vineale.torproject.org,web-cymru-01.torproject.org,web-hetzner-01.torproject.org
```
This might not be very easy to read, but the important bit is this:
```
(5) hetzner-hel1-01.torproject.org,kvm4.torproject.org,macrum.torproject.org,textile.torproject.org,unifolium.torproject.org
----- OUTPUT of 'for log in /var/...xit 1 ; fi; done' -----
|logfile /var/log/daemon.log larger than 1GB
```
So I looked at the first one of those (hetzner-hel1-01) and lo and behold, the `daemon.log` is gigantic:
```
1,4G /var/log/daemon.log
```
I looked into the file briefly and it looks like a *lot* of information from ipsec. But before I start shaving another yak, I figured I would just file this as a ticket to document how far I went and let this one rest for a while.
(I did end up setting delaycompress after doing more investigations in Prometheus about free disk space, but that's documented in the tor-puppet commit 44f86c7d and previous.)weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/team/-/issues/29846fstrim script makes noises on some servers2020-06-27T14:17:33Zanarcatfstrim script makes noises on some serverswe get this nightly since bungei was installed:
```
To: root@bungei.torproject.org
Date: Thu, 21 Mar 2019 06:25:03 +0000
/etc/cron.daily/puppet-trim-fs:
fstrim: /srv/backups/pg: the discard operation is not supported
fstrim: /srv/backu...we get this nightly since bungei was installed:
```
To: root@bungei.torproject.org
Date: Thu, 21 Mar 2019 06:25:03 +0000
/etc/cron.daily/puppet-trim-fs:
fstrim: /srv/backups/pg: the discard operation is not supported
fstrim: /srv/backups/bacula: the discard operation is not supported
```
this is from the following script deployed through puppet:
```
# by weasel
if tty > /dev/null; then
verbose="-v"
else
verbose=""
fi
awk '$9 ~ "^(ext4|xfs)$" && $4 == "/" {print $3, $5}' /proc/self/mountinfo | while read mm mountpoint; do
path="/sys/dev/block/$mm"
[ -e "$path" ] || continue
path="$(readlink -f "$path")"
while : ; do
qi="$path/queue/discard_max_bytes"
if [ -e "$qi" ]; then
[ "$(cat "$qi")" -gt "0" ] && fstrim $verbose "$mountpoint"
break
fi
# else try the parent
path="$(readlink -f "$path/..")"
# as long as it's a device
[ -e "$path/dev" ] || break
done
done
```
I can confirm the mapped device cannot be "trimmed":
```
root@bungei:/home/anarcat# fstrim -v /srv/backups/pg
fstrim: /srv/backups/pg: the discard operation is not supported
```
I'm unsure why that is the case. I suspect it might be a matter of adding the `issue_discards` option to `lvm.conf`, but I'm not sure. I also note that the `discard` option is not present in `crypptab` either.
In the [Debian wiki SSDOptimization page](https://wiki.debian.org/SSDOptimization), they mention a `fstrim` systemd service (not required in Buster, apparently) that supposedly takes care of that work for us. It does, however, only the following command:
```
fstrim -av
```
... which doesn't seem to do anything here. It also doesn't silence the warnings from the script, so I'm not sure it's *doing* anything.
In any case, I welcome advice on how to deal with that one warning.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29852Let ahf and cohosh push to /pluggable-transports/snowflake.git2020-06-27T14:17:33ZDavid Fifielddcf@torproject.orgLet ahf and cohosh push to /pluggable-transports/snowflake.git```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I'l like ahf and cohosh to be able to push to the
/pluggable-transports/snowflake.git repo.
Signed, David 2019-03-21
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEeXoyauxKR4rwUMw64rk...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I'l like ahf and cohosh to be able to push to the
/pluggable-transports/snowflake.git repo.
Signed, David 2019-03-21
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEeXoyauxKR4rwUMw64rk9gVzTiOUFAlyUEAoACgkQ4rk9gVzT
iOXPww//UwoNN6Fi3PaKepwqQYbO6TunJJ4SeBzwDPKOFwOe0E0F5zSzJnVP329h
8f5o/20E88gRdHRlbJ5SzZnGWwW2KJFSRStJhSx7r3glJrsbsK6gUXFB8nbIuM7B
sczbG7gzOv9b3ly/EjjBk0+mC5EjtdzqsiqKYDH2mXQCRoDQsqlnWAvCVfPPgnC4
LRyFLtaK5dZQU6gRWqBN1EhWzrtLdbl2qSG2mLot+8z/BJrUk2BkNDXsyQla6ahP
vKpS3XKN5ldBfxBXTqOLZQTgUKQwRoTIT0xZpbuSb2WCRx7N3WDWbpwKbyL4GTJO
ZNNXsrz5qiSZ6h20qHTMt4TMrmKMQrmkcocWJ/6uqCqYCrDqCyF7SFmfwJzNYgtE
36OfQnaYcuH8XJYHEviwrLJRPWfgjcxzkEvA/RxwFTl/1Er1ulwxrFq8yya8IFCy
uQjSydLtga/WLWhq993x8aUGFvapF4P8L9iWkRSEqxln+WTxbx4F3yAszH3UeALS
eCzyl5kp6N1MkEB+VbvfsEViOLYqSwgZf74XRkmcMt9R1fy72CpSqUO24gY0Neuu
XpJ7F6+ksvKhKie31fZPxQb30ifEyZgsXSh4a9ia/62X99cl13sAZ/aoJ3vCjT8L
kfCRit6QtZ5GuPCOXTuiPbgkxlBJRvnp4TZsB8iAkmIUoBuzH5U=
=nwyV
-----END PGP SIGNATURE-----
```https://gitlab.torproject.org/tpo/tpa/team/-/issues/29889Add email alias nextcloud-admin@tpo2020-06-27T14:17:32ZLinus Nordberglinus@torproject.orgAdd email alias nextcloud-admin@tpoIn order to not have to add individuals to trac tickets related to nextcloud service administration, let's have an email alias for this group. We can then let that alias be the owner of the trac component.In order to not have to add individuals to trac tickets related to nextcloud service administration, let's have an email alias for this group. We can then let that alias be the owner of the trac component.Linus Nordberglinus@torproject.orgLinus Nordberglinus@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29921Please create new static component onionperf.torproject.org2020-06-27T14:17:32ZirlPlease create new static component onionperf.torproject.orgThis static component will contain the development/deployment documentation for OnionPerf. This should be built by Jenkins from the git.tpo onionperf.git repository automatically when new pushes are made and I would hope that we can copy...This static component will contain the development/deployment documentation for OnionPerf. This should be built by Jenkins from the git.tpo onionperf.git repository automatically when new pushes are made and I would hope that we can copy over the config from stem.
Please let me know if there are any actions needed from me to progress this (like creating any other tickets for other people).anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29942Please create a new git repo project/tor-browser/fastlane2020-06-27T14:17:32ZMatthew FinkelPlease create a new git repo project/tor-browser/fastlane```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Please create a new public git repo project/tor-browser/fastlane under "Infrastructure and Administration".
The description for this repo should be: Tor Browser app store and dep...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Please create a new public git repo project/tor-browser/fastlane under "Infrastructure and Administration".
The description for this repo should be: Tor Browser app store and deployment configuration for Fastlane
Please give sysrqb and gk write access.
Thanks!
signed for trac.torproject.org on 2019-03-28 17:25:00 UTC
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmQpn3DVLpEMbqGYohK8DqE7aGAAFAlydA5EACgkQhK8DqE7a
GACbMg/+NNf2u/EO+r5mzGVRSFRfFA8zk4izvJtgZqhuv6smEC5E9Utz5hNZPIEr
sZW9UPw5YFtDTs2hd3A37mgGoosRFctoodKsTF2valdQqGr4+ur/7gPW0Q2qDU+I
dZVbPbXpHQBRr7nKcT+4u1L4NSb3JHDKpkoeD4nI3HlG6xG32lixXpvvWIY33YVx
D91gkFxLuibZ5IL0z1VuH8GIjNe8MAv8kp38mc97zyjWvLd86qGDggZ8csw3DCxJ
4YLYwRl7ULzjUeX34wqaWujH4AWEtGqG2aU6BlsFLM3igKSXlAufzww87j8hjbYN
J3g7MpvOfWvij9I0vUTvtOwq5J0uwy8gbGpbWe5vvg76o+HjcR5eXD6gdrIW2W9h
oFfySg2uVVF9oQtS1dRwwP5cZfpQOXygnXHkQe/YmPA5MoLb9hjzADgQrBTM4HlQ
fxmeFSp/CsHIKpVBEqvlPK03SRflHUQcwmiCMG5xMoekE1jazXS3Eyjl2eeA7J4T
Xn+kG5YAuSAbqtk3nwIO+s25STs3RRwUWfw+sHXCkX0Dyd+nd94A36dYVAcIoQMH
rrUT/T78j0LS5XGb1ImgELF13VuoRXhTWfiSdJ3dK7pGm7+PUYJ6XWtKpN0QLBZm
eAqLOU/4pPgPxi/KBTtoe3ZOC7lYFEhHM8zuaiNI8pV/6KA7Cnw=
=Q7cI
-----END PGP SIGNATURE-----
```https://gitlab.torproject.org/tpo/tpa/team/-/issues/29948Add micah to nextcloud-admin@2020-06-27T14:17:32ZLinus Nordberglinus@torproject.orgAdd micah to nextcloud-admin@Linus Nordberglinus@torproject.orgLinus Nordberglinus@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29975Please create email alias/forwarding and LDAP for acat2020-06-27T14:17:31ZErin WyattPlease create email alias/forwarding and LDAP for acat```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please create LDAP and email forwarding for our new browser dev:
Display Name: Alex Catarineu
Forwarding email address: acat@mailbox.org
Desired UID: acat
PGP: 3F5B D76C 2C9B D09B F4...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please create LDAP and email forwarding for our new browser dev:
Display Name: Alex Catarineu
Forwarding email address: acat@mailbox.org
Desired UID: acat
PGP: 3F5B D76C 2C9B D09B F4A8 0AB0 75DC D26C 3A21 2E9A
I verified his key by video chat and signed it today. The key is here (if not everywhere else by now): http://pgp.rediris.es:11371/pks/lookup?op=get&search=0x75DCD26C3A212E9A
Thank you!
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAlyiYzgACgkQugyUAPgP
kc7duQ/+JJoXEoCEqDAqwZerepiS+Iw+rYcXhL+G0M0L/ViRycnOaE4XMOff1KmB
fKgbFi3z7iwWwa5bDjvxgailyBodHHXaWGA62yG1mvH5CZ3rsmIWsQydH1zGvSro
ux4FrjZzOW4aOyDoF2RKFft3MFfHJ9SwVgMITW9ae2Zd+GU6G+u8rG84RKRjy2tL
hiX6kZUnC5V0ri+PNDnIwVcnv0LlkDvQCxq1w6jxOrsPwIaVjl2AGc+sGSXfwI1r
hW2OqzmCh7ItXbtkBr+Rytnq/PzEssZJligkqB5xXP6uMgO+MVcaex6wvXHRzrl+
YBtO1YPeiXfp0GAwn/8OlavjY827buQkpo7+e4xRMYwpJVM85Xj81fe9fbVicFTw
lzd6naELy824HJ0Vwpet5mUw8fBp0OjVEDStREZdUX+duWLN35zRtdSv2V34wSsP
irAcjEeaV28qL/5+uInY/aIF6EscQGTN2lajff1PGOjxzgCFVQrrPt0/vY0z40cl
hJC9ph2RB/QEyv+Mc+o1NfrkKt8UiHPAslNBqKCqYLDHwij00A4M7jPxPM1FrrWp
EDUqzCcNRsV/6oHBHuGkJPG1QV7LGcE26eGuBXMgJUchOtZr0EDgYXPuSCCCg9ly
13iyz+31NS7r2omsmdTlREm9jtx1WAWpmYZbbf11D5ilrsICQzE=
=SuAj
-----END PGP SIGNATURE-----
```https://gitlab.torproject.org/tpo/tpa/team/-/issues/29988Add phw to sponsor19.git with RW access2020-06-27T14:17:31ZMatthew FinkelAdd phw to sponsor19.git with RW access```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add phw to the sponsor19.git repository with RW access.
This message was written for a ticket on trac.torproject.org.
Wed Apr 3 01:16:22 UTC 2019
-----BEGIN PGP SIGNATURE-----...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add phw to the sponsor19.git repository with RW access.
This message was written for a ticket on trac.torproject.org.
Wed Apr 3 01:16:22 UTC 2019
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmQpn3DVLpEMbqGYohK8DqE7aGAAFAlykCXkACgkQhK8DqE7a
GABm/w/+N1Eqc6+1Xa6A83q76KRuwo8zMC1mDItNuacDVpkPZ/JiZLsO5sFdVNZl
r2Md4LRL+/p0K9TykdnYJ162bG5R6LuSSiLH1UXy9EN5HUvC0sVGn9nWyI+661yL
4q7OK6ibl1K8FVaJQPFmx4OCtIxZi9AGvyZJ0TQkcOQ82DAM46blg43U64AMqbGZ
uqe4K43vMNBOM7gLF3WgjX0+Gyw9W7li/we4N7HglTeIM8pMAFVzRIon3d7NOEmQ
mrLBB9gT2FTbJv46jairuuYChg1I1VtI6qWyWSCLKA8GVfS3zmuG8vRdCNE3nR4b
idqfBa/8Mst2d1EBiKf9ootexIaeChbfHceXGLUVlIaZfq3ujmqx+s4bcj2rkXuv
gkdpGpIOhlgFvufJ5MUVPIWhtQeKSbwyd5xmkdxZRl/BEW74gvSuiVIzL1btJHZU
rXwXZ84KJl+x3YA03l+naFAHs6nQpvjqmusRbvmaeRhmQ4VTfE/6dfitVYIbnNmT
Xjn5VBArFX8wPzy988P77Ug64tnhUZp61SQPweFd/jrex1d/229q6smYmZ2VsIYH
QRd8en26z1QiazCkf9Jk8Kq/cke2b31kS7BmqoxZjygCwGkW36Ni0Uohj55nRoQP
4gebMxZynkXDzIgJrghzQqQovqv1aFLmHdyIUHDbsSrR/tvAruw=
=BH2P
-----END PGP SIGNATURE-----
```