Re: "_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode"
On Mon, Jun 20, 2016 at 04:42:39AM -0700, David Wolfskill wrote: > After updating my (amd64) build machine from r302018 to r302026, things > work OK, but (now that I've re-connected the serial cable so I can > actually interact with the serial console -- i.e., this may have > occurred a while back, but I wouldn't have noticed), I see: > > ... > Starting devd. > add host 127.0.0.1: gateway lo0 fib 0: route already in table > add net default: gateway 172.16.8.1 > add > FreeBSD/amd64 (freebeast.catwhisker.org) (ttyu0) > > login: Jun 20 11:34:16 freebeast sshd[736]: _secure_path: cannot stat > /etc/login.conf: Not permitted in capability mode > Jun 20 11:34:16 freebeast last message repeated 2 times > Jun 20 11:34:21 freebeast sshd[810]: _secure_path: cannot stat > /etc/login.conf: Not permitted in capability mode > Jun 20 11:34:21 freebeast last message repeated 2 times > Jun 20 11:34:25 freebeast sshd[882]: _secure_path: cannot stat > /etc/login.conf: Not permitted in capability mode Yes, me too. I reported this a few days ago here on current@. -- Joel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
"_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode"
After updating my (amd64) build machine from r302018 to r302026, things work OK, but (now that I've re-connected the serial cable so I can actually interact with the serial console -- i.e., this may have occurred a while back, but I wouldn't have noticed), I see: ... Starting devd. add host 127.0.0.1: gateway lo0 fib 0: route already in table add net default: gateway 172.16.8.1 add FreeBSD/amd64 (freebeast.catwhisker.org) (ttyu0) login: Jun 20 11:34:16 freebeast sshd[736]: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode Jun 20 11:34:16 freebeast last message repeated 2 times Jun 20 11:34:21 freebeast sshd[810]: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode Jun 20 11:34:21 freebeast last message repeated 2 times Jun 20 11:34:25 freebeast sshd[882]: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode on the serial console. Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
On 13 Jun 2016, at 12:09, Joel Dahl <j...@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 <j...@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. Robert ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
On Mon, Jun 13, 2016 at 07:00:46AM -0400, Ngie Cooper (yaneurabeya) wrote: > > > On Jun 13, 2016, at 06:57, Joel Dahl <j...@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. -- Joel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
> On Jun 13, 2016, at 06:57, Joel Dahl <j...@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. Thanks! -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
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. -- Joel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
