From mboxrd@z Thu Jan 1 00:00:00 1970 From: wkt@tuhs.org (Warren Toomey) Date: Fri, 10 Mar 2017 12:06:35 +1000 Subject: [TUHS] UUCP: working systems, come and get them In-Reply-To: References: <20170307070941.GA2012@minnie.tuhs.org> <20170307090908.GA9793@minnie.tuhs.org> <20170307204307.GA23160@minnie.tuhs.org> <20170308092052.GA13593@minnie.tuhs.org> Message-ID: <20170310020635.GB14221@minnie.tuhs.org> On Thu, Mar 09, 2017 at 06:49:45PM -0700, John Floren 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? Yes, I'm trying to work on that. There is a way set some DZ lines to listen on port Y and the others on port X. sim> ATTACH DZ X,Line=3,Y,line=4,Z But there isn't a way to bind to localhost AFAICT. So we should be able to run uucico only on certain /dev/tty lines, but this still will require you to iptables block the other port. Unless someone has a way to bind simh DZ lines to localhost? Cheers, Warren -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: