This is the second time this week that my firewall has reported
the following:
[DoS Attack: ACK Scan] from source: 69.171.227.60, port 443, Sunday, August
05,2012 20:25:40
The reported IP address is within a range owned by Facebook
and DNS shows a hostname that (FWIW) is at least plausibly in
On Mon, Aug 6, 2012 at 10:06 AM, Michael ODonnell
michael.odonn...@comcast.net wrote:
is there *ANY*
legitimate reason why anything should be attempting to connect
from Facebook to my home IP address, which offers no such
services? I assume, of course, that the answer is No.
The *only*
On 8/6/12 10:13 AM, Brian Chabot wrote:
On Mon, Aug 6, 2012 at 10:06 AM, Michael ODonnell
michael.odonn...@comcast.net wrote:
is there *ANY*
legitimate reason why anything should be attempting to connect
from Facebook to my home IP address, which offers no such
services? I assume, of
It's *just* a home connection? No services? Nuke the connection
attempt.
If you're on a network with DHCP (most residential connections),
it's possible someone else wrote an app that points to a DNS
name that points to your IP address. Still safe to nuke it.
When you say nuke the
On Mon, Aug 6, 2012 at 11:31 AM, Michael ODonnell
michael.odonn...@comcast.net wrote:
When you say nuke the connection attempt do you mean
kill the process that's attempting to open the connection?
I can't, because it's an inbound connection and that process is
(apparently) somewhere inside
On Mon, Aug 6, 2012 at 10:13 AM, Brian Chabot br...@datasquire.net wrote:
The *only* reason Facebook should be contacting you this way is if you
have an app set to pull data from there.
Doesn't need to be an app. A simple web link to a home IP address,
or name that resolves to same, will do
When you say nuke the connection attempt do you mean
[...]
Nuke as in (continue to) deny the connection attempt.
Cool.
Hmmm, I did end up in a situation recently (and reluctantly)
where I was obliged to install a Firefox add-in involved
with use of MacroMedia's AdobeConnect (grrr! don't
