I would put some kind of firewall in front of it, If even to restrict source addressed to well known. There is a LOT of people scanning the internet. I also have a publicly available FTP server and I'll see it on lists of known boxes etc.

On March 10, 2017 9:49:45 AM GMT+08:00, John Floren <john@jfloren.net> wrote:
I've now got it working and it made me think a little.

In order to do these "serial ports over TCP" things, we basically are
putting login prompts out to the Internet. Is it possible to restrict
things so the only user allowed on ttyN is 'uucp', or should I just
put in iptables rules to only allow traffic from my UUCP peers?

john

On Wed, Mar 8, 2017 at 2:20 AM, Warren Toomey <wkt@tuhs.org> wrote:
 On Wed, Mar 08, 2017 at 06:43:07AM +1000, Warren Toomey wrote:
 More progress. I now have             mcsun----seismo----munnari
 with uucp mail between them all.

 Even more progress. I wrote a script to generate the uucp systems,
 and given it a rough test. It's now here:

 https://github.com/DoctorWkt/4bsd-uucp

 and ready for people to download and try things out. I'm happy for
 people to make changes, by adding them in as contributors.

 We should add a file with uucp names, owners and connection details.
 I'll do that soon.

 Have at it!
         Warren

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.