Re: [tor-relays] how to distribute pgp public key?

2016-12-06 Thread Jason Odoom
On Dec 7, 2016 1:28 AM, "Univibe" wrote: If I want to include a reference to my public PGP key on Atlas using the ContactInfo field on my relays, what's the best way to do it? Should I upload my key to some of the public keyservers and then list the fingerprint on Atlas? Yes. I use the MIT Keys

[tor-relays] how to distribute pgp public key?

2016-12-06 Thread Univibe
If I want to include a reference to my public PGP key on Atlas using the ContactInfo field on my relays, what's the best way to do it? Should I upload my key to some of the public keyservers and then list the fingerprint on Atlas? If so which keyservers are recommended? I had a thought to publi

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread Rana
I can just imagine someone panting while dragging a sub-$35 old desktop computer up the stairs after physically searching for it in a nearby junkyard. A considerable level of destitution and a commendable commitment to the cause of Tor would be required. -Original Message- From: tor-r

Re: [tor-relays] Circuits from Tor relay?

2016-12-06 Thread Rana
That's a thorough and useful answer. Thank you Tim. -Original Message- From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf Of teor Sent: Wednesday, December 07, 2016 12:12 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Circuits from Tor relay? >

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread Roman Mamedov
On Wed, 7 Dec 2016 00:36:15 + Duncan Guthrie wrote: > My original figure may have been... somewhat off. With different models > they may have updated the network hardware. They did not. All models with Ethernet use the same SMSC LAN9514 chip. > A more general point is that old desktop comp

Re: [tor-relays] Call for Tor Fallback Directories

2016-12-06 Thread teor
> On 7 Dec. 2016, at 11:38, Tobias Sachs wrote: > > Hey teor, > > my relay 5665A3904C89E22E971305EE8C1997BCA4123C69 is according to your log > [4] black and whitelisted. But it is only in the whitelist from you [1] > My second relay B567E8E39641F61091C1F2CAAAF73D3D1BF9CFE1 is according to [4]

Re: [tor-relays] Call for Tor Fallback Directories

2016-12-06 Thread Tobias Sachs
Hey teor, my relay 5665A3904C89E22E971305EE8C1997BCA4123C69 is according to your log [4] black and whitelisted. But it is only in the whitelist from you [1] My second relay B567E8E39641F61091C1F2CAAAF73D3D1BF9CFE1 is according to [4] blacklisted but also not in [2]. I hope you can clarify this

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread Duncan Guthrie
On 06/12/16 21:10, SuperSluether wrote: I don't know the actual numbers for the Raspberry Pi 1, I was just quoting from Duncan: https://lists.torproject.org/pipermail/tor-relays/2016-December/011182.html I was told this figure by a friend who tried networking "stuff" on a Pi. From personal ex

Re: [tor-relays] Call for Tor Fallback Directories

2016-12-06 Thread teor
> On 7 Dec. 2016, at 11:04, l3thal.inject...@gmail.com wrote: > > Hey Tim, > > I believe my relay may already be on the fallback list. If not, please > feel free to include it. It has been up, fast and stable for well over > 2 years and will up for the indefinite future at this time. Thanks, I

Re: [tor-relays] Call for Tor Fallback Directories

2016-12-06 Thread l3thal . injecti0n
Hey Tim, I believe my relay may already be on the fallback list. If not, please feel free to include it. It has been up, fast and stable for well over 2 years and will up for the indefinite future at this time. Thanks On Sun, Dec 4, 2016 at 5:44 AM, teor wrote: > -BEGIN PGP SIGNED MESSAGE--

Re: [tor-relays] Circuits from Tor relay?

2016-12-06 Thread teor
> On 7 Dec. 2016, at 08:07, Rana wrote: > > Arm reports that my relay has 15 circuits connected to my (middle only) > relay. Some of the circuits have one middle relay and some of them have two. > All the circuits are FROM my relay to exit nodes, and all have the same guard > (first) relay.

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread Roman Mamedov
On Tue, 6 Dec 2016 22:00:20 +0100 diffusae wrote: > Well, I can read and also now the translation from Bits to Bytes. > But I am not sure about your value of the maximum network capacity. > > That's the iperf3 measurement of a Raspberry Pi 1 Model B+: > > [ ID] Interval Transfer B

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread diffusae
Ahh, ok. It looks like, that should be a bit more that 1 MB/s. Regards, On 06.12.2016 22:10, SuperSluether wrote: > I don't know the actual numbers for the Raspberry Pi 1, I was just > quoting from Duncan: > https://lists.torproject.org/pipermail/tor-relays/2016-December/011182.html > > > On 12

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread SuperSluether
I don't know the actual numbers for the Raspberry Pi 1, I was just quoting from Duncan: https://lists.torproject.org/pipermail/tor-relays/2016-December/011182.html On 12/06/2016 03:00 PM, diffusae wrote: Well, I can read and also now the translation from Bits to Bytes. But I am not sure about

