Re: [tor-relays] Bridge relays should upgrade to use the new bridge authority
On Wed, Jul 18, 2018 at 08:40:00PM +, nusenu wrote: > you probably want to reach out to package maintainer > that didn't update yet (like the ubuntu snap) - if you didn't do so yet Right, those people should be on the tor-packagers list if they want to hear about it. There is also a separate list of people that we mail personally, like the Debian maintainer, because we're the ones who care most about having the new update happen so it's polite of us to do the extra work. We could add more people to that list. > > AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44 > > A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533 > > I'd expect such email to be signed - yes, even if people can fetch that > data from a signed release. I actually thought about signing it but then I realized that mailman mangles messages to the point that my signatures usually end up bad (yours do too :/ ), so it didn't seem worth fighting with that one. --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Discounts/Free Trials on BSD instances to promote BSD relays?
> On 19 Jul 2018, at 11:34, Conrad Rockenhaus wrote: > > To the point - would it be fair to network stability to offer a week > long free trial to run a tor instance, well, that is if that's what > the user hopefully runs? Would such a model even have an affect on > increasing the number of BSD instances we have on Tor presently? Exits typically see some traffic after a week. It can take guards and middles a few months to get decent traffic. So maybe a month-long trial would be more rewarding? T signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge relays should upgrade to use the new bridge authority
> On 19 Jul 2018, at 10:18, nusenu wrote: > >>> ... >>> Roger Dingledine: If you run a bridge relay, please upgrade -- so your bridge address can resume being given out to censored users, and so your stats can resume being included in the metrics pages. We just put out new releases (0.2.9.16, 0.3.2.11, 0.3.3.9, 0.3.4.5-rc) that retire the old bridge authority and start using a new one. The new bridge authority is "Serge", and it is operated by George from the Tor BSD Diversity project: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html If for whatever reason you can't upgrade yet, you can also manually switch to advertising your bridge descriptor to the new bridge authority by using this torrc line: AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44 A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533 >>> >>> I'd expect such email to be signed - yes, even if people can fetch that >>> data from a signed release. >> >> Please submit a patch to ReleasingTor.md. > > Since Roger's email wasn't the release announcement that email is > not in scope of ReleasingTor.md? If we want the release manager to follow a process when notifying relay operators about a release, the best place to document that process is ReleasingTor.md. Please add another paragraph about emailing affected operators after the existing "Mail the release blurb and ChangeLog” paragraph at: https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md#n210 For relay and bridge operators, the appropriate list is: tor-relays@lists.torproject.org For directory authority operators, the appropriate list is: dir-a...@lists.torproject.org Then you can replace “mail” with "signed mail” where appropriate. T signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Discounts/Free Trials on BSD instances to promote BSD relays?
Conrad wrote > To the point - would it be fair to network stability to offer a week > long free trial to run a tor instance, well, that is if that's what > the user hopefully runs? Would such a model even have an affect on > increasing the number of BSD instances we have on Tor presently? Conrad, For diversity I would participate and learn to use BSD to run a relay. Robert ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Discounts/Free Trials on BSD instances to promote BSD relays?
Howdy, So, anyway, I was previously more active, but I decided on a midlife career change and was on a training path to become a Physician Assistant. Then I was hit by a drunk driver. Now I had to drop out of the program for the next year at least, if at all, so I'm going back to working IT. That's the sob story. I like BSD, primarily FreeBSD (please flame me about how my relays aren't secure later :P) and like promoting the use of it. I have excess capacity on dedicated servers that I personally pay for that are used to host portions of a very popular Wiki based Satire/Dark Humor website. Some of that capacity is already going to Tor. On the servers that have address space SWIPed to me, I would like to resell that capacity specifically to host BSD based Tor relays, exits, bridges, and hidden services. Right now I'm working on infrastructure and a website and trying to somewhat automate things. The question I would like to ask, and honestly, I'm not trying to generate customers, I honestly believe that if a Linux user actually logs into a BSD box for the first time and sees the beauty and grace that the differences between BSD and Linux are that they would want to switch their own personal relay. I'm a firm believer of this. I know there's some hardcore Linux fans out there and that's fine, there's a legion of BSD fans too :). To the point - would it be fair to network stability to offer a week long free trial to run a tor instance, well, that is if that's what the user hopefully runs? Would such a model even have an affect on increasing the number of BSD instances we have on Tor presently? And again, per a suggestion in a previous email chain that I was involved in, I setup my ARIN and RIPE ids, and my providers have SWIPed the address spaces to me so any and all abuse complaints will be coming to me for the address spaces for now on. Thanks, Conrad ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge relays should upgrade to use the new bridge authority
>> you probably want to reach out to package maintainer >> that didn't update yet (like the ubuntu snap) - if you didn't do so yet > > Emailing package maintainers is part of our existing process: > https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md#n171 Chad, do you want to be on the list linked above? > If the maintainer is not on the list, please submit a patch to > ReleasingTor.md, or ask them to join tor-packag...@lists.torproject.org. > >> Roger Dingledine: >>> If you run a bridge relay, please upgrade -- so your bridge address can >>> resume being given out to censored users, and so your stats can resume >>> being included in the metrics pages. >>> >>> We just put out new releases (0.2.9.16, 0.3.2.11, 0.3.3.9, 0.3.4.5-rc) >>> that retire the old bridge authority and start using a new one. The new >>> bridge authority is "Serge", and it is operated by George from the Tor >>> BSD Diversity project: >>> https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html >>> >>> If for whatever reason you can't upgrade yet, you can also manually >>> switch to advertising your bridge descriptor to the new bridge authority >>> by using this torrc line: >>> >>> AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44 >>> A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533 >> >> I'd expect such email to be signed - yes, even if people can fetch that >> data from a signed release. > > Please submit a patch to ReleasingTor.md. Since Roger's email wasn't the release announcement that email is not in scope of ReleasingTor.md? -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge relays should upgrade to use the new bridge authority
> On 19 Jul 2018, at 06:40, nusenu wrote: > > Signed PGP part > you probably want to reach out to package maintainer > that didn't update yet (like the ubuntu snap) - if you didn't do so yet Emailing package maintainers is part of our existing process: https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md#n171 If the maintainer is not on the list, please submit a patch to ReleasingTor.md, or ask them to join tor-packag...@lists.torproject.org. > Roger Dingledine: >> If you run a bridge relay, please upgrade -- so your bridge address can >> resume being given out to censored users, and so your stats can resume >> being included in the metrics pages. >> >> We just put out new releases (0.2.9.16, 0.3.2.11, 0.3.3.9, 0.3.4.5-rc) >> that retire the old bridge authority and start using a new one. The new >> bridge authority is "Serge", and it is operated by George from the Tor >> BSD Diversity project: >> https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html >> >> If for whatever reason you can't upgrade yet, you can also manually >> switch to advertising your bridge descriptor to the new bridge authority >> by using this torrc line: >> >> AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44 >> A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533 > > I'd expect such email to be signed - yes, even if people can fetch that > data from a signed release. Please submit a patch to ReleasingTor.md. T signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge relays should upgrade to use the new bridge authority
you probably want to reach out to package maintainer that didn't update yet (like the ubuntu snap) - if you didn't do so yet Roger Dingledine: > If you run a bridge relay, please upgrade -- so your bridge address can > resume being given out to censored users, and so your stats can resume > being included in the metrics pages. > > We just put out new releases (0.2.9.16, 0.3.2.11, 0.3.3.9, 0.3.4.5-rc) > that retire the old bridge authority and start using a new one. The new > bridge authority is "Serge", and it is operated by George from the Tor > BSD Diversity project: > https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html > > If for whatever reason you can't upgrade yet, you can also manually > switch to advertising your bridge descriptor to the new bridge authority > by using this torrc line: > > AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44 A889 > E64B 93FA A2B1 14E0 2C2A 279A 8555 C533 I'd expect such email to be signed - yes, even if people can fetch that data from a signed release. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Updating relay using killall -hup command
Keifer Bly: > Is there a way I can cause the upgrade to appear without completely > restarting the relay? the answer is easy and short: no -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Updating relay using killall -hup command
On 7/18/18 14:58, Keifer Bly wrote: > Hello, > > > So recently I upgraded from tor 0.3.3.8 to tor 0.3.3.9, and used the > killall -HUP command to restart the relay. However this did nothing, > the relay consensus says I am still running tor 0.3.3.8 days later. Is > there a way I can cause the upgrade to appear without completely > restarting the relay? > > The OS is macos High Sierra 10.13.6. > No. You have to restart the process, thus the relay. (Can you update any other program without restarting it entirely? [If you say the Linux kernel, does your distro actually do it?]) Don't fret about uptime or flags. Updates -- both for Tor and your OS -- are more important. Thanks for running a relay. Matt ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Updating relay using killall -hup command
Hello, So recently I upgraded from tor 0.3.3.8 to tor 0.3.3.9, and used the killall -HUP command to restart the relay. However this did nothing, the relay consensus says I am still running tor 0.3.3.8 days later. Is there a way I can cause the upgrade to appear without completely restarting the relay? The OS is macos High Sierra 10.13.6. Thank you. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
