Date: Tue, 6 Oct 1998 10:35:12 -0700 (PDT) From: Dan Busarow <dan@dpcsys.com> To: Studded <Studded@dal.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <Pine.BSF.3.96.981006103009.16376H-100000@java.dpcsys.com> In-Reply-To: <361A4F37.141BAE11@dal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Oct 1998, Studded wrote: > I don't think spaces are valid on either side of the syslog.conf entry. > At least my reading of the man page doesn't suggest that. > > Multiple selectors may be specified for a single action by > separating > them with semicolon (``;'') characters. It is important to note, > howev- > er, that each selector can modify the ones preceding it. > > Multiple facilities may be specified for a single level by > separating > them with comma (``,'') characters. The LHS does look space safe. > The section about the RHS is more wordy, but the only valid seperator > mentioned is a comma. My vote is to change the code, failing that, the > comment in the PR would be a good start. >From the man page # Pipe all authentication messages to a filter. auth.* |exec /usr/local/sbin/authfilter Unless someone can demonstrate a valid use of spaces on the LHS crontab style checking would work though. (spaces are only legal in the last field of crontab as well) Dan -- Dan Busarow 949 443 4172 Dana Point Communications, a California corporation dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981006103009.16376H-100000>