Date: Tue, 14 Jun 2016 06:45:52 +0100 From: "Robert N. M. Watson" <rwatson@freebsd.org> To: Joel Dahl <joel@vnode.se> Cc: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, current <current@freebsd.org>, Robert Watson <rwatson@FreeBSD.org> Subject: Re: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode Message-ID: <D260F131-526F-46FC-AD4A-2118E6891309@freebsd.org> In-Reply-To: <20160613110904.GB62543@ymer.vnode.se> References: <20160613105725.GA62543@ymer.vnode.se> <0242AAA6-7BBF-4754-9E06-3EB91CCF8BCF@gmail.com> <20160613110904.GB62543@ymer.vnode.se>
index | next in thread | previous in thread | raw e-mail
On 13 Jun 2016, at 12:09, Joel Dahl <joel@vnode.se> wrote: > >> On Mon, Jun 13, 2016 at 07:00:46AM -0400, Ngie Cooper (yaneurabeya) wrote: >> >>> On Jun 13, 2016, at 06:57, Joel Dahl <joel@vnode.se> wrote: >>> >>> Hi, >>> >>> I've just rebuilt and installed latest current on a machine here. I noticed >>> the following message in dmesg after a reboot: >>> >>> _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode >>> >>> I don't remember seeing this before. >> >> Hi Joe, >> Try reverting r301867. Let Robert know if that fixes your issue. > > Hi, > > This is with r301857. Forgot to mention that in my previous mail. Sorry. I can't see that these are in any way related to the error message. In fact, I saw the same login.conf message (and wondered about it) before committing the BSM fix. This sounds like an sshd or login issue? The former is more likely as I don't think the latter uses sandboxing. Roberthelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D260F131-526F-46FC-AD4A-2118E6891309>