On Sat, 31 Dec 2016 01:18:16 +0100, Alexander Bluhm wrote:
> Currently syslogd accepts network input only for either IPv4 or
> IPv6. To overcome this limitation, allow to specify more than one
> listen addresses.
>
> As multiple TLS contexts need more thought, implement it only for
> TCP and
On Sun, 01 Jan 2017 21:05:58 +0100, Alexander Bluhm wrote:
> Regular programs should die as early as possible when an error
> occurs, then it can be fixed. But syslogd is special. If it dies,
> you become blind and don't see any errors at all. An attacker could
> exploit this. So I think
On Sun, Jan 01, 2017 at 08:43:49AM -0700, Todd C. Miller wrote:
> Now that syslogd supports multiple network sockets, does it still
> make sense to die if one of them cannot be bound? It seems like
> syslogd should still run as long as there is at least one address
> it can bind to.
>
> What do
Now that syslogd supports multiple network sockets, does it still
make sense to die if one of them cannot be bound? It seems like
syslogd should still run as long as there is at least one address
it can bind to.
What do you think?
- todd
Hi,
Currently syslogd accepts network input only for either IPv4 or
IPv6. To overcome this limitation, allow to specify more than one
listen addresses.
As multiple TLS contexts need more thought, implement it only for
TCP and UDP sockets now.
ok?
bluhm
Index: usr.sbin/syslogd/syslogd.8
