[TUHS] UUCP: working systems, come and get them

[TUHS] UUCP: working systems, come and get them

[Noel Chiappa]

    > From: Warren Toomey

    > attach dz line=0,Connect=simh.tuhs.org:5000
    >
    >  which will connect /dev/tty00

Provided that /dev/tty00 exists, and the major device type is set to the
cdevsw index for the DZ in whatever Unix you are using, and the minor device
is set to the correct value to DZ #0, line #0.... :-)

	Noel

[TUHS] Help request: uucp, mail on 4.2BSD

[Warren Toomey]

Hi all, as part of my effort to recreate part of a simulated Usenet,
I'm trying to bring up uucp, then mail, then C-news on 4.2BSD boxes.
I've got a hardwired serial port between them, and I can see a basic
uucp conversation when I do this:

munnari.oz# /usr/lib/uucp/uucico -r1 -sseismo -x7
uucp seismo (3/6-8:04-132) DEBUG (ENABLED)
	. . .
uucp seismo (3/6-8:04-132) SUCCEEDED (call to seismo )
imsg >\015\012\020<
Shere\000imsg >\020<
ROK\000msg-ROK
 Rmtname seismo, Role MASTER,  Ifn - 5, Loginuser - uucp
	. . .

I tried e-mail to seismo!wkt and wkt at seismo.UUCP but it's been deferred.
I now need some help with the sendmail config. I did play around with
sendmail.cf/mc way back, but it never involved uucp so I'm stuck.

Anybody want to help (and dust out those cobwebs at the same time)?

Thanks, Warren 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170307/bf296513/attachment.sig>

[TUHS] Help request: uucp, mail on 4.2BSD

[Warren Toomey]

On Tue, Mar 07, 2017 at 05:09:41PM +1000, Warren Toomey wrote:
> I tried e-mail to seismo!wkt and wkt at seismo.UUCP but it's been deferred.
> I now need some help with the sendmail config. I did play around with
> sendmail.cf/mc way back, but it never involved uucp so I'm stuck.

Progress. I had to set up L.sys entries for each system to know the other
system. Then on each 4.2BSD system I had to uucp "make mkdirs" to make the
correct directories in /usr/spool/uucp.

On the sendmail front, I edited the uucp-only cad.mc file to state the system
name and the other system name (and in reverse for the other system). Then
make cad.cf.

With all of this in place, I can mail from one system to the other:
$ echo hello | mail wkt at seismo.UUCP

and then manually do a uucp call with # /usr/lib/uucp/uucico -r1 -sseismo -x7

There are a few things to iron out, but at least thing work :)
	Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170307/cf49015b/attachment.sig>

[TUHS] Help request: uucp, mail on 4.2BSD

[Warren Toomey]

On Tue, Mar 07, 2017 at 07:09:08PM +1000, Warren Toomey wrote:
> Progress.

More progress. I now have    		mcsun----seismo----munnari
with uucp mail between them all.

It should be easy to generate systems and their connections from a template.
I'll write the scripts soon. I might call for participation in a uucp/Usenet
reconstruction with people running simulated nodes on the Internet.

Mail me your "dibs" for specific nodes. Who wants kremvax?  :-)

Cheers, Warren

P.S A/B/C-news  at http://www.tuhs.org/Archive/Applications/News/
    Taylor UUCP at http://www.tuhs.org/Archive/Applications/TaylorUUCP/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170308/1d941445/attachment.sig>

[TUHS] UUCP: working systems, come and get them

[Warren Toomey]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170308/7eeeb90e/attachment-0001.sig>

[TUHS] UUCP: working systems, come and get them

[Warren Toomey]

On Wed, Mar 08, 2017 at 07:20:52PM +1000, Warren Toomey wrote:
> https://github.com/DoctorWkt/4bsd-uucp

The list of people and sites they have chosen is at 
https://github.com/DoctorWkt/4bsd-uucp/blob/master/uucp_sites.txt

I've just set up "seismo" at simh.tuhs.org:5000, if anybody wants a
remote site to connect to. E-mail me your site and IP details.

Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170309/a8db34df/attachment.sig>

[TUHS] UUCP: working systems, come and get them

[Dave Horsfall]

I'm surprised no-one's taken decvax, ihnp4, cbosgd...

...!utzoo!dave[.UUCP] one day...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."

[TUHS] UUCP: working systems, come and get them

[Mary Ann Horton]

Please save cbosgd for me.  It may be awhile before I get around to 
doing anything with it.

There was never a cbosgd!mah, but now I have a shot at it :)

   Mary Ann

On 2017-03-08 14:31, Dave Horsfall wrote:
> I'm surprised no-one's taken decvax, ihnp4, cbosgd...
> 
> ...!utzoo!dave[.UUCP] one day...

[TUHS] UUCP: working systems, come and get them

[Kurt H Maier]

On Thu, Mar 09, 2017 at 08:16:45AM +1000, Warren Toomey wrote:
> 
> The list of people and sites they have chosen is at 
> https://github.com/DoctorWkt/4bsd-uucp/blob/master/uucp_sites.txt

