From owner-freebsd-security Tue Oct 12 13:52:28 1999 Delivered-To: freebsd-security@freebsd.org Received: from srv1.thuntek.net (srv1.thuntek.net [206.206.98.18]) by hub.freebsd.org (Postfix) with ESMTP id 2546514C32; Tue, 12 Oct 1999 13:52:25 -0700 (PDT) (envelope-from dwilde1@thuntek.net) Received: from thuntek.net (abq-145.thuntek.net [207.66.52.145]) by srv1.thuntek.net (8.9.1/8.6.12TNT1.0) with ESMTP id OAA19192; Tue, 12 Oct 1999 14:52:19 -0600 (MDT) Message-ID: <3803A0F7.DABF362F@thuntek.net> Date: Tue, 12 Oct 1999 14:58:31 -0600 From: Donald Wilde Reply-To: dwilde1@thuntek.net Organization: Wilde Media X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: freebsd-security@freebsd.org Subject: Re: MD5 systems interacting with DES systems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kennaway wrote: > As for encrypted transport, which it sounds like you were talking about, > you want either ssh (if the license restrictions are applicable to you - > or you could port the "last truly free" version which the openbsd guys > have been cleaning up in their tree), or your could go for IPSec (either > in the kernel - see www.kame.net), or userspace (the pipsecd port in > net/). > Thanks for the tips, Kris! From what little I know of IPsec, that would be the ideal anmswer, especially as the systems and their connections multiply. However, for now, knowing that there's an ssh with no restrictions is a !!! Thanks! -- Donald Wilde "Linking Minds and Micros" ================= S i l v e r L y n x =================== PMB 117, 1380 Rio Rancho Blvd SE v: 505-771-0709 f: 771-1356 Rio Rancho, New Mexico 87124 web: http://www.Wilde-Media.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message