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
At 11:36 PM 11/14/99 -0500, Chris Wagner wrote:
At 05:47 PM 11/14/99 -0800, Michael W. Shaffer wrote:
><> Is this adequate to protect from random dialers who might
>stumble on the modem tone and try logging in to this machine?
I think war dialers are a thing of the past really.
Nope, they are
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
At 05:47 PM 11/14/99 -0800, Michael W. Shaffer wrote:
><> Is this adequate to protect from random dialers who might
>stumble on the modem tone and try logging in to this machine?
I think war dialers are a thing of the past really.
><> Are there any other routine actions like this I should take
"Michael W. Shaffer" <[EMAIL PROTECTED]> writes:
> What I have done is create an /etc/mgetty/login.config file with
> only the following two lines:
>
> adminname - - /bin/login @
> * - - /bin/false
Are you aware that entering adminname and any password will cause
login to re-
I have recently installed a Linux machine at a remote customer
site to serve as a masquerading firewall/router and various other
things such as SMTP/POP3 spool, DNS cache, etc. I installed two
modems, one for dial-out only to the local ISP and the other which
has a simple mgetty listening on it for
6 matches
Mail list logo