<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Yeah, he knows, he'd just kind of like it to go away.<br>
<br>
A bit of googling yielded something called tortunnel which links
direct to the exit node and allows a scan. It'd be nice to make a
bit of an effort though, so, anyone know how to interfere with that?
It's Moxie, mind you, so it's probably bulletproof.<br>
<br>
K.<br>
<br>
<div class="moz-cite-prefix">On 21/05/16 21:46, Green Dream wrote:<br>
</div>
<blockquote
cite="mid:CAAd2PDJp=niFW4LrSThn93Pj=ySj9fmvVnN3JQxNrBAi9A984w@mail.gmail.com"
type="cite">
<div dir="ltr">There's really nothing to do. Based on the limited
logs, it looks like someone was just looking for open TCP port
22 (ssh). You can't really block the scans by source since you
don't know the source address (because Tor). You could prevent
connections to port 22, but that would prevent everyone else
from using ssh through your exit, and also, it wouldn't stop
port scanning of any other ports allowed through the exit.
<div><br>
</div>
<div>I'd just explain you're running a Tor exit, and thus you
cannot identify the source of the scan.</div>
<div><br>
</div>
<div>As common as port scanning is (and has been for as long as
the Internet has been around), I'm surprised providers still
worry about it this much.</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tor-relays mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
</blockquote>
<br>
</body>
</html>