All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Erich Schubert <erich@debian.org>
Cc: selinux@tycho.nsa.gov, fedora-selinux-list@redhat.com,
	Debian Devel <debian-devel@lists.debian.org>
Subject: Re: log file names (was Additional rule files)
Date: Sun, 5 Sep 2004 20:45:46 +1000	[thread overview]
Message-ID: <200409052045.46899.russell@coker.com.au> (raw)
In-Reply-To: <1094260356.29689.44.camel@wintermute.xmldesign.de>

On Sat, 4 Sep 2004 11:12, Erich Schubert <erich@debian.org> wrote:
> The next two rule sets are for the statistic tools "bindgraph" and
> "mailgraph". The first parses bind query logs and does nice graphs out
> of them, the second does the same for postfix+amavis logs.

Do we need to have two different domains for programs that do the same thing?

Both bindgraph and mailgraph can read the same file types as input and their 
output can be accessed by cgi-bin scripts.  It seems that there is little (if 
any) benefit in isolating them.

If we were to assign different types to different log files (may require code 
changes in syslogd) then we could deny the mailgraph program the ability to 
read log files other than mail.log and deny the bindgraph program the ability 
to read mail.log.

Also note that in your policy both those programs can read /var/log/auth.log 
(Debian) and /var/log/secure (Fedora).  This is not desirable, we probably 
should make changes to the syslog setup.

One possible change is greater use of sub-directories in /var/log.  We could 
have /var/log/security/ for auth.log, secure, and any other security critical 
log files and /var/log/mail/ for mail server log files (including POP server, 
and maybe webmail), etc.  Doing this would allow different types for the log 
files with no code changes to syslogd, and this would make it more beneficial 
to have separate domains for mailgraph and bindgraph.

I've CC'd this to fedora-selinux and debian-devel because if we make such 
changes then we want to get some cross-distribution agreement on file names.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2004-09-05 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04  1:12 Additional rule files Erich Schubert
2004-09-05 10:19 ` Russell Coker
2004-09-06 17:12   ` Erich Schubert
2004-09-13 22:52   ` Erich Schubert
2004-09-19 10:02     ` Russell Coker
2004-10-02 23:37       ` Erich Schubert
2004-09-05 10:27 ` Russell Coker
2004-09-05 10:31 ` Russell Coker
2004-09-05 13:54   ` Erich Schubert
2004-09-05 17:34     ` Luke Kenneth Casson Leighton
2004-09-05 17:38       ` Erich Schubert
2004-09-05 18:50         ` Luke Kenneth Casson Leighton
2004-09-05 10:45 ` Russell Coker [this message]
     [not found]   ` <00ab01c4933f$c66e32f0$0a01a8c0@huey>
2004-09-05 12:52     ` Is anyone using Selinux for VOIP applications? Russell Coker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200409052045.46899.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=debian-devel@lists.debian.org \
    --cc=erich@debian.org \
    --cc=fedora-selinux-list@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.