Why are you not running Apache? New IIS holes should make you rethink your web server
It has been a while since I have played with Apache, I will admit that. The last time I used it, version 2.0 was the norm, and version 2.2 was just coming out of beta. Today of version 2.2.11 is the current version. What got me thinking about Apache was partially nostalgia and partially head banging and continued frustration with government use of IIS, especially given the exciting events this week.
First, we have reports of the theft and corruption of the Commonwealth of Virginia’s Prescription Monitoring Program web site. The story is that the site had been hacked, the data encrypted or deleted or being held hostage, according to a variety of sites, and the FBI is investigating. As discussed on the latest Search Engine, almost no one is really taking the ransom demand seriously for a variety of reasons. The second topic that got me annoyed was a ComputerWorld article yesterday about new, serious bugs in IIS and Microsoft’s prevailing attitude about the risk. Finally I had to set up an IIS server and kept lamenting that it should not be this hard.
Now, in all fairness, IIS 7 is supposed to be a much better product with text file configuration capability (just like Apache) and it is supposed to be more secure. My question is this. Why, would anyone voluntarily run their web site on IIS? Especially if it was a forward-facing site, connected to the Internet and subjected to attacks every minute of every day?
One of the most outstanding products from the Open Source community is Apache. It is robust, reliable, secure and easily configurable on so many levels. It runs on almost every platform out there, although personally I would only run forward-facing sites with Apache on a stripped and hardened Linux kernel, and it supports a wide variety of plugins for content management, application management and document presentation.
According to Netcraft, the hacked Virginia site is running IIS 5.0 and 6.0 on Windows 2000 and 2003. This violates a number of basic security tenants, patch management being only one of them, but I am continually amazed that government organizations continue to put their citizen’s data at risk this way. More and more, the United States government is collecting your personal data. TSA is about to start collecting your full name, birth date and other personally identifiable information (PII). The current administration is pushing for electronic medical records. Already many government services are only available on-line, and require large amounts of PII to be inputed to get everything from veteran’s benefits to government grants, yet it seems that each of the owners of these sites seems to be less concerned about the security of their customer’s data rather than the perceived ease of operation and cost of ownership by running IIS. There are more stringent security requirements on government laptops than there is on website security.
The Internet, and its interconnection of data, is a good thing. However the front door to these repositories should be as secure and as impenetrable as they can be. Gone are the days of gentlemen hackers who, when finding an unlocked door, would politely tell the site admin about it. This is full scale guerilla warfare, and as administrators and architects, it is our responsibility to make sure the crackers cannot get access to the data that they are not supposed have access to, while the customers can do what they need to do.
Next time we will talk about the data itself, and the databases that it resides on.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide