From owner-freebsd-stable Tue Jul 4 1:38: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 47FEB37B99E; Tue, 4 Jul 2000 01:38:04 -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 BAA50793; Tue, 4 Jul 2000 01:38:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 4 Jul 2000 01:38:03 -0700 (PDT) From: Kris Kennaway To: Brad Knowles Cc: stable@FreeBSD.ORG Subject: Re: sshd/RSAPrivateDecrypt problems after make world In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Jul 2000, Brad Knowles wrote: > At 10:03 PM -0700 2000/7/3, John Polstra wrote: > > > It has been fixed now. The file in question is back in its original > > collection, and the src-crypto-rsa collection is gone. > > On a related question -- I've got a 4.0-STABLE machine that I > recently cvsup'ed (completed as of Jun 28 17:30). However, I have > this sneaking suspicion I actually cvsup'ed with "cvs tag=." for the > crypto code (although I'm quite certain I used RELENG_4 for the base > source), and wound up with the CURRENT crypto as opposed to the > then-STABLE crypto. Just cvsup it back to RELENG_4. The -current crypto code will probably work fine (the only difference I think is the newer version of OpenSSL which I havent MFC'ed because one or two people were having weird non-reproducable (by me) bugs), but that may change at any moment :-) 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-stable" in the body of the message