Re: TCP Scan by Google machine?
From: Documatrix (florrie_at_casualsailor.com)
Date: 01/07/05
- Next message: jeanjean: "Re: trojan horse attack"
- Previous message: Greg Hennessy: "Re: Proxy + content filetering + antivirus +auth"
- In reply to: Michael Fuhr: "Re: TCP Scan by Google machine?"
- Next in thread: Michael Fuhr: "Re: TCP Scan by Google machine?"
- Reply: Michael Fuhr: "Re: TCP Scan by Google machine?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 7 Jan 2005 13:45:56 -0800
Thanks for the reply, Michael. You're probably right: These are
originating at Google's port 80, but it bugs me that they're running
through my TCP ports.
OnlineEye's Open Port Check registers a TIME_WAIT status for each of
the "attempts." On three occasions that I've noticed, the status has
been ESTABLISHED for a few minutes, then the connection drops.
Whatever it is has apparently finished running through the ports and
started over...
Ah well. I have an e-mail in to Google. Maybe it's one of their own
utilities or, as you suggest, someone's exploiting a Google service.
Whichever, perhaps they'll get back to me soon on it.
Thanks for your help,
Florrie
- Next message: jeanjean: "Re: trojan horse attack"
- Previous message: Greg Hennessy: "Re: Proxy + content filetering + antivirus +auth"
- In reply to: Michael Fuhr: "Re: TCP Scan by Google machine?"
- Next in thread: Michael Fuhr: "Re: TCP Scan by Google machine?"
- Reply: Michael Fuhr: "Re: TCP Scan by Google machine?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|