Date: Wed, 24 Jan 2001 18:36:14 -0800 From: "Scott Hilton" <kupek@earthlink.net> To: <scott@link-net.com>, <freebsd-security@freebsd.org> Subject: RE: OpenSSH b0rked (was RE: Problems with IPFW patch) Message-ID: <NDBBJJFIKLHBJCFDIOKGEEKHCAAA.kupek@earthlink.net> In-Reply-To: <FDEEKLDJMPFBCBKOEEINMEHPCKAA.scott@link-net.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBJJFIKLHBJCFDIOKGEEKHCAAA.kupek>