Date: Thu, 27 Apr 2000 06:49:45 -0400 (EDT) From: Trevor Johnson <trevor@jpj.net> To: freebsd-gnats-submit@freebsd.org Subject: kern/18252: sysctl -a causes panic Message-ID: <Pine.BSI.4.21.0004270637070.5434-100000@blues.jpj.net>
next in thread | raw e-mail | index | archive | help
>Number: 18252 >Category: kern >Synopsis: sysctl -a causes panic >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 27 03:50:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Trevor Johnson (trevor@jpj.net) >Release: 5.0-CURRENT >Organization: myself >Environment: FreeBSD ws99.invalid 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Apr 25 17:12:54 PDT 2000 root@dennis1.invalid:/usr/src/sys/compile/FREEBASE50b i386 >Description: I'm running 5.0-CURRENT with a kernel built from sources cvsupped at around 11:27 UTC 2000-04-06, with a couple of small patches from Soren Schmidt (needed so my IDE CD-RW drive will work). When I run "sysctl -a" as an ordinary user, my system panics. My /sbin/sysctl is out of date (from around March 6th) but this seems like something a hostile user could take advantage of. My kernel configuration is at http://jpj.net/~trevor/freebsd/FREEBASE50b.gz . >How-To-Repeat: % /sbin/sysctl -a >Fix: unknown >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.21.0004270637070.5434-100000>