[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #7 from Shawn Webb --- (In reply to Brooks Davis from comment #6) In my case, I'm not trying to use connectat(2). Rather, I'm trying to use connect(2). -- You are receiving this mail because: You

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #6 from Brooks Davis --- Hmm, seems to be some confusion in the implementation. kern_connectat() checks CAP_CONNECT despite a CAP_CONNECTAT existing. SCTP also uses CAP_CONNECT in ways that aren't

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #5 from Shawn Webb --- (In reply to Brooks Davis from comment #4) That's essentially what I'm doing. I'm writing a non-capsicumized child process that handles socket and file descriptor creation in

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 Brooks Davis changed: What|Removed |Added CC|

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #3 from Shawn Webb --- Robert Watson's whitepaper which outlines why connect(2) currently does not support Capsicum can be found here: https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-818.pdf -- You

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #2 from Shawn Webb --- Based on research done by Robert Watson, which isn't referenced anywhere in FreeBSD's official Capsicum documentation, connect(2) isn't ready to be Capsicumized. Note that

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #1 from Shawn Webb --- Fixed in HardenedBSD: https://github.com/HardenedBSD/hardenedBSD/commit/1b1b6b8f1ec1fbbefc5de82f0b15bb470beda370 -- You are receiving this mail because: You are the assignee

[Bug 222632] Enable Capsicum for connect(2)

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 Bug ID: 222632 Summary: Enable Capsicum for connect(2) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects

[Bug 213572] Support for Setting base system build options via dialog

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213572 Roberto Fernandez Cueto changed: What|Removed |Added Attachment #175870|0 |1

[Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222624 Bernhard Froehlich changed: What|Removed |Added Keywords||crash --

[Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222624 Bug ID: 222624 Summary: [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193 Product: Base System Version: 11.1-RELEASE Hardware: amd64

[Bug 222617] kernel panic

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222617 Eugene Grosbein changed: What|Removed |Added Status|New |In Progress

[Bug 222620] [patch] usr.sbin/ppp/auth.c: Incorrect NOPAM section in auth_CheckPasswd

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222620 Bug ID: 222620 Summary: [patch] usr.sbin/ppp/auth.c: Incorrect NOPAM section in auth_CheckPasswd Product: Base System Version: CURRENT Hardware: Any

[Bug 222617] kernel panic

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222617 --- Comment #2 from Andrey --- https://drive.google.com/open?id=0BxciMy2q7ZjTYlg2ZHNOanNfNlE - link for kernel.debug -- You are receiving this mail because: You are the assignee for the bug.

[Bug 222617] kernel panic

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222617 --- Comment #1 from Andrey --- Created attachment 186735 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186735=edit backtrace Added backtrace. -- You are receiving this mail because: You are the assignee

[Bug 222590] hangs when rebooted KVM Guest

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222590 Eugene Grosbein changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org

[Bug 222617] kernel panic

2017-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222617 Bug ID: 222617 Summary: kernel panic Product: Base System Version: 10.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me