Send tor-relays mailing list submissions to
tor-relays@xxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
or, via email, send a message with subject or body 'help' to
tor-relays-request@xxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
tor-relays-owner@xxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of tor-relays digest..."
Today's Topics:
1. Re: tor-relays Digest, Vol 68, Issue 12 (jensm1)
2. Re: BeagleBoard-X15 (jensm1)
3. Re: Useful metrics for relay operators (pa011)
4. Re: tor-relays Digest, Vol 68, Issue 12 (grarpamp)
----------------------------------------------------------------------
Message: 1
Date: Sun, 4 Sep 2016 14:17:12 +0200
From: jensm1 <jensm1@xxxxxxx>
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] tor-relays Digest, Vol 68, Issue 12
Message-ID: <9069332d-2d3a-1a51-83c7-fa851b8842eb@xxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hi Daniel
One thing first: If you want to actively participate on this mailing
list on a regular basis, it would be best if you switched your
mailing-list-setting from digest to the actual mails (you can then
either configure your inbox to put everything containing [tor-relays]
into its own folder, or use a seperate email-address). This way, the
Subject-lines are preserved when you answer, so it's easier to group the
right messages together, automatically.
Regarding relay vs. exit:
Yes, there's a difference. I assume you're familiar with the basic
workings of Tor (otherwise, read
https://www.torproject.org/docs/faq.html.en#Torisdifferent and check out
https://www.eff.org/pages/tor-and-https).
An exit is a special kind of relay, as it is the one where your traffic
leaves the Tor network and gets sent to the actual destination. This
means that the destination sees the exit as the source of this traffic.
So when somebody sends bad or illegal traffic, e.g. a hacker or someone
downloading a movie, it looks like your exit is doing these things.
Depending on the competence of your local law enforcement agencies, this
could mean your computer (or all your computers in your home) might get
seized, and you'll be a suspect.
Therefore, it is not advisable to run an exit from home (since then
you'll get all your computers taken away), or put anything else on the
same server.
Also, lawyers will file abuse complaints against your exit, which you'll
have to deal with.
It's perfectly fine to simply run a "normal" relay (you'll then be the
middle hop), especially if you're running Tor on a system that's not
online 24/7.
Nice to see your relay is running now! Though I must admit that I have
no idea what these "connection speed" notices mean. Probably nothing
important, or they'd be warnings.
Am 04.09.2016 um 06:52 schrieb daniel boone:
> Ok, 1st on to MATT
> "I missed your SOCKS question."
> Well that doesnt matter because I took you advice on the first reply
> you sent explaing things so I commented all again as suggested. So all
> is well now on that part of the torrc file.
> What I did do was kept the ORPort at 9001. I tried 443 but in the
> terminal it showed me it could not bind so it would not work.
> As for the question on "hope this helps" you bet and well appricated.
> Thank you.
> *What I did on the exit on lines 186-190 here is what it is set at*
> *"#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4
> and IPv6 but no more
> #ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well
> as default exit policy
> #ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as
> default exit policy
> #ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as
> default exit policy
> ExitPolicy reject *:0 #no exits allowed: Minus the quotes natrually.
> this line is line 190*
> The links you sent me to look thru was interesting. Per what it says I
> believe port 443 for the ORPort would be best but until I get the bind
> issue I need to learn to do I best leave it set at 9001 for now.
> As for the reading on the relay
> ORPort 443
> Exitpolicy reject *:* <stock in the box>
> Nickname ididnotconfig
> ContactInfo human@...
>
> *{ORPort 9001
> Exitpolicy reject *:* <how i set mine>
> Nickname danielboon
> ContactInfo human@...}*
> *back to line 190 I do have it UNCOMMENTED as you can see.*
> *{ExitPolicy reject *:0 #no exits allowed}*
> *Maybe i can comment line 190, I am not sure but u or Jen will get me
> right.*
> ................................................................................................
> This part is Addressed to Jen
>
> Regarding the exit settings:
> Is this relay running on a computer at your home, Daniel? *<answer is
> yes, my tower with a 64bit linux system duel core>*
>
> Is there other important stuff stored/running on that computer?
> *<basically no important stuff. I do have some stuff but only mount
> the partitons when I need. Think I'm safe on that>*
>
> If the answer to AT LEAST ONE of those two questions is yes, you
> should definitely set
> "ExitRelay 0" and "ExitPolicy reject *:*".
> Actually, you should set this, regardless of the answers, unless you
> know exactly, what it means to run an exit-relay and are willing and
> prepared to do this.
>
> *<what I want to do is run a relay to help fuel the system. So is a
> relay and exit different?>*
> *and to the both of you I too will enjoying working with the group.
> I'm interested in many things at my age. I am self taught on all with
> books and just working with various OS's. Windows has been out for my
> many years once I got to now linux.*
> *As for both if you 2 are good enough to give me your names I can to
> that too. It is David so we can use that.*
>
> I do have a setback here in the terminal I will post it>
>
> *{Sep 03 23:57:39.000 [notice] Bootstrapped 0%: Starting
> Sep 03 23:57:47.000 [notice] Bootstrapped 80%: Connecting to the Tor
> network
> Sep 03 23:57:48.000 [notice] Bootstrapped 85%: Finishing handshake
> with first hop
> Sep 03 23:57:49.000 [notice] Guessed our IP address as 108.79.14.224
> (source: 154.35.175.225).
> Sep 03 23:57:49.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
> Sep 03 23:57:51.000 [notice] Tor has successfully opened a circuit.
> Looks like client functionality is working.
> Sep 03 23:57:51.000 [notice] Bootstrapped 100%: Done
> Sep 03 23:57:51.000 [notice] Now checking whether ORPort
> 108.79.14.224:9001 is reachable... (this may take up to 20 minutes --
> look for log messages indicating success)
> Sep 03 23:59:07.000 [notice] Your network connection speed appears to
> have changed. Resetting timeout to 60s after 18 timeouts and 1000
> buildtimes.
> Sep 04 00:07:45.000 [notice] Your network connection speed appears to
> have changed. Resetting timeout to 60s after 18 timeouts and 100
> buildtimes.
> Sep 04 00:11:48.000 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent. Publishing server descriptor.
> Sep 04 00:11:49.000 [notice] Performing bandwidth self-test...done.*
>
> *{*Sep 04 00:11:56.000 [notice] Your network connection speed appears
> to have changed. Resetting timeout to 60s after 18 timeouts and 104
> buildtimes.}
>
> *<what is going on with that. I did not change anything and I am not
> doing or using anything to set it back. Right with the MB too.}*
>
> I'll check back in the morn. 21 hrs today is enough for my butt. C/Ya
>
> *[snip quote of digest]*
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.torproject.org/pipermail/tor-relays/attachments/20160904/cbb9d604/attachment-0001.html>
------------------------------
Message: 2
Date: Sun, 4 Sep 2016 14:28:15 +0200
From: jensm1 <jensm1@xxxxxxx>
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] BeagleBoard-X15
Message-ID: <5bf7b624-a5b2-6ddb-b9b8-0d0f57bbbe93@xxxxxxx>
Content-Type: text/plain; charset=utf-8
Hi,
the BeagleBoard-X15 seems to be in the last phase of
development/certification. We'll probably have to wait a bit until it
finally gets released.
As to alternatives: I'd be interested in these, too.
Jens
Am 04.09.2016 um 11:05 schrieb jchase:
> Hello,
> At least a year ago someone recommended the BeagleBoard-X15 as a Tor
> relay, partly due to its speed. The X15 does not seem to be available in
> the Netherlands (according to Mouser electronics). Are there any other
> comparable boards available in the Netherlands?
> Thanks,
> James Chase
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
------------------------------
Message: 3
Date: Sun, 4 Sep 2016 14:55:01 +0200
From: pa011 <pa011@xxxxxx>
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] Useful metrics for relay operators
Message-ID: <6831d788-f088-d7b7-4e47-8e2e2e39c1e1@xxxxxx>
Content-Type: text/plain; charset=utf-8
Am 01.09.2016 um 05:39 schrieb teor:
>
>> On 1 Sep 2016, at 13:36, I <beatthebastards@xxxxxxxxx> wrote:
>>
>> Did someone mention t-shirts?
>>
>>
>> When is the last time anyone got a t-shirt?
>
> I'm pretty sure Jon has been sending them out on a regular basis.
> (We're trying to automate the process a bit more.)
>
> If you want one, please feel free to get in touch with him, I've CC'd him on this email.
>
> Tim
>
> Tim Wilson-Brown (teor)
Hi Tim,
if not changed the person in charge should be Juris not Jon - a little bit similar :-)
I would bet nobody got a T-shirt this year - otherwise there wouldn’t be a moaning every now an then, especially from Robert.
I, waiting for a shirt as well, was offering my help on June, 13th in this group - nobody ever came back on that.
Rgds
Paul
------------------------------
Message: 4
Date: Sun, 4 Sep 2016 09:28:27 -0400
From: grarpamp <grarpamp@xxxxxxxxx>
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] tor-relays Digest, Vol 68, Issue 12
Message-ID:
<CAD2Ti2-QrVcZb9jmkwfPQJaEHOoVV52H8_OOwYMtQvifsR88hg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
On Sun, Sep 4, 2016 at 8:17 AM, jensm1 <jensm1@xxxxxxx> wrote:
> you can then configure your inbox to
> put everything containing [tor-relays] into its own folder
This is non ideal as it continues the poor notion that bloating everyone's
subject lines with, currently 13, characters of non content junk is a good idea,
and it will cause mismatches on nonlist material.
The proper way to segregate a list is to match on envelope headers such as
the included X-BeenThere:, List-Id:, Sender:, not meta material in the body.
Unix users can easily use fetchmail and maildrop to do this.
Thunderbird and other clients should be able to.
Webmails are typically junk so no guarantees there.
------------------------------
Subject: Digest Footer
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
------------------------------
End of tor-relays Digest, Vol 68, Issue 14
******************************************