From owner-freebsd-stable Mon Jun 19 4:56:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id EE15C37BCBD for ; Mon, 19 Jun 2000 04:56:45 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id DEB641F4F6; Mon, 19 Jun 2000 13:56:38 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200006191023.MAA22754@rizla.energy.it> References: <200006191023.MAA22754@rizla.energy.it> Date: Mon, 19 Jun 2000 13:54:52 +0200 To: "Alessandro de Manzano" , "stable@freebsd.org" From: Brad Knowles Subject: Re: SSH failed on 4.0-S Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:25 PM +0200 2000/6/19, Alessandro de Manzano wrote: >>> Jun 19 10:48:27 gandalf sshd[438]: fatal: rsa_private_decrypt() failed >> >>This means the key could not be processed for some reason. Are you certain >>you are using an sshd from 4.0-STABLE? The most common cause of this error > > well, I think yes, because I upgraded all via CVSUP using this supfile: Yup. The RSAREF library can't handle keys longer than 1024 bits. If you upgrade with the /usr/ports/security/rsaintl library, that should solve the problem (unless you're in the US, in which case you can't do that for copyright reasons that will require that you continue to use the RSAREF library instead). -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message