From: Dale Amon <amon@vnl.com>
To: Russell Coker <russell@coker.com.au>
Cc: Dale Amon <amon@vnl.com>, SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: Boot time avc messages
Date: Mon, 22 Sep 2003 11:34:23 +0100 [thread overview]
Message-ID: <20030922103423.GR12158@vnl.com> (raw)
In-Reply-To: <200309202339.52886.russell@coker.com.au>
On Sat, Sep 20, 2003 at 11:39:52PM +1000, Russell Coker wrote:
> > allow syslogd_t syslogd_t:capability { fsetid };
>
> I still can't work out why syslogd would need fsetid. What stops working if
> you deny it?
In syslog-ng's affile.c it seems to twiddle file ownerships if
necessary when opening a log file, if I correctly understood what
is going on around a chown() call after all of 30 seconds of code
scanning...
> > allow syslogd_t tty_device_t:chr_file { setattr };
>
> If we could make it some sort of standard to write to /dev/tty12 (for example)
> then we could relabel the terminal device(s) in question to a syslog specific
> type and allow syslog to write to it.
Trouble is, this is user configurable, for example, I have this on some of
my machines:
# Virtual console.
#
destination console_all { file("/dev/tty8"); };
> Also how does syslog-ng handle ^S on the terminal it's writing to?
Haven't checked yet. I'm still sipping coffee and the only machine
here in my home office with this running would be the firewall for
which I have to find a keyboard and crawl under the table to connect
it first. Later. :-)
> > There are 3 ports discussed in the manual
> > (found at http://www.balabit.com/products/syslog_ng/reference/book1.html).
> >
> > The internal default is to listen on 514 tcp and/or udp or send to
> > that port. However it is also used by rshell, so many people
> > use the document's example ports instead and place this line in
> > syslog-ng.conf:
>
> So syslog-ng has it's own special method of logging in addition to the
> standard ways? :(
>
> > destination d_tcp { tcp("10.1.2.3" port(1999); localport(999)); };
>
> What is port 1999 for?
A server listens on 1999, clients rcv on 999. Sometimes you can have a
machine acting as both, ie a host that consolidates from a local LAN
as a server and then connects over a tunnel as a logging client to a
master server.
Here's what a connection looks like in iptstate:
Source IP Destination IP Proto State TTL
xx.xx.xx.xx,999 yy.yy.yy.yy,1999 tcp ESTABLISHED 119:59:42
--
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.
next prev parent reply other threads:[~2003-09-22 10:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030915214153.GE8988@vnl.com>
2003-09-16 14:53 ` Boot time avc messages Dale Amon
2003-09-17 10:14 ` Russell Coker
2003-09-17 10:14 ` Russell Coker
2003-09-17 12:37 ` Dale Amon
2003-09-17 12:45 ` Russell Coker
2003-09-19 15:41 ` Dale Amon
2003-09-20 6:32 ` Russell Coker
2003-09-20 12:21 ` Dale Amon
2003-09-20 13:39 ` Russell Coker
2003-09-22 10:34 ` Dale Amon [this message]
2003-09-22 13:25 ` Dale Amon
2003-09-20 13:13 ` Dale Amon
2003-09-20 13:35 ` Russell Coker
2003-09-20 14:38 ` Dale Amon
2003-09-20 14:51 ` Dale Amon
2003-09-18 13:07 ` Dale Amon
2003-09-18 13:11 ` 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=20030922103423.GR12158@vnl.com \
--to=amon@vnl.com \
--cc=russell@coker.com.au \
--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.