(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version



Shameful Internet providers

Wed Jun 23 18:02:11 2004



A client of a client (in other words, I sub to the person this company does business with), finally got high speed internet access last Friday. They didn't think to ask me or anyone else about it; they just called Cox cable who came in and put a static ip address on one of their machines without updating Microsoft updates or Norton Anti-virus.

Of course they were immediately attacked. That's when I got called to come down with a firewall router. All's well now (I hope!), although I had a heck of a time getting the box up to date.

Shouldn't internet providers like this be just a little more conscientious? I think it's just disgusting that they would do this, and even more so because the ONLY reason I was called was because the machine couldn't print after being attached to the Cox modem. Well, of course it couldn't: it was no longer attached to the internal network and now had a static, routable ip address anyway!

I'm sure the installer had a protected machine - they always do, so they can test. He or she could have temporarily gated the clients machine through that and made sure that Microst Updates were current (I had 22 critical updates to install!) and that Norton Anti-Virus was up to date.

I don't blame the customer for not knowing any better, but I do blame Cox for not educating them and for not insisting on a firewall router. All this does is add more problems to the whole Internet for the rest of us to deal with.




Click here to add your comments


~ ISP's should be liable for bandwidth ONLY. No firewalls, proxies, or other filters should be applied. That would be like public libraries being required to ban certain politically incorrect books that are frowned upon by the Christian coalation. Think about that. When an ISP sets up an internet account, all they should do is exactly what they did... although some precautionary advise would have been nice to give. ~jay


~ ISP's should be liable for bandwidth ONLY. No firewalls, proxies, or other filters should be applied. That would be like public libraries being required to ban certain politically incorrect books that are frowned upon by the Christian coalation. Think about that. When an ISP sets up an internet account, all they should do is exactly what they did... although some precautionary advise would have been nice to give.

~jay

Yes, I don't mean that they should PROVIDE a firewall - just cautionary advice.

Consider that compromised machines just add to all our grief..

--TonyLawrence



~ ISP's should be liable for bandwidth ONLY. No firewalls, proxies, or other filters should be applied. That would be like public libraries being required to ban certain politically incorrect books that are frowned upon by the Christian coalation. Think about that. When an ISP sets up an internet account, all they should do is exactly what they did... although some precautionary advise would have been nice to give.

~jay

Yes, I don't mean that they should PROVIDE a firewall - just cautionary advice.

Consider that compromised machines just add to all our grief..

--TonyLawrence


The analogy of the public library isn't exactly appropriate. He's not suggesting that the ISP should filter the client's content.

He's suggesting that the installer/ISP, of all people, know's the risks involved in establishing a static IP address, and should be liable to inform the user of such risks, as well as ways to minimize it. (Most do this as a way to sell additional software or hardware.)

A more appropriate analogy would be a fireworks vendor selling a large and, unbeknownst to the buyer, dangerous firework. All the buyer knows is that it's going to look really pretty in the sky. He's being sent out without being informed that this thing can blow his arm off. Just my .02
-Anonymous


~ ISP's should be liable for bandwidth ONLY. No firewalls, proxies, or other filters should be applied. That would be like public libraries being required to ban certain politically incorrect books that are frowned upon by the Christian coalation. Think about that. When an ISP sets up an internet account, all they should do is exactly what they did... although some precautionary advise would have been nice to give.

~jay

Yes, I don't mean that they should PROVIDE a firewall - just cautionary advice.

Consider that compromised machines just add to all our grief..

--TonyLawrence


The analogy of the public library isn't exactly appropriate. He's not suggesting that the ISP should filter the client's content.

He's suggesting that the installer/ISP, of all people, know's the risks involved in establishing a static IP address, and should be liable to inform the user of such risks, as well as ways to minimize it. (Most do this as a way to sell additional software or hardware.)

A more appropriate analogy would be a fireworks vendor selling a large and, unbeknownst to the buyer, dangerous firework. All the buyer knows is that it's going to look really pretty in the sky. He's being sent out without being informed that this thing can blow his arm off. Just my .02
-Anonymous


~ ISP's should be liable for bandwidth ONLY. No firewalls, proxies, or other filters should be applied. That would be like public libraries being required to ban certain politically incorrect books that are frowned upon by the Christian coalation. Think about that. When an ISP sets up an internet account, all they should do is exactly what they did... although some precautionary advise would have been nice to give.

~jay

Yes, I don't mean that they should PROVIDE a firewall - just cautionary advice.

Consider that compromised machines just add to all our grief..

--TonyLawrence


The analogy of the public library isn't exactly appropriate. He's not suggesting that the ISP should filter the client's content.

He's suggesting that the installer/ISP, of all people, know's the risks involved in establishing a static IP address, and should be liable to inform the user of such risks, as well as ways to minimize it. (Most do this as a way to sell additional software or hardware.)

A more appropriate analogy would be a fireworks vendor selling a large and, unbeknownst to the buyer, dangerous firework. All the buyer knows is that it's going to look really pretty in the sky. He's being sent out without being informed that this thing can blow his arm off. Just my .02
-Anonymous
---July 8, 2004

Or, if we want to use the library analogy the book you want may have been contaminated with Anthrax. The librarian should warn you..

--Foobah




Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


book graphic unix and linux troubleshooting guide

My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!



 I sell and support
 Kerio Mail server




pavatar.jpg
More:
       - Blog
       - Networking
       - Security


Unix/Linux Consultants

Skills Tests

Guest Post Here











My Favorites

Change Congress