From owner-freebsd-security  Fri Nov 24 09:22:11 1995
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id JAA08060
          for security-outgoing; Fri, 24 Nov 1995 09:22:11 -0800
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA08055
          for <security@FreeBSD.ORG>; Fri, 24 Nov 1995 09:22:03 -0800
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id JAA02513; Fri, 24 Nov 1995 09:19:16 -0800
To: Randy Berndt <rberndt@nething.com>
cc: security@FreeBSD.ORG
Subject: Re: I wonder how much trouble something like this would be to do? :) 
In-reply-to: Your message of "Fri, 24 Nov 1995 10:44:06 CST."
             <199511241644.KAA26846@kilgour.nething.com> 
Date: Fri, 24 Nov 1995 09:19:16 -0800
Message-ID: <2511.817233556@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-security@FreeBSD.ORG
Precedence: bulk

> Wow, only $3,600 for the PC version. I wonder if Dec has looked on 
> the ftp site: ftp.cs.hut.fi:/pub/ssh for the ssh program, that does
> much the same thing for telnet, rlogin type stuff for FREE.

Yeah, but ssh is different.  The DEC folks are encrypting *all*
traffic between the networks, not just those clients that support end
to end crypto.

Yes, you and I may know that doing it one layer up is architecturally
superior, but to the MIS manager who reads DEC's solution as "one big
hammer" he won't have to worry too much about, well, the solution
he'll pick will be obvious.

					Jordan