From owner-freebsd-security  Tue Nov  2  6:38:21 1999
Delivered-To: freebsd-security@freebsd.org
Received: from india.citi.umich.edu (india.citi.umich.edu [141.211.92.147])
	by hub.freebsd.org (Postfix) with ESMTP id E921A15139
	for <security@freebsd.org>; Tue,  2 Nov 1999 06:38:04 -0800 (PST)
	(envelope-from provos@citi.umich.edu)
Received: from citi.umich.edu (IDENT:provos@india.citi.umich.edu [141.211.92.147])
	by india.citi.umich.edu (8.9.3/8.9.3) with ESMTP id JAA27155;
	Tue, 2 Nov 1999 09:37:47 -0500 (EST)
Message-Id: <199911021437.JAA27155@india.citi.umich.edu>
Subject: Re: OpenSSH patches 
From: Niels Provos <provos@citi.umich.edu>
In-Reply-To: Issei Suzuki, Tue, 02 Nov 1999 06:57:58 +0900
To: Issei Suzuki <issei@issei.org>
Cc: security@freebsd.org
Date: Tue, 02 Nov 1999 09:37:47 -0500
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <19991102065758V.issei@issei.org>, Issei Suzuki writes:
>  It does not seem that OpenSSH source code includes any kind of
>crypto argorythm (they are included in OpenSSL library), but is it
>still affected by US crypto restrictions?
We tried very hard to remove all crypto algorithms from the OpenSSH
sources themselves.  Eseentially only the protocol is left.  OpenSSH
has about 20K lines of source, compared to the 70K in ssh-1.2.27.
This allows for easier code audit, and also easier to touch for people
in the USA.

Greetings,
 Niels.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message