From owner-freebsd-security Tue Nov 10 04:32:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17538 for freebsd-security-outgoing; Tue, 10 Nov 1998 04:32:46 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17533 for ; Tue, 10 Nov 1998 04:32:45 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id HAA20274 for ; Tue, 10 Nov 1998 07:32:29 -0500 (EST) Date: Tue, 10 Nov 1998 07:32:28 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-security@FreeBSD.ORG Subject: chflags on log files question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok I setup a firewall box running with secure level 3. And added the following flags to /var/log files, uappnd and sappnd. This should allow syslog to continue to write to the files correct? For instance: -rw-r--r-- 1 root bin uappnd,sappnd 6581 Nov 3 01:15 sec-log Is where my sshd connections are logged, although why it hasn't logged any since the 3rd im still working on. But the flags should still allow syslog to write to them correct? Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message