Date: Wed, 30 May 2007 12:27:44 GMT From: Erik<fastdeverik@hotmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/113157: PortACL Rules causing crash Message-ID: <200705301227.l4UCRi1K040182@www.freebsd.org> Resent-Message-ID: <200705301230.l4UCUAI4071907@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 113157 >Category: kern >Synopsis: PortACL Rules causing crash >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 30 12:30:10 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Erik >Release: 6.2-STABLE >Organization: FAST >Environment: FreeBSD www.maadnet.net 6.2-STABLE FreeBSD 6.2-STABLE #3: Tue May 29 07:54:13 EDT 2007 root@www.maadnet.net:/usr/obj/usr/src/sys/MAADNET.NET i386 >Description: My ssh daemon is running on port 8691, uid for that process is 22, gid is 22. Kernel security is enabled and kern.securelevel is set as 1337. Compiled kernel with options: options MAC options MAC_PORTACL Specified kernel tunables in sysctl.conf: security.mac.portacl.enabled=1 security.mac.portacl.rules=uid:80:tcp:80,uid:80:tcp:443,uid:22:tcp:8691 On system boot, when the tunables are read from sysctl.conf, a page error occurs when reading the rules. I believe this to happen because the highest port that portacl is configured (by default) to watch is 1023 but my ruleset was configured to have portacl active on 8691. >How-To-Repeat: See problem description. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705301227.l4UCRi1K040182>