<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 19, 2017, at 8:55 PM, teor <<a href="mailto:teor2345@gmail.com" class="">teor2345@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><br class=""><div class="">On 20 Dec 2017, at 13:28, Conrad Rockenhaus <<a href="mailto:conrad@rockenhaus.com" class="">conrad@rockenhaus.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><span class="">Howdy,</span><br class=""><span class=""></span><br class=""><span class="">Early this morning (3 AM CST) I brought a non-exit relay named “ConradsAWSRelay” online. I would appreciate it if someone would take an objective look at it to see if the relay is fast enough and bringing useful services to the tor network.</span><br class=""></div></blockquote><div class=""><br class=""></div><div class="">Please upgrade your relay to the latest Tor version:</div><div class=""><a href="https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html" class="">https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html</a></div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>I noticed this when I started it up. It appears that the version of Tor on EPEL is out of date. I’ll build it out of source to fix it. I’ll probably have to do that for the Cloud solution as well since the lifecycle of EPEL is normally behind. I’ll fix this now.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class="">Your relay might take a few weeks to be used:</div><div class=""><a href="https://blog.torproject.org/lifecycle-new-relay" class="">https://blog.torproject.org/lifecycle-new-relay</a></div></div></div></blockquote><div><br class=""></div><div>I completely forgot about that. Thank you for reminding me :D.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><br class=""><blockquote type="cite" class=""><div class=""><span class="">Additionally, I know that people have been working on ansible solutions regarding the installation of tor and what not, but that being said, I’m working on an AWS specific solution to replace the previous Cloud torproject that we had years ago. I will keep everyone in the loop, but I think its time that we have a cloud specific solution for rolling out tor.</span><br class=""></div></blockquote><br class=""><div class="">Thanks!</div><div class="">It would be great to have this again.</div></div></div></blockquote><div><br class=""></div><div>I’m making progress and will advise all when I hit certain points so I can get feedback. I would like this new solution to have significant community input so I have all of my i’s dotted and my t’s crossed.</div><div><br class=""></div><div>Thanks,</div><div><br class=""></div><div>Conrad</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class=""><br class=""></div><div class="">T</div></div>_______________________________________________<br class="">tor-relays mailing list<br class=""><a href="mailto:tor-relays@lists.torproject.org" class="">tor-relays@lists.torproject.org</a><br class="">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br class=""></div></blockquote></div><br class=""></body></html>