I don't see kremvax listed.  If nobody else will, I'll operate a kremvax
installation.

khm

[TUHS] UUCP: working systems, come and get them

[arnold]

Kurt H Maier <khm at sciops.net> wrote:

> On Thu, Mar 09, 2017 at 08:16:45AM +1000, Warren Toomey wrote:
> > 
> > The list of people and sites they have chosen is at 
> > https://github.com/DoctorWkt/4bsd-uucp/blob/master/uucp_sites.txt
>
> I don't see kremvax listed.  If nobody else will, I'll operate a kremvax
> installation.
>
> khm

Ahem - my name is Arnold Robbins - my domain is "Skeeve" ... :-)

Please fix the file. 

Arnold

[TUHS] UUCP: working systems, come and get them

[Lars Brinkhoff]

Warren Toomey <wkt at tuhs.org> writes:
> The list of people and sites they have chosen is at 
> https://github.com/DoctorWkt/4bsd-uucp/blob/master/uucp_sites.txt
>
> I've just set up "seismo" at simh.tuhs.org:5000, if anybody wants a
> remote site to connect to. E-mail me your site and IP details.

I'd like to join this network, but I don't know how to configure a UUCP
site.  I'm using Taylor UUCP 1.07.  I can probably figure things out
eventually but if someone has any hints, that would be helpful.

I'm looking to use TCP and protocol T, but I don't know if that's
appropriate.

[TUHS] UUCP: working systems, come and get them

[Warren Toomey]

On Thu, Mar 09, 2017 at 01:57:05PM +0100, Lars Brinkhoff wrote:
> Is it ok to do experimental testing with that host?  I've never set up
> uucp, so I do not yet know quit what I'm doing.

Neither have I! But yes, feel free. In yur SimH .ini file, put (or change)
this line to say:

attach dz line=0,Connect=simh.tuhs.org:5000

which will connect /dev/tty00 to simh.tuhs.org port 5000. Then
set up your L.sys file with a line that says:

seismo Any;9 DIR 9600 tty00 "" "" ogin:--ogin:--ogin: uucp ssword: uucp

so that the uucp site seismo can be contacted via /dev/tty00. Then you
can try doing:

# echo hello there | mail seismo\!root
  <wait a few seconds>
# /usr/lib/uucp/uucico -r1 -sseismo -x7

and you should see the debug information with parts of the uucp conversation.

Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170310/21cc1a0f/attachment.sig>

[TUHS] UUCP: working systems, come and get them

[Lars Brinkhoff]

Warren Toomey wrote:
> Lars Brinkhoff wrote:
>> Is it ok to do experimental testing with that host?  I've never set
>> up uucp, so I do not yet know quit what I'm doing.
> Neither have I! But yes, feel free. In yur SimH .ini file, put (or change)
> this line to say

I'm using Taylor UUCP on a somewhat modern system (Ubuntu 12).

I managed persuade it to connect to seismo over TCP port 5000 and do a
handshake for protocol g.  A few packets were sent.

Now I'll see if I can inject email messages into this.  We're using the
exim MTA, and it's does exactly support uucp.

[TUHS] UUCP: working systems, come and get them

[Warren Toomey]

On Thu, Mar 09, 2017 at 04:01:09PM -0700, John Floren wrote:
> Well, I'm trying to set up lanl-a, it's at 199.180.255.235:6666
> (theoretically). I've set it up to point at seismo but uucico hangs
> waiting for the login prompt.

OK, try this: Edit your /etc/remote file to say this for dialer:

dialer:dv=/dev/tty00:br#9600:

Now try:

# tip dialer

which should connect out over /dev/tty00 to seismo via the TCP connection.
Hit Return a few times to see if there is any response. On your host system,
do netstat -a | grep ESTAB and see if there is a TCP connection to
simh.tuhs.org:5000.

I also forgot. To be able to send e-mail, you need to add seismo to the
list of known remote sites in /usr/lib/sendmail.cf:

CWseismo

Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170310/2baf98b5/attachment.sig>

[TUHS] UUCP: working systems, come and get them

[John Floren]

No luck with tip, and I don't see any net connections. My .ini file
contains this:

set dz lines=8
set dz 8b
attach dz line=0,Connect=simh.tuhs.org:5000
att dz -m 6666

and I can 'telnet simh.tuhs.org 5000' from the host.

john

On Thu, Mar 9, 2017 at 4:19 PM, Warren Toomey <wkt at tuhs.org> wrote:
> On Thu, Mar 09, 2017 at 04:01:09PM -0700, John Floren wrote:
>> Well, I'm trying to set up lanl-a, it's at 199.180.255.235:6666
>> (theoretically). I've set it up to point at seismo but uucico hangs
>> waiting for the login prompt.
>
> OK, try this: Edit your /etc/remote file to say this for dialer:
>
> dialer:dv=/dev/tty00:br#9600:
>
> Now try:
>
> # tip dialer
>
> which should connect out over /dev/tty00 to seismo via the TCP connection.
> Hit Return a few times to see if there is any response. On your host system,
> do netstat -a | grep ESTAB and see if there is a TCP connection to
> simh.tuhs.org:5000.
>
> I also forgot. To be able to send e-mail, you need to add seismo to the
> list of known remote sites in /usr/lib/sendmail.cf:
>
> CWseismo
>
> Cheers, Warren

