Forgot your password?
typodupeerror

Submission Summary: 0 pending, 8 declined, 5 accepted (13 total, 38.46% accepted)

Submission + - Ask Slashdot: How to deal with persistent and incessant port scanner

jetkins writes: What would you do if your firewall was being persistently targeted by port scans from a specific group of machines from one particular company?

I run a Sophos UTM9 software firewall appliance on my home network. Works great, and the free Home Use license provides a bunch of really nice features normally only found on commercial-grade gear. One of those is the ability to detect, block, and report port scans, and under normal circumstances I only get the occasional alert when some script kiddie comes a-knocking at my door.

But in recent months I have been getting flooded with alerts of scans from one particular company. I initially reported it to my own ISP's (RoadRunner's) abuse desk, on the assumption that if they're scanning me then they're probably scanning a bunch of my neighbors as well, and any responsible ISP would probably want to block this BS, but all I ever got back was an automated acknowledgement and zero action.

So I used DNS lookup and WHOIS to find their phone number, and spoke with someone there; it appears that they're a small outfit, and I was assured that they had a good idea where it was coming from and that they would make it stop. Indeed, it did stop a few days later but then it was back again, unabated, after another week or so. So last week I called them again, and was once again assured of a resolution. No dice, the scans continue to pour in.

I've already blocked their subnet at my firewall, but the UTM apparently does attack detection before filtering, so that didn't stop the alerts. And although I *could* disable port scan alerts, it's an all-or-nothing thing and I'm not prepared to turn them off completely.

This afternoon I forwarded the twenty-something alerts that I've received so far today, to their abuse@ address with an appeal for a Christmas Miracle, but frankly I'm not holding out much hope that it will have any effect.

So, Slashdotters, what should I do if this continues into the new year? Start automatically bouncing every report to their abuse address? Sic Anonymous on them? Start calling them every time? I'm open to suggestions.

Submission + - Ask Slashdot: How to deal with a company that appears unconcerned that their use 3

jetkins writes: As the owner of my own mail domain, I have the luxury of being able to create unique email addresses to use when registering with web sites and providers. So when I started to receive virus-infected emails recently, at an address that I created exclusively for use with a well-known provider of tools for the Systems Administration community (and which I have never used anywhere else), I knew immediately that either their systems or their subscriber list had been compromised.

I passed my concerns on to a couple of their employees whom I know socially, and they informed me that they had passed it up the food chain, but I have never received any sort of official response, nor seen any public notification or acceptance of this situation.

When I received another virus-infected email at that same address this week, I posted a polite note on their Facebook page. Again, nothing.

If it was a company in any other field, I might expect this degree of nonchalance, but given the fact that this company is staffed by — and primarily services — geeks, I'm a little taken aback by their apparent reticence.

So, since the polite, behind-the-scenes approach appears to have no effect, I now throw it out to the group consciousness: Am I being paranoid, or are these folks being unreasonable in refusing to accept or even acknowledge that a problem might exist? What would you recommend as my next course of action?
Spam

Submission + - DynDNS drops NDR's from their MailHop service

jetkins writes: In an email to subscribers, DynDNS announced that they "will no longer deliver locally-generated NDRs from any MailHop systems." Mailhop is a multi-faceted service offering in- and outbound relay services, spam and virus filtering, and store-and-forward buffering.

DynDNS makes it clear that they are aware that this goes against RFC 2821 Section 3.7, but explains that in their opinion the increase in spam volume, and the use of NDR's as a spam vector in their own right, means that the value of NDR's is now far outweighed by their potential for harm.

Is DynDNS merely the first one to blink? Will this start a flood (mutiny) of ISP's following suit? Should they have made efforts to have the standard changed instead of just saying "fsck the police"?
Communications

Submission + - Cell phones in planes on trial Down-Under

jetkins writes: Just days after the FCC announced that the use of cellular phonres would be officially banned onboard aircraft in the USA, the Melbourne Age reports that Australian airline Qantas is to undertake a three-month trail of a new in-flight cellular service. Initially installed on a single aircraft, the system utilizes technology from British company Aeromobile, providing a miniature GSM "tower" within the aircraft cabin. Since GSM phones dynamically adjust their transmit power, being in such close proximity to the tower means that phones will emit only minimal RF. The system operates as a separate "country", meaning phones must be enabled for international roaming and calls are charged at international roaming rates. During the trial at least, only SMS, MMS, and GPRS (data) traffic will be allowed; voice calls will be blocked.
Handhelds

Submission + - Official: Palm to go Linux

jetkins writes: The Melbourne Age reports that company officials announced Tuesday that Palm will move to a new Linux-based platform "to help the company compete better." According to The Age the move was announced "during a meeting with analysts in New York, where they also discussed the company's business strategy and refused to talk about recent rumors of a possible buyout."

Slashdot Top Deals

"Success covers a multitude of blunders." -- George Bernard Shaw

Working...