[Bugzilla] Commit Needs MFC
Hi, You have a bug in the Needs MFC state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by ead...@freebsd.org. (10 bugs) Bug 57630: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=57630 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: lptcontrol(8) gives device busy if device turned off Bug 123977: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=123977 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: Segmentation fault in dialog(1) with ghostscript-gpl-nox11 port Bug 155028: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155028 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: init(8): init q in single user causes segfault Bug 156481: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156481 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [kernel] [patch] kernel incorrectly reports PPS jitter with accurate measurements Bug 165630: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165630 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [ndis][panic][patch] IRQL_NOT_GREATER_THAN Bug 167133: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167133 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: stale files in /usr/share/examples Bug 169471: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169471 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] pw(8) deletes group username on userdel even if group username is not assoc. w/user username Bug 171779: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171779 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] passwd(1): make option NO_FSCHG incomplete Bug 184507: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184507 Severity: Affects Some People Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] [libfetch] allow hiding User-Agent with empty string Bug 184681: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184681 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: A bug of bsdconfig(8) in 10.0 RC1 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 191080] New: Unable to add serial device using conscontrol(8)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191080 Bug ID: 191080 Summary: Unable to add serial device using conscontrol(8) Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: sh...@freebsd.org I'm trying to dynamically add a uart console device (/dev/ttyu0) to the low-level console list per conscontrol(8), but always get an ENXIO error: root@wasp:~ # conscontrol add /dev/ttyu0 conscontrol: could not add ttyu0 as a console: Device not configured I've tried it with getty running and not running, as well as with a terminal connected and not connected with the same results in all cases. root@wasp:~ # uname -a FreeBSD wasp 11.0-CURRENT FreeBSD 11.0-CURRENT #14: Mon Jun 16 01:01:23 PDT 2014 admin@wasp:/usr/obj/usr/src/sys/GENERIC amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 121073] [kernel] [patch] run chroot as an unprivileged user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=121073 Robert Watson rwat...@freebsd.org changed: What|Removed |Added CC||rwat...@freebsd.org --- Comment #8 from Robert Watson rwat...@freebsd.org --- A appreciate the desirability for the features implied by this change, but given the propensity for vulnerabilities relating to chroot() in the past, think we should take a very conservative approach to potentially adopting it. There's a particular concern with how it interacts with non-UNIX-ID-based models -- e.g., MAC, Capsicum, Audit, Jail, as well as a future fine-grained privilege model. Overall, I'd rate this proposed change as extremely high risk; we will fix multiple vulnerabilities in it in the future, and so that cost would need to be carefully weighed against presumed benefit -- a fine-grained privilege model in which PRIV_CHROOT is delegable to only specific users or roles would help mitigate that risk. I wonder if a more suitable name for the proposed P_NOSUGID would be P_NOCREDCHANGE, and I also wonder if it should be CR_NOCREDCHANGE. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 191086] New: grep and bsdgrep do not recognize [[::]] and [[::]]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191086 Bug ID: 191086 Summary: grep and bsdgrep do not recognize [[::]] and [[::]] Product: Base System Version: 9.2-RELEASE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: we...@iastate.edu grep and bsdgrep do not recognize the '[[::]]' or '[[::]]' bracket expressions described in re_format(7), though sed does: $ printf 'foobar\nfoo bar\nbaz' | grep 'foo[[::]]' grep: Invalid character class name $ printf 'foobar\nfoo bar\nbaz' | grep '[[::]]bar' grep: Invalid character class name $ printf 'foobar\nfoo bar\nbaz' | bsdgrep 'foo[[::]]' bsdgrep: Invalid character class name $ printf 'foobar\nfoo bar\nbaz' | bsdgrep '[[::]]bar' bsdgrep: Invalid character class name $ printf 'foobar\nfoo bar\nbaz' | sed -n '/foo[[::]]/p' foo bar $ printf 'foobar\nfoo bar\nbaz' | sed -n '/[[::]]bar/p' foo bar -- Nathan Weeks IT Specialist USDA-ARS Corn Insects and Crop Genetics Research Unit Crop Genome Informatics Laboratory Iowa State University http://weeks.public.iastate.edu/ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 176250] [libc] [patch] euc locale input modifies data
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176250 David Chisnall thera...@freebsd.org changed: What|Removed |Added CC||thera...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|thera...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 179721] [libc] [patch] char-wchar_t mismatch in glob(3), fnmatch(3), regexec(3)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=179721 David Chisnall thera...@freebsd.org changed: What|Removed |Added CC||thera...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|thera...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 182170] strtofflags.c build failures
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182170 David Chisnall thera...@freebsd.org changed: What|Removed |Added Assignee|thera...@freebsd.org|freebsd-bugs@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 121073] [kernel] [patch] run chroot as an unprivileged user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=121073 --- Comment #9 from Nathan Whitehorn nwhiteh...@freebsd.org --- There are, I think, two potential security issues here: 1. Many pieces of software assume that if you chroot and drop privileges, no further chroot is possible. 2. There could be sneaky ways of obtaining privileges once no-new-privileges is set. (1) is pretty straightforward since we can just disallow unprivileged chroot after any other chroot. (2) is the complex one. Are there others? Some no-cred-change property for processes seems extremely useful from a security perspective and, if we have one we could trust, this patch becomes trivial. Would it make sense just to work on that first and come back to unprivileged chroot later? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 191114] New: buildworld failure using WITHOUT_NCURSESW
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191114 Bug ID: 191114 Summary: buildworld failure using WITHOUT_NCURSESW Product: Base System Version: 10.0-STABLE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: dewa...@heuristicsystems.com.au Performing a buildworld using 10.Stable on both amd64 and i386 platforms result in the error (below) during stage 5.1. /etc/src.conf contains this line WITHOUT_NCURSESW=YES when the line is removed, the build completes successfully. The world is prepared for headless servers, so unnecessary material is removed. uname -vK FreeBSD 10.0-STABLE #0 r267307M: Mon Jun 16 18:04:07 EST 2014 root@hathor:/usr/obj/usr/src/sys/hqdev-vga 1000710 CC='cc -m32 -march=core-avx-i -DCOMPAT_32BIT -isystem /usr/obj/usr/src/lib32/usr/include/ -L/us --- lib/ncurses/ncursesw__L --- --- init_keytry.h --- ./make_keys keys.list init_keytry.h ./make_keys: Exec format error *** [init_keytry.h] Error code 126 make[4]: stopped in /usr/src/lib/ncurses/ncursesw 1 error make[4]: stopped in /usr/src/lib/ncurses/ncursesw To reproduce echo WITHOUT_NCURSESW=YES /etc/src.conf echo 'CPUTYPE?= core-avx-I' /etc/make.conf echo 'ARCH=amd64' /etc/make.conf cd /usr/src make -j8 buildworld DESTDIR=/tmp/no-ncursesw /tmp/n-ncursesw.log 21 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
