In article <[EMAIL PROTECTED]>,
Onno <[EMAIL PROTECTED]> writes:
> Hmmm, this means that running tcplogd is a security hazard...
Yes, definitely. iplogger should be purged from the distribution. Use
ippl from potato (fetch the source and recompile for slink usage). ippl
does the same tcplo
Hmmm, this means that running tcplogd is a security hazard...
Thanks,
Onno
At 01:25 AM 11/13/99 +0100, Engard Ferenc wrote:
On Fri, 12 Nov 1999, Onno wrote:
>At 09:37 PM 11/11/99 +0100, Ralf Nyren wrote:
>>In package iplogger there is a daemon, tcplogd, which logs incoming
>>tcp-connection
On Fri, 12 Nov 1999, Onno wrote:
>At 09:37 PM 11/11/99 +0100, Ralf Nyren wrote:
>>In package iplogger there is a daemon, tcplogd, which logs incoming
>>tcp-connection attempts to syslog.
>> It seems that this daemon forks a child for every connection discovered and
>>if for example the machine r
At 09:37 PM 11/11/99 +0100, Ralf Nyren wrote:
Hi!
I don't if this is already known but I thought it might be worth a notice.
In package iplogger there is a daemon, tcplogd, which logs incoming
tcp-connection attempts to syslog.
It seems that this daemon forks a child for every connection dis
Hi!
I don't if this is already known but I thought it might be worth a notice.
In package iplogger there is a daemon, tcplogd, which logs incoming
tcp-connection attempts to syslog.
It seems that this daemon forks a child for every connection discovered and
if for example the machine running t
5 matches
Mail list logo