From owner-freebsd-security Mon Apr 1 10:48:36 2002 Delivered-To: freebsd-security@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5A14A37B405 for ; Mon, 1 Apr 2002 10:48:21 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.6) id g31ImGv55875; Mon, 1 Apr 2002 13:48:16 -0500 (EST) (envelope-from wollman) Date: Mon, 1 Apr 2002 13:48:16 -0500 (EST) From: Garrett Wollman Message-Id: <200204011848.g31ImGv55875@khavrinen.lcs.mit.edu> To: Dag-Erling Smorgrav Cc: freebsd-security@FreeBSD.ORG Subject: Re: It's time for those 2048-, 3072-, and 4096-bit keys? In-Reply-To: References: <5.0.2.1.1.20020326024955.02392830@popserver.sfu.ca> <20020326034234.Q10197-100000@patrocles.silby.com> <20020326185714.F22539@mail.webmonster.de> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Some systems (like the SparcStation 5 that serves DNS, DHCP and NTP > requests from my home network) are too slow for the algorithms used by > ssh2. It's perfectly acceptable on our IPX. The session takes a few seconds to start, and the keys took a long time to generate, but once authenticated there does not seem to be much difference to me. (In fact, `cat /etc/termcap' takes consistently twice as long using v1 as v2.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message