Re: Exposed serial connection

[John Adams <jna-dated-1032604310.732402 () retina net>]

On 16 Sep 2002, Jonas Anden wrote:

> - Encrypting the IP connection (Preferably SSL)
> - Provide for authentication (Preferably outside the protocol sphere,
> like SSL client certificates).
> - Convert the data received on the IP end and send it out on the serial
> line, and vice versa.

I'd think a Linux box running ssh and a captive shell (i.e. ssh to a
restricted rsh, chroot'ed session) would be low-cost and ideal for this 
situation. You can handle all of your authentication issues and such using 
SSL and any additional features can be readily programmed in. Just find a 
PC around the office that noone's using anymore (even a 286 will do for 
this job!) and put it into service. 

There are also many applications that can directly couple an inbound 
session to a serial port that you may want to look into. 

It's simply not worth spending money on proprietary hardware to solve this
problem.

--john

_______________________________________________
firewall-wizards mailing list
firewall-wizards () honor icsalabs com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards