[comp.protocols.tcp-ip] CMU-TEK tcp/ip and 'C'

philipp@quiche.cs.mcgill.ca (Philip PRINDEVILLE) (11/25/88)

Hi.

	I have to locate -- or write myself -- a set of VMS client
utilities for rsh, rcp, rlogin, etc. that run on the CMU-TEK TCP/IP
package.  If anyone has code that does this already *or* information
on binding C calls to BLISS functions (I don't know BLISS), this
would be immensely helpful.

Thanks,

-Philip

Rudy.Nedved@H.GP.CS.CMU.EDU (11/26/88)

There is already a mailing list for discussing CMU Tektronix TCP/IP. The
address is CMU-TEK-TCP@CS.CMU.EDU and to be added to the list you send
mail to CMU-TEK-TCP-REQUEST@CS.CMU.EDU.

You will find that there are alot of little problems that you will encountered
with the very insecure rsh, rlogin and rexec system that Berkeley hacked up.
   - you will be giving your VMS machine more access power to your Unix
     machines (possibly giving any VMS user access to root on your Unix
     machines).
   - you will have to fight with the conflicts from standard TCP/IP not having
     the insecure "priviledged" port concept Berkeley Unix has. Forcing the
     VMS application to allocate a number less then 512 will be tough. Making
     VMS/Unix communication reliable when reusing a port-pair that was just
     used in the last 2 minutes will be tough.
   - mapping Unix semantics to and from VMS semantics for interrupts and
     for terminal i/o will be trickier then telnet...

-Rudy