[tor-relays] Circuits from Tor relay?

2016-12-06 Thread Rana
Arm reports that my relay has 15 circuits connected to my (middle only) relay. Some of the circuits have one middle relay and some of them have two. All the circuits are FROM my relay to exit nodes, and all have the same guard (first) relay. My relay has a small number of inbound connections and

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread diffusae
Well, I can read and also now the translation from Bits to Bytes. But I am not sure about your value of the maximum network capacity. That's the iperf3 measurement of a Raspberry Pi 1 Model B+: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 83.6 MBytes 8.36 M

Re: [tor-relays] network diversity with freeBSD - solved

2016-12-06 Thread diffusae
Hi Tim! Thanks a lot for your hint. I've changed it. I'd recognized the public IPs with arm, but didn't know the circumstances. Now it should be in a more secure mode, than before. Regards, On 05.12.2016 23:49, teor wrote: > >> On 6 Dec. 2016, at 08:32, diffusae wrote: >> >> Hi! >> >> On 05.1

Re: [tor-relays] relays with dynamic IP - here Rasp2

2016-12-06 Thread diffusae
Hi! That's from today: rx | tx |total| avg. rate +-+-+--- today 6,26 GiB |5,21 GiB | 11,47 GiB | 1,27 Mbit/s It's just a "low" bandwidth, but this depends on the ISP

Re: [tor-relays] relays with dynamic IP - here Rasp2

2016-12-06 Thread pa011
Am 06.12.2016 um 18:16 schrieb Rana: > -Original Message- > From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf > Of pa011 > Sent: Tuesday, December 06, 2016 1:24 AM > To: tor-relays@lists.torproject.org > Subject: Re: [tor-relays] Unwarranted discrimination of re

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread Tristan
Again, bits or bytes. I can't believe I'm repeating myself, don't you people read? The ORIGINAL (version 1) Raspberry Pi had a max of 1 MegaBYTE. 1 MegaBYTE = 8 megaBITS Obviously other factors limit performance, but looking at just the maximum network capacity of a Raspberry Pi 1, it could hand

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

2016-12-06 Thread Rana
-Original Message- From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf Of pa011 Sent: Tuesday, December 06, 2016 1:24 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP > I would like to hear abou

Re: [tor-relays] Updating wiki - good bad isps

2016-12-06 Thread Sec INT
Same here - i'll submit a ticket Submission rejected as potential spam Content contained these blacklisted patterns: 'http:', '(?i)business' Hopefully they can fix it as I could update quite alot of stuff on there regards Mark B > On 6 Dec 2016, at 10:42, teor wrote: > > >> On 6 Dec. 2

Re: [tor-relays] Updating wiki - good bad isps

2016-12-06 Thread teor
> On 6 Dec. 2016, at 21:40, heartsucker wrote: > > If you attempt to edit the wiki, this error shows up: > > Submission rejected as potential spam > >Content contained these blacklisted patterns: 'http:', > '(?i)(call|customer|technical).?support' > > Since these patters already exist in

Re: [tor-relays] Updating wiki - good bad isps

2016-12-06 Thread heartsucker
If you attempt to edit the wiki, this error shows up: Submission rejected as potential spam Content contained these blacklisted patterns: 'http:', '(?i)(call|customer|technical).?support' Since these patters already exist in the wiki, I can't make updates. -h On 12/06/2016 11:33 AM, teor w

Re: [tor-relays] Updating wiki - good bad isps

2016-12-06 Thread teor
> On 6 Dec. 2016, at 21:15, Sec INT wrote: > > Hi > > Does anyone know a contact for updating the wiki page for good bad isps - im > using five of them and one is not doing what is advertised - i.e. Shutting > off an exit node each time a spam abuse emailer asks them to despite there > being

[tor-relays] Updating wiki - good bad isps

2016-12-06 Thread Sec INT
Hi Does anyone know a contact for updating the wiki page for good bad isps - im using five of them and one is not doing what is advertised - i.e. Shutting off an exit node each time a spam abuse emailer asks them to despite there being little evidence to back up their claims regards Mark B