Date: Fri, 26 Jan 2001 13:53:21 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Ade Lovett <ade@FreeBSD.ORG> Cc: Kris Kennaway <kris@FreeBSD.ORG>, freebsd-security@FreeBSD.ORG Subject: Re: OpenSSH b0rked (was RE: Problems with IPFW patch) Message-ID: <200101262153.f0QLrLL40016@earth.backplane.com> References: <NDBBJJFIKLHBJCFDIOKGEEKHCAAA.kupek@earthlink.net> <FDEEKLDJMPFBCBKOEEINCEIGCKAA.scott@link-net.com> <20010124230626.A49802@citusc17.usc.edu> <20010125103255.A78404@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:I would ask, that in -STABLE at least, the fatal error be backed :out to a warning, at least for a few months (with sshd ignoring the :directive, and continuing to run), and then only move to a fatal :error + die. : :-aDe : :-- :Ade Lovett, Austin, TX. ade@FreeBSD.org :FreeBSD: The Power to Serve http://www.FreeBSD.org/ I second this request. It also happened when pam.conf/ssh changed. Only the serial console saved me from a car trip to one of my colocated machines. Two such changes in a row for ssh is too much. -Matt 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?200101262153.f0QLrLL40016>