- tor-relays - lists.torproject.org

don't worry (to much) if your relay is loosing the guard flag
by Nusenu 01 Aug '14

01 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I guess it makes sense to make this change a bit more visible on the tor-relays mailing list since relay ops will notice the change eventually and not everyone is reading changelogs closely. A lot of relays will loose their guard flag (and probably see less traffic?) once enough dir auths [1] upgraded to 0.2.5.6-alpha. For the background see the changelog [2]: >> o Minor features: - Authorities now assign the Guard flag to the >> fastest 25% of the network (it used to be the fastest 50%). Also >> raise the consensus weight that guarantees the Guard flag from >> 250 to 2000. For the current network, this results in about 1100 >> guards, down from 2500. This step paves the way for moving the >> number of entry guards down to 1 (proposal 236) while still >> providing reasonable expected performance for most users. >> Implements ticket 12690. It will be interesting to follow the metrics graphs during that transition. I.e. will the guard bw history go down or will the remaining relays handle the same amount of traffic without any difference? (and similar questions) https://metrics.torproject.org/bandwidth.html#bandwidth-flags [1] https://consensus-health.torproject.org/#authorityversions [2] https://lists.torproject.org/pipermail/tor-talk/2014-July/034180.html -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT2rO6AAoJEDcK3SCCSvoeh4sP/iH6DKlOLtCo1ZoBYKsZx+EJ jir+Lk4urwU+3MeM5Ikbb/XTCXY9Y3RCX8tTG65tn+NoLKNJP/fUGuz8A87Vrc48 ismcoSPrjpgX358VMLy7gO9i1tZGLGDd6qNuh0hLws1Z1JVMBACQKv6ZJrSuaoy6 gM/+htBawyRy8KC9Lsw4C6RZsu8b5Kintn9D6MmcWwVIDY8voB3wyypeZZLWaFzI N9sfyT9M4GC+i2CyWsYNdXB/x6z+IEsq0FE0XMdaLr0W17vh8pef0X3XH06h+MUf GsqK86MkjiYfQ0KfMkA/XfYCA3AWTdMSn63L40cDtLqBEHILlvpY/awWX0G78cnU D6cyhRs/R9rUlzvxMxtEF2mMrhvMAkWhz3JrqoEh0o6eOOF9QsOB700rovNsNufw tCYw/PfDD8PVj/J38jcidxo4VBtLcIrdnSInFuLezyZtvKvlCgzMomu8fOdSLxgf gXmKLY6MzduQFAqgYOg5eu33zMSqiTckC2mWPJXWiJ8m5uRbgw57I+7DjTalB4lD KTBTbtjLf+jbZOYn+E8bmoi8hQFPfhjkMMaqSIXeooqDa2xTbYlmEgPy4VmW5rLf cJd1rM2irw9yMKIYMMcI/aLG5uWZJ5pYAw0zWNA1aBzp33mgJ1yFbdhk9BMA+3/G rqNAV1pSC4brVzn4nF++ =02Sf -----END PGP SIGNATURE-----

1 0

tor daemon problem with obfsproxy
by Fereydoon Sepehri 01 Aug '14

01 Aug '14

