Unpatched Linux Lives 3 Months on Internet 56
Allnighterking writes "The Honeypot project Honeynet.org has released their study on the expected lifetime of an unpatched default Linux install. If some of you remember AvanteGarde recently did a study of its own with several versions of Windows products and found that the average lifetime was about four minutes. Internet Week has an article on the study and the PDF with the full details of the study is available on Honeynet.org. Needless to say, from my viewpoint this is a good reason to limit Windows installations in IT that any PHB and/or Smiling Man can understand. Have them put into a spreadsheet and see what this kind of security means to their bottom line."
It depends (Score:3, Insightful)
Distro choice (Score:4, Interesting)
It would be an interesting thing to see how the other dists would fare. I suspect Debian and Gentoo should survive quite a bit longer than those 3 months. After all, a default minimal Debian Woody installation is 34MB, compared to 0.5GB of Red Hat, and this means you simply don't have that many unnecessary services that can fail.
Re:Distro choice (Score:4, Informative)
It would be an interesting thing to see how the other dists would fare. I suspect Debian and Gentoo should survive quite a bit longer than those 3 months. After all, a default minimal Debian Woody installation is 34MB, compared to 0.5GB of Red Hat, and this means you simply don't have that many unnecessary services that can fail.
Due to age, I am guessing that a Debian woody installation would fall rather quickly -- its just too old. Sure, the minimal install is tiny, with almost nothing to hijack, but a typical default server install has far too many things listening on every interface.
I'm curious how long an older (3.4 or 3.3) version of OpenBSD would have faired with a typical (not default) setup.
(My server right now is running Debian Woody, and has been since Potato was stable.)
Re:Distro choice (Score:3, Informative)
You see, the packages in Woody are kept up-to-date in the security department. The age of the packages is irrelevant to the security of the packages. All security fixes are backported to the Debian stable distribution.
Re:Distro choice (Score:3, Informative)
You see, the packages in Woody are kept up-to-date in the security department. The age of the packages is irrelevant to the security of the packages. All security fixes are backported to the Debian stable distribution.
I was referring to the test -- which did not involve any security updates.
In such a situation, an unpatched debian woody distro may fall rather quickly.
Re:Distro choice (Score:1)
Re:Distro choice (Score:3, Informative)
Why? I have never ever had any security problems. With or without iptables on. I have never used SELinux, I hear the security is beefed up.
I have never encountered a "failed service" on RH or FC. OK VMware sometimes comes close
I would think an FC3 box with iptables, SEL
Network services are what matters... (Score:3, Informative)
Re:Network services are what matters... (Score:1)
4 Minutes, or never (Score:5, Interesting)
Windows XP SP1 with the for-free ZoneAlarm firewall, however, as well as Windows XP SP2, fared much better. Although both configurations were probed by attackers, neither was compromised during the two weeks.
Also:
The Macintosh machine, on the other hand, was assaulted as often as the Windows XP SP1 box, but never was grabbed by a hacker, thanks to the tunnel vision that attackers have for Windows. "The automated bot/worm attackers were exclusively using Windows-based attacks," said Colombano, so Mac and Linux machines are safe. For now. "[But] it would have been very vulnerable had code been written to compromise its system," he added
And finally and most importantly:
"No machine is immune," he counseled. "No human is safe from every virus, and it's the same for machines. That's why people have to have some personal responsibility about security. You have to be a good citizen on the network, so you're not only protecting yourself, but others who might be attacked from exploits originating on your machine."
Re:4 Minutes, or never (Score:3, Insightful)
The assholes that release viruses, worms and other malware on the computing world are also well aware that the average Linux user is much more difficult to hoodwink than the average Windows user (your grandma, for example).
The past ~10 years of the popular web has exposed the best (altruism, open source efforts, education, anti-bullshit) and the worst (scammers, spammers, hate groups, SCO) of global society.
Have a great 2005 everyone.
Re:4 Minutes, or never (Score:1)
The Macintosh machine, on the other hand, was assaulted as often as the Windows XP SP1 box, but never was grabbed by a hacker, thanks to the tunnel vision that attackers have for Windows. "The automated bot/worm attackers were exclusively using Windows-based attacks," said Colombano, so Mac and Linux machines are safe. For now. "[But] it would have been very vulnerable had code been written to compromise its system," he added
Prove it. (I'm talking more to the guy in the article than you, btw.)
That is
Re:A firewall would help (Score:1)
It's a good idea to limit Windows? (Score:2)
Re:It's a good idea to limit Windows? (Score:2)
I don't know if Microsoft guarantees that its fixes won't screw things up (or even work), but there track history would make me hesitant before deploying 'fixes'.
Re:It's a good idea to limit Windows? (Score:1)
Best security (Score:2)
*it will not be connected to any outside network at all. your box will be. (Microsoft pulled this to give a high security rating to NT, i believe)
Re:Best security (Score:4, Informative)
Not exactly. I don't want to be an MS apologist, but the TCSEC rating that MS got for Windows NT was indeed while it was not connected to a network. We all agree that is rather useless these days. The problem was the TCSEC (Orange Book) certification; it specifically does not cover networked systems. Networks are covered by the Red Book. This problem is one of the reasons the Common Criteria was created, which can certify systems including networks.
What about newer distros ? (Score:1)
Re: (Score:2, Informative)
Re:Question about Red Hat (Score:3, Interesting)
if your cable modem has a firewall, turn that on also.
the less public you make your home box, the less up-to-date it has to be, in terms of security patches.
I still prefer to keep my internal boxes up to date. and it all boils down to how much you trust your vendor and the patch/pkg process (and the reviewers of all the code and patches).
after spending about 5 yrs in the linux world of things, chasing this and that distro, fixing pkgs mostly by hand, tracking things mo
Actually no, (Score:2, Insightful)
The message isn't Linux > Windows, it's that not keeping up to date with your patches is dangerous, and Linux is less of a target than Windows at the moment. By the submitters criterion, you would be recommending Apple to your PHB, not Linux, as an unpatched box wasn't even hit with any OS specific exploits!
An
Re:Actually no, (Score:3, Insightful)
The relevant data here is that if you are going to set up an internet server, a computer that will connect directly to the internet, or a computer in an untrusted environment in general, that Linux and Mac OS X are statistically least vulnerable to remote exploits (with some caveats related to the configuations tested).
It's just another (and a very important, but not necessarily the *mos
Re:So what? (Score:3, Funny)
Re:So what? (Score:2)
TTCFF (time to crash first file) is much faster on win98 and winme than any other o/s.
we're talking blue-ribbon, here.
Re:So what? (Score:1)
This is senseless (Score:5, Interesting)
The Linux box wasn't compromised because it was being attacked as if it were a Windows box.
Therefore, in this case, the article is suggesting that Linux is secure because it is *obscure*. Linux can't be hacked because nobody would want to/nobody knows how to because it's so rare in comparison to Windows = Security through Obscurity.
Microsoft also uses this practice by threatening to sue anyone who exposes a vulnerability in their OS, and by hiding their source code. Hiding source code and vulnerabilities = Security through Obscurity.
I find it morally offensive that Linux hacks are trying to pass of Linux as secure on exactly the same grounds that Microsoft uses to try and keep their own leaky OS as private and secure as they can. Thankfully the author is sensible enough to write a few disclaimers, but as usual, the Slashdot submitter decided to omit that for the sake of sensationalism (and for a quick boot into Microsoft because we all like that).
I bet I could put an unpatched Windows 3.11 box on the internet, too. I bet no-one would hack that. I'd suggest more people are out trying to exploit even Linux or Mac than old Win3.11/DOS. Or how about an OS/2 box? I bet that would last even longer than Linux. Perhaps we should all switch to OS/2?
Re:This is senseless (Score:5, Insightful)
in the last 72 hours.. Where are all these IIS servers that are being targeted? Apache outnumbers them 2 to 1. Wouldn't it make more sense to target Apache?
Re:This is senseless (Score:2)
Because publicizing a fault in an open source software product like Apache -- by publishing an exploit in the form of a pushbutton script kiddie tool, for example -- results in the fault getting fixed. Meanwhile, even if Microsoft does patch a known fault in IIS, a lot of home users/amateur server admins either won't know about the patch, or do know about it but don't bothe
Re:This is senseless (Score:2)
From a pragmatic point of view, why should I care what the reason is?
Re:This is senseless (Score:2)
But seriously, that's like not filling out your TPS reports. Pragmatically it doesn't seem like fun but you need to take quality assurance and correct procedures and practices into account, or it will bite you hard down the track.
Namely, don't *hide* your vulnerabilities, *fix* your vulnerabilities. That's why I started this whole rant. Linux shouldn't be secure because people don't know anyth
Re:This is senseless (Score:1)
I RTFA, and I agree that it wasn't the greatest piece comparison in the world.
I read you post, and I'm sick from the faux pas that you're using. EW, GROSS. Seriously, you're comparing a USELESS OS (windows 3.11) with the most useful OS (linux, I know that some things such as video editing are lacking, but all around, it is the most practical). And you're expecting me to draw a security comparison? Please. I would consider comparing OSX (quite a useful piece of OS) and maybe windows XP or 2003 (modern
Re:This is senseless (Score:2)
What disturbed me about the article is that the same points he was applying to Linux regarding security also applied to Win3.11 and OS/2. It's obscure, therefore it's secure. This is foolish and dangerous thinking. It's exactly the same kind of justifications Microsoft uses for selling their OS.
Linux is more secure simply because the open source nature of the so
Re:This is senseless (Score:1)
Ahh now you make much more sense, and i see your gripe with the article (i will add it to my long list of gripes with the article).
A more useful test would be to observe how quickly the box would be compromised if the assailants were specifically targetting the box and knew exactly which OS it was running, what patch level, and had the correct tools available to use it.
Interestingly, what [macdiscussion.com] you [ftponline.com] suggest [attrition.org] has already been tried and [slashdot.org] dismissed [slashdot.org] by the infallible moderators of slashdot. Case dismissed. NEXT! :)
Re:This is senseless (Score:1)
short on details (Score:2)
I left linux for bsd since I consider it more secure. linux is great, but it is a popular attack for kiddies. so far [knock disk] bsd has been spared such, uhm, 'popularity'.
I would bet a similarly configured bsd box would last longer than any of them.
Why unpatched? (Score:3, Insightful)
Re:Why unpatched? (Score:1)
This just isn't logical and it pains me to see that people get paid to waste thier time on somehting this moronic, or, that I am not one of the people getting paid to waste my time. It's one of those, I'm sure.
-S
Unpatched Linux Lives 3 Months on Internet (Score:3, Funny)
I've seen this (Score:4, Informative)
Last time I moved I set up my laptop running Win2K on my new DSL connection without a firewall. It was just for 5-10 minutes or so, to set up the connection. Within those few minutes, I managed to pick up a worm. This was even with most of the latest patches already installed.
Firewalls/NAT greatly cuts down on your risk. Running firefox pretty much gets rid of the rest. But if you put Windows on the internet without a firewall and you're not a security expert who has done a thorough audit of your machine, you're asking for trouble.
Re:Tell me... (Score:2)
If you have any evidence of a 'fully patched windows box' on the internet, please post an ip address.
Re:Tell me... (Score:1)
"However, we did have two Win32 honeypots in Brazil online for several months before being compromised by worms."
and it you read the techweb article you would have read
"Windows XP SP1 with the for-free ZoneAlarm firewall, however, as well as Windows XP SP2, fared much better. Although both configurations were probed by attackers, neither was compromised during the two weeks."
Why would I post an IP address? So I can have my network disrupted with a flood of att
Re:Tell me... (Score:1)
Re:Tell me... (Score:1)
this is nice, but... (Score:1)