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