Date: Mon, 3 Mar 2014 15:36:33 -0500 From: John Baldwin <jhb@freebsd.org> To: "Dag-Erling SmXXrgrav" <des@freebsd.org> Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-10@freebsd.org Subject: Re: svn commit: r262566 - in stable/10: crypto/openssh crypto/openssh/contrib/caldera crypto/openssh/contrib/cygwin crypto/openssh/contrib/redhat crypto/openssh/contrib/suse crypto/openssh/openbsd-comp... Message-ID: <201403031536.33679.jhb@freebsd.org> In-Reply-To: <201402271729.s1RHT2rx075258@svn.freebsd.org> References: <201402271729.s1RHT2rx075258@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, February 27, 2014 12:29:02 pm Dag-Erling SmXXrgrav wrote: > Author: des > Date: Thu Feb 27 17:29:02 2014 > New Revision: 262566 > URL: http://svnweb.freebsd.org/changeset/base/262566 > > Log: > MFH (r261320): upgrade openssh to 6.5p1 > MFH (r261340): enable sandboxing by default Mails on stable@ suggest that this latter change may be a bit of a POLA violation as if people are using a custom kernel configuration that doesn't include CAPSICUM they are now locked out of their boxes as sshd fails. It seems that this is at least worth a note in UPDATING if not adding a workaround to handle the case of a kernel without CAPSICUM. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403031536.33679.jhb>