[TUHS] UUCP: working systems, come and get them

[Cory Smelosky]

On Thu, Mar 9, 2017, at 15:19, Warren Toomey wrote:
> On Thu, Mar 09, 2017 at 04:01:09PM -0700, John Floren wrote:
> > Well, I'm trying to set up lanl-a, it's at 199.180.255.235:6666
> > (theoretically). I've set it up to point at seismo but uucico hangs
> > waiting for the login prompt.
> 
> OK, try this: Edit your /etc/remote file to say this for dialer:
> 
> dialer:dv=/dev/tty00:br#9600:
> 
> Now try:
> 
> # tip dialer
> 
> which should connect out over /dev/tty00 to seismo via the TCP
> connection.
> Hit Return a few times to see if there is any response. On your host
> system,
> do netstat -a | grep ESTAB and see if there is a TCP connection to
> simh.tuhs.org:5000.
> 
> I also forgot. To be able to send e-mail, you need to add seismo to the
> list of known remote sites in /usr/lib/sendmail.cf:
> 
> CWseismo
> 
> Cheers, Warren
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

I'm trying to do an identical test before bring UUCP up. (but using
4._3_BSD).

# grep -i "tty00" /etc/ttys
#tty00   "/etc/getty std.9600"   unknown         on secure

# tip dialer
/dev/tty00: Permission denied
link down
# grep -i "dialer" /etc/remote
dialer:dv=/dev/tty00:br#9600:

sim> show dz0
DZ0     attached to 5000,Line=0,Connect=simh.tuhs.org:5000, 8b, 1
current connection

# cat /dev/tty00

Connected to the VAX 11/780 simulator DZ device, line 5


Password:
Connected to tLogin incorrect
login: he VAX 11/780 simulator DZ device, line 5
Password:


Password:

Login incorrect
Cologin: login: login: Password:
login: he VAX 1Login incorrect
login: 1/780 simulator DZ device, line 5
Password:
assword:

What'd I miss?

-- 
  Cory Smelosky
  b4 at gewt.net

[TUHS] UUCP: working systems, come and get them

[Cory Smelosky]

On Thu, Mar 9, 2017, at 18:02, Warren Toomey wrote:
> On Thu, Mar 09, 2017 at 05:57:00PM -0800, Cory Smelosky wrote:
> > # grep -i "tty00" /etc/ttys
> > #tty00   "/etc/getty std.9600"   unknown         on secure
> > 
> > # tip dialer
> > /dev/tty00: Permission denied
> 
> You need to chown uucp /dev/tty00 I think!
> 
> Cheers, Warren
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

That did it.

-- 
  Cory Smelosky
  b4 at gewt.net

[TUHS] UUCP: working systems, come and get them

[John Floren]

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 at 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

[TUHS] UUCP: working systems, come and get them

[Warren Toomey]

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: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170310/fcdb3a1b/attachment.sig>

[TUHS] UUCP: working systems, come and get them

[Cory Smelosky]

On Thu, Mar 9, 2017, at 18:06, Warren Toomey wrote:
> 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?

sim> att dz -m 127.0.0.1:5000
Listening on port 127.0.0.1:5000
Modem control activated

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.


Connected to the VAX 11/780 simulator DZ device, line 1

[root at lethe] ~# telnet 10.12.10.1 5000
Trying 10.12.10.1...
telnet: connect to address 10.12.10.1: Connection refused
telnet: Unable to connect to remote host

> 
> Cheers, Warren
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)


-- 
  Cory Smelosky
  b4 at gewt.net

[TUHS] UUCP: working systems, come and get them

[Jason Stevens]

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 at 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 at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170310/4dd5ba59/attachment-0002.html>

[TUHS] UUCP: working systems, come and get them

[John Floren]

On Fri, Mar 10, 2017 at 5:25 AM, Jason Stevens
<jsteve at superglobalmegacorp.com> wrote:
> 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.
>

That's the plan. I now have lanl-a and unmvax up and talking to each
other. If anyone would like to set up a bi-directional connection with
lanl-a, contact me off-list and I'll put you in my firewall / add a
serial connection to you. I'll try to get C-News going soon too.

john

[TUHS] UUCP: working systems, come and get them

[Warren Toomey]

On Fri, Mar 10, 2017 at 08:25:25PM +0800, Jason Stevens 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

Use the 4.3BSD branch. In these systems, I've set the serial ports
as insecure in /etc/ttys, so people can't login as root. Then, remove
all users from the password file (with vipw) except root and uucp. Or,
keep one non-root user for you to login as.

If you leave vax780 running in 'screen', you can still login as root there.

Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170311/1dc7f544/attachment.sig>