On 02-Apr-01 William W. Austin opined:
> Here's an odd one.
>
> I have a machine which had been a firewall for some time until my main
> system
> went down (burned out MB -- had to replace). While that machine was
> reconfigured as a workstation, it got broken into, and the next day
> (when the
> new machine arrived a week earlier than expected) I dutifully
> re-installed on
> the firewall machine from scratch just to be safe.
>
> Now the interesting thing begins. Ever since the breakin and the
> follow-up
> reinstall, I get a beakin attempt on the firewall machine every 12
> minutes,
> obviously running out of cron somewhere.
>
> The spooky part is that the network address of the machine trying to
> break in is
> on my local network, on this side of the firewall. It is a windoze box
> I keep
> around for my son to play games on, etc.
>
> Why I say it is spooky is that the attacks continue even if this
> machine is
> turned off and disconnected totally from the network. Obviously
> someone is
> spoofing the address. They stop only if I take down my dsl link to my
> isp, so
> clearly they are not local.
>
> I am also running tripwire and portsentry on this box, and portsentry
> is logging
> the attempts (and they show up in /var/log/messages regular as
> clockwork of
> course).
>
> As tripwire is not finding any problems and ckrootkit gives me a clean
> bill of
> health (I run these and portsentry on this machine and every other
> machine on my
> network as well) -- and FWIW nothing else wierd is being detected -- is
> it
> reasonable to say that someone has probably left a cron job going to
> try to
> break in, or should I pursue it further at this point?
>
> Any suggestions?
Shut down portsentry and monitor the logs.
I, just today, reinstalled & setup portsentry. My system load was sudenly
heavy every time I restarted portsentry and dropped off every time I
stopped it.
In my case, it looked like somebody slamming hard into a couple of ports,
but the address appeared to be external. I had the ports closed on the
firewall. I then went into portsentry configs and deleted the ports it
was monitoring one by one. Every time I deleted one, the port being
slammed would move to another.
I shut portsentry down and did tail -f on the logs, only to see almost no
activity from outside (there's always somebody hitting some port, but not
thousands of times a minute).
Just a wild guess and maybe not the problem. But, I didn't have this
happen before either and it had me scratching several parts of my body
for some time before I found the problem.
---
Me? A skeptic? Can you prove it?
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list