<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Block ports that spread worm(like) virii would also mean closing ports 80 and 443. I am afraid that is no option<br><br>the white rider<div><p style="margin: 0px; font-size: 12px; font-family: Helvetica;"><span style="font-size: 12pt;">(Het leuke van ... is </span></p></div></div><div><br><div><br><br>the white rider<div><p style="margin: 0px; font-size: 12px; font-family: Helvetica;"><span style="font-size: 12pt;">(Het leuke van ... is </span></p></div></div>On 18 aug. 2016, at 01:30, teor <<a href="mailto:teor2345@gmail.com">teor2345@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span></span><br><blockquote type="cite"><span>On 18 Aug 2016, at 08:23, majacobs <<a href="mailto:tor@tent.xs4all.nl">tor@tent.xs4all.nl</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Cut off three times because of worm spread alert. I ran an exit node for just a couple of weeks. First came in while i was away on holiday . Could not connect to my vpn but noticed that one of my consumer routers send a reboot message around the first day of my vacation and didn't think about it again , that is till I got home and really started to run the node . Node 0d0a was running fine and well when the net was cut of for a second time just a few days before the third and last time. I contacted support , sought advice I was told to better run a relay.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>No way! I thought!</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>To cut a story short, I know run in bridged mode (obsfs4proxy) but I am looking for solutions as to how Tor can help not seeing exit-nodes coming and going because of worm spreading?</span><br></blockquote></blockquote></blockquote><span></span><br><span>Tor doesn't discriminate based on traffic, so this is a hard problem.</span><br><span></span><br><span>Over the long term, encourage destinations (or server providers) to block particular problematic traffic, rather than entire IP addresses or servers.</span><br><span></span><br><span>Over the short term, block the ports that the worm uses to spread.</span><br><span></span><br><span>Tim</span><br><span></span><br><span>Tim Wilson-Brown (teor)</span><br><span></span><br><span>teor2345 at gmail dot com</span><br><span>PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B</span><br><span>ricochet:ekmygaiu4rzgsk6n</span><br><span>xmpp: teor at torproject dot org</span><br><span></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span></span><br></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>tor-relays mailing list</span><br><span><a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a></span><br><span><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a></span><br></div></blockquote></div></body></html>