From owner-freebsd-current Thu Apr 20 2:47:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3DF1E37B945 for ; Thu, 20 Apr 2000 02:47:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA29209 for ; Thu, 20 Apr 2000 02:47:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 20 Apr 2000 02:47:55 -0700 (PDT) From: Kris Kennaway To: current@freebsd.org Subject: HEADS UP: Alpha OpenSSH/OpenSSL breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tracked down what seems to be a bug in the new version of OpenSSL I imported a week ago which affects the alpha platform. It *looks* like a bug in OpenSSL's "bignum" library which might not have shown up for users of the default openssl distribution, which uses assembly to implement (parts of) bignum on alpha. We don't currently use asm on either platform (i386 or alpha) because of a lack of support for a target "CPU revision" (e.g. i[3456]86) during make world. Anyway, the net result of this is that OpenSSH is broken because the RSA operations fail. Possibly the solution is to enable asm code when building for the alpha, but that is going to take a bit of work. In the meantime, I recommend alpha users who make use of openssh or openssl not upgrade their crypto/ and secure/ directories, or revert them to prior to the 13th. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message