From owner-freebsd-security Wed Jan 24 19: 9:52 2001 Delivered-To: freebsd-security@freebsd.org Received: from server1.link-net.com (link-net.com [209.10.61.231]) by hub.freebsd.org (Postfix) with ESMTP id A7BA237B400 for ; Wed, 24 Jan 2001 19:09:33 -0800 (PST) Received: from scott1 (scott1.link-net.com [209.10.61.241]) by server1.link-net.com (Post.Office MTA v3.5.3 release 223 ID# 0-52894U200L100S0V35) with SMTP id com; Wed, 24 Jan 2001 19:09:32 -0800 Reply-To: From: "Scott Raymond" To: "Scott Hilton" , Subject: RE: OpenSSH b0rked (was RE: Problems with IPFW patch) Date: Wed, 24 Jan 2001 19:09:32 -0800 Keywords: FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh, crap. That's EXACTLY what was happening. Looks like it's time for another compile. Duh. -- Scott ======================= Scott Raymond http://soundamerica.com ======================= > -----Original Message----- > From: Scott Hilton [mailto:kupek@earthlink.net] > Sent: Wednesday, January 24, 2001 6:36 PM > To: scott@link-net.com; freebsd-security@freebsd.org > Subject: RE: OpenSSH b0rked (was RE: Problems with IPFW patch) > > > What's wrong with OpenSSH? The only problem I encountered > with it was the > following message when trying to start it: > > fatal: ConnectionsPerPeriod has been deprecated > > > I was looking around for a few minutes, and found the following: > > ================================================================= > = Changes from previous versions = > ================================================================= > > 2.3.0: > We link with OpenSSL 0.9.6 now. > > Diffs from the FreeBSD version are not distributed right > now (but will be). > > ConnectionsPerPeriod is currently not integrated. > Consider using MaxStartups instead. If you still need > ConnectionsPerPeriod, bug me and I may do it. > > > I commented out ConnectionsPerPeriod in /etc/ssh/sshd_config > and sshd loaded > without any problems. > > > > -----Original Message----- > Yeah, now if I could just figure out what was wrong with the openssh > implementation in the core system. Openssh (ports tree > version) has an > annoying install sequence - you can't define where it gets > installed, so > the files get installed to the hard-coded directory tree /usr/local. > The non-working core system one normally installs sshd to > /usr/sbin and > the config files to /etc/ssh. > > What bugs me is that when this gets fixed it's going to take another 4 > hours of compiling and installing. > > Bah. > > -- > Scott > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message