Most likely, yes. primarily, it depends on whether or not you know who 61.80.2.113 is. If you don't, and they really have no reason to try to connect to that port, then Portsentry did the right thing. Either way, it is doing its job, yes.
On Sat, 15 Dec 2001, Edward Dekkers wrote: > This is the first time I've seen this. This is good right? He/She didn't get > in? > > Active System Attack Alerts > =-=-=-=-=-=-=-=-=-=-=-=-=-= > Dec 15 12:39:04 server portsentry[712]: attackalert: SYN/Normal scan from > host: 61.80.2.113/61.80.2.113 to TCP port: 12345 > Dec 15 12:39:04 server portsentry[712]: attackalert: Host 61.80.2.113 has > been blocked via wrappers with string: "ALL: 61.80.2.113" > Dec 15 12:39:04 server portsentry[712]: attackalert: Host 61.80.2.113 has > been blocked via dropped route using command: "/sbin/route add -host > 61.80.2.113 gw 127.0.0.1" > Dec 15 12:39:04 server portsentry[712]: attackalert: SYN/Normal scan from > host: 61.80.2.113/61.80.2.113 to TCP port: 12345 > Dec 15 12:39:04 server portsentry[712]: attackalert: Host: > 61.80.2.113/61.80.2.113 is already blocked Ignoring > > > -- > Edward Dekkers (Director) > Triple D Computer Services Pty. Ltd. > 822 Rowley Road > Oakford W.A. 6121 > +61 8 9397-1040 > ABN: 33 635 238 024 > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
