Date: Tue, 4 Jul 2000 10:02:17 +0200 From: Brad Knowles <blk@skynet.be> To: stable@FreeBSD.ORG, kris@FreeBSD.ORG Cc: stable@FreeBSD.ORG Subject: Re: sshd/RSAPrivateDecrypt problems after make world Message-ID: <v04220801b5874913263d@[195.238.1.121]> In-Reply-To: <200007040503.WAA35597@vashon.polstra.com> References: <Pine.BSF.4.21.0007031454280.50816-100000@freefall.freebsd.org> <200007040503.WAA35597@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. So far, I haven't noticed any big problems with this machine (ssh still works, etc...), but I'm wondering how I might be able to tell if there has been damage that I haven't yet been able to detect, and if I do need to downgrade the crypto source to the now-STABLE versions, just how I'd go about doing that. Thanks! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, <blk@skynet.be> || 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04220801b5874913263d>