Hi All, I install and configure tor to set up a obfs3 bridge. If I use command "tor", everything is fine and clients could connect to server buf if I use "service tor start", the connection will be refused. I checked the log file. the problem is: [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is > 'closed'. Most probably the managed proxy stopped running. This might be a > bug of the managed proxy, a bug of Tor, or a misconfiguration. Please > enable logging on your managed proxy and check the logs for errors. > Jul 31 20:55:56.000 [notice] Failed to terminate process with PID '28836' > ('No such process'). the question is why "tor" command could run the obfsproxy but "service tor start"could not. I change the permission of "obfsproxy" from "root" to "debian-tor" but it did not solve the problem. Best Regards Fereydoon

1 0

Re: [tor-relays] obfsproxy issue
by Mike Patton 01 Aug '14

01 Aug '14

On 01/08/2014 3:00 am, Fereydoon Sepehri <fereydoonsepehri(a)gmail.com> wrote: > > Dear All, > > I want to set up tor Bridge. the bridge is up and working normally. > I decided to use obfsproxy to set up obfs3 bridge. > > I installed Python, python-pip and obfsproxy. > the obfsproxy is in "/usr/bin/" directory. The "obfsproxy which" command did not show this directory but this: > -bash: /usr/local/bin/obfsproxy: No such file or directory > > could you please advise me on this issue. > > Best Regards > Fereydoon As a suggestion, perhaps take the error meager as instructive? Try putting obfsproxy in /use/local/bin instead of /use/bin. M.

2 1

obfsproxy issue
by Fereydoon Sepehri 01 Aug '14

01 Aug '14

Dear All, I want to set up tor Bridge. the bridge is up and working normally. I decided to use obfsproxy to set up obfs3 bridge. I installed Python, python-pip and obfsproxy. the obfsproxy is in "/usr/bin/" directory. The "obfsproxy which" command did not show this directory but this: -bash: /usr/local/bin/obfsproxy: No such file or directory could you please advise me on this issue. Best Regards Fereydoon

1 0

Auto Response
by bbzxrmy wowman 31 Jul '14

31 Jul '14

1 0

how sensitive is relay 'state' file?
by starlight.2014q3＠binnacle.cx 31 Jul '14

31 Jul '14

Can anyone comment on how sensitive the information in the relay 'state' is? In particular, if entry guards are recorded in the file should one be concerned about protecting the file via a) encrypting the file system where it resides b) making a point of not backing up the file I suppose it comes down to how likely it is that an adversary can use entry guard information for correlation attacks against past and present tor-client traffic originating from a targeted client-relay.

1 0

Finding relay Sybils / Groups [re: relay_early/blackhat]
by grarpamp 31 Jul '14

31 Jul '14

As a project then to production development, someone should go back through the entire history of descriptors and look for groups coming online... dates, IP's, contacts, tor/OS versions, nicknames, ISP's, geoip, numbers coming online over sliding timeframes, correlation to 'news events', etc. There may be more questionable relays to be found. We were talking about such influxes around july 4 09, ironically, or not.

2 1

German company Webtropia: Terminated contract without notice because of abuse
by tor＠t-3.net 31 Jul '14

31 Jul '14

You somewhat made a mistake here - you've got to have an exit policy that (minimally) rejects ports 25 and 465, or else your relay becomes a giant abuse tool for spammers, scammers, and phishers instead of what you intended it to be (which was a standard-functioning Tor relay). You might try telling your ISP that you made a mistake in your configuration which allowed spam email to go out, and you're willing to correct that error and move forward. ExitPolicy reject *:25 ExitPolicy reject *:465

4 3

0.2.4.23 availability on trusty armhf?
by trash eighty 31 Jul '14

31 Jul '14

I am running a pretty active relay, using Ubuntu Trusty on armhf. I see 0.2.4.23 for Intel architecture in the repositories, but not on Trusty/armhf. Didn't know if this was an oversight, or if it's still coming down the pipe. Thanks, Trash80

2 1

Re: [tor-relays] German company Webtropia: Terminated contract without notice because of abuse
by tor＠t-3.net 31 Jul '14

31 Jul '14

Let's not confuse two things, here. The customer wanting to host a Tor exit relay is a different service request than wanting to run a wide-open SMTP relay. No reputable ISP would agree to host an open SMTP relay and I'm sure this one did not knowingly do so. It would be unfortunate for ISPs to come under the incorrect impression that hosting Tor is equal to hosting open SMTP. ISPs which might have been Tor-friendly at the outset would do a 180 and unnecessarily adopt a No-Tor service policy. On 07/30/2014 03:39 PM, Lunar wrote: > tor(a)t-3.net: >> You somewhat made a mistake here - you've got to have an exit policy that >> (minimally) rejects ports 25 and 465, or else your relay becomes a giant >> abuse tool for spammers, scammers, and phishers instead of what you intended >> it to be (which was a standard-functioning Tor relay). > > Please don't blame the victim. If this ISP acted differently than what > they initially promised, then they are the problem. >

1 0