Choosing an Internet Services Provider
With a BBS, shell account, or on-line service, the dangers are small and minimal. The worst danger (possible with any service, of course) is probably a lightning strike that damages your modem, and possibly your computer. If you download programs directly from the service involved, you may need to think about viruses (none are known on Linux) or Trojan Horses, programs which claim to do one thing and really do another. If you consider censorship a danger, you are most likely to find it in various forms on the on-line services.
With fake IP, the dangers are also rather minimal, but the danger of a remote user breaking into your computer, while remote, now exists. Someone using the same ISP may be able to log into your computer if you don't pay attention to basic security, such as having good passwords for your accounts.
With serial IP, the dangers are very real. Unlike single-user program loaders like DOS and Windows, Linux is designed to function across the network. This power brings the potential for break-ins if security is not maintained. And in order to manage that power, it is best to know a little bit about what you are doing. The Linux Network Administrator's Guide (The NAG) tells you all you need to know to understand how to maintain your network, so have a copy handy.
Of course, you need to maintain good passwords—that should go without saying. Don't run unnecessary services. Read the /etc/inetd.conf file and comment out (by inserting a # character at the beginning of the line) services that you don't need. If you don't want anyone to be able to use telnet to connect to your machine, comment out the line that starts telnetd. If you are confused, read the NAG.
Make sure that you have a file called /etc/securetty. The securetty file controls which terminals root is allowed to log in on, and allowing root logins over the network is a good way to invite break-ins. Make sure that it does not contain any lines starting with ttyp--these are the pseudo-ttys that are used for network logins.
Pay attention to security alerts. Security holes in Linux or Linux distributions are announced on the comp.os.linux.announce newsgroup. Read these announcements and act on them. They contain careful, easy-to-follow instructions on how to close the security hole in question. If you have PGP installed, use it to ascertain that the announcement is genuine before following the instructions.
If you have reason to be even more careful about security, take time to learn about authorization (man tcpd) and firewall software—there are several articles in this issue on that topic.
Pricing structures may have nothing to do with reality. If prices seem too low to believe, they may well be. How much trouble would it be to switch your e-mail to another site if your current provider goes out of business? What about your web site or your home page? Many ISPs have gone out of business in the last year, and the trend doesn't appear to be slowing down yet.
Do you want a local ISP or a national one? There are advantages to both; some people keep two accounts, one local and one national. If your ISP is near you, they will be easier to find. They may know more about people at the local phone company office and know who to talk to to get things done (or fixed) at a local level. By contrast, a national ISP has sites all around the nation that you can call in to, and by being bigger businesses, they may have more resources to provide the right distribution of equipment to meet all their users needs.
You need to decide what level of service you want, and be willing to pay for what you need. If your business depends on your connection, you probably don't want to go with a fly-by-night operation that may or may not be around next week, and may not have as much experience. If you just want to “surf the net” and can deal with trouble or switching providers if necessary, you are likely to be able to pay less—just don't expect the same level of service from all providers, regardless of price.
Also, it's important to understand that there are some things that the ISP can fix, and some things that the ISP can't fix any more than you can. The ISP can provide enough modems that you don't get a busy signal too often, and the ISP should be able to respond as quickly to emergency phone calls as they promise to, however quickly that is. The ISP can't, however, fix the rest of the Internet if their own connection to the Internet is broken by their provider, or make the phone company fix broken phone equipment on your schedule.
The Internet is constantly under construction. Choosing an ISP with multiple connections to the Internet through different providers makes it less likely that your ISP will temporarily loose Internet connectivity through no fault of their own. If your business depends on reliable connections to many different parts of the Internet, choose an ISP with two or three connections to major Internet providers, such as MCI, Sprint, PSI, or ANS.
Troubles will occur. Every ISP has troubles from time to time. You may have the choice of bouncing from one ISP to another. Our recommendation is to stick with one ISP as long as you can, especially if you choose a local ISP, because they can be extra helpful to people they know.
If you absolutely, positively need Internet access all the time, consider keeping a backup account at a different ISP. If you do this, make sure that the backup account is connected to the Internet in a different way than your main ISP. It may even be worth making a long-distance call in an emergency, depending on your need.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Hacking a Safe with Bash
- Django Models and Migrations
- Secure Server Deployments in Hostile Territory, Part II
- Huge Package Overhaul for Debian and Ubuntu
- Home Automation with Raspberry Pi
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development