From owner-freebsd-security Mon Jun 3 08:10:42 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22569 for security-outgoing; Mon, 3 Jun 1996 08:10:42 -0700 (PDT) Received: from sea.campus.luth.se (sea.campus.luth.se [130.240.193.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22561 for ; Mon, 3 Jun 1996 08:10:39 -0700 (PDT) Received: (from karpen@localhost) by sea.campus.luth.se (8.6.12/8.6.12) id RAA06749 for freebsd-security@FreeBSD.ORG; Mon, 3 Jun 1996 17:10:51 +0200 Message-Id: <199606031510.RAA06749@sea.campus.luth.se> Subject: Re: MD5 Crack code To: freebsd-security@FreeBSD.ORG Date: Mon, 3 Jun 1996 17:10:50 +0200 (MET DST) From: "Mikael Karpberg" In-Reply-To: from "Johann Visagie" at Jun 3, 96 04:54:19 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello again. > > Why not simply something like SSL which is being developed and used a lot > > just because the WWW is growing with enormous speed? If you have a secure > > link, there is no need for a lot of hassle. You can send anything over the > > socket and it'll be safe. Umm.. No? > > Alternatively, a lot of work is currently being done on and around ssh. > Mostly commercial, though. :-((( The author of ssh wrote to my boss: I know there are at least SSL implementations out there that are free. The specs are free, also. What's "ssh" supposed to stand for and what is it? :-) /Mikael