Free Republic
Browse · Search
News/Activism
Topics · Post Article

Skip to comments.

Flaws raise red flag on Linux security
ComputerWorld ^ | JANUARY 09, 2004 | Jaikumar Vijayan

Posted on 01/10/2004 12:20:46 PM PST by Bush2000

Flaws raise red flag on Linux security

But many users remain confident about the security of the open-source environment

Story by Jaikumar Vijayan

JANUARY 09, 2004 ( COMPUTERWORLD ) - A report earlier this week about a critical flaw in the Linux kernel was the latest in a series of recently discovered security problems with the popular open-source operating system. But many users were unfazed by the report and said Linux remains a solid and secure environment for running enterprise applications.

Poland-based iSec Security Research on Monday said it had found a critical flaw in a function used to manage virtual memory on Linux systems (see story). The flaw affects the 2.2, 2.4 and 2.6 versions of the Linux kernel, according to iSec.

The vulnerability could allow attackers to take administrative control of compromised systems and run attack code of their choice, an iSec advisory stated. ISec claimed that it had developed and successfully tested code that was capable of exploiting the flaw, although it added that actually launching such an attack wouldn't be easy.

The news follows the discovery of a similar flaw in the Linux 2.4 kernel last fall. In November, unknown attackers used that flaw to take down several servers belonging to the Debian Project, which produces a noncommercial Linux distribution. And last month, an attack on the Gentoo Linux Project compromised a server that was being used to download copies of Gentoo's Linux source code by users.

The rise in such incidents can be attributed to Linux's growing popularity, which makes it a more attractive target for malicious attackers, said David Wreski, CEO of Linux security vendor Guardian Digital Inc. in Allendale, N.J.

"The underground hacker community is very interested in Linux as a potential target," he said. "Because of the accessibility of the source code to everyone, it provides an equal opportunity for malicious attackers to find vulnerabilities and ways to exploit them."

Even so, Linux remains a secure environment, said John Cahill, senior network security engineer at Piedmont Natural Gas in Charlotte, N.C.

"I would say it is more secure than Microsoft and other environments because the code is looked over by so many people and it's so widely available that any vulnerabilities can be quickly identified and patched," Cahill said. Piedmont uses Linux for several e-mail-related functions and is considering its use for antispam purposes.

"There's not very much we've needed to do to secure Linux [applications]," said Joe Poole, manager for technical support at Boscov's Department Stores LLC in Reading, Pa. The company runs several virtual Linux servers on its mainframes that are protected by network and internal firewalls. All nonessential services, such as file transfers and Telnet, have been disabled. But there has been no need for the kind of constant patching and maintenance required for Windows, Poole said.

Linux distributors in general are also doing a better job of shipping products that have nonessential services disabled by default, said Paul Schmel, adjunct information security officer at the University of Texas at Dallas.

"The biggest plus that Linux has is that it's designed to allow users to be users and not administrators," Schmel said. "What Linux has that Windows doesn't have is ease of configuration from an administrator's standpoint. Stopping and starting services, configuring services to only respond on certain ports and interfaces is dramatically easier than it is with Windows."


TOPICS: Business/Economy; Culture/Society; Front Page News; Technical
KEYWORDS: computersecurity; linux; lowqualitycrap
Navigation: use the links below to view more comments.
first previous 1-20 ... 81-100101-120121-140 ... 181-186 next last
To: Bush2000
If the flaw is a buffer overflow, then that is most likely a compiler issue, and will affect any software, even windows.
101 posted on 01/11/2004 7:37:07 PM PST by ElectricRook
[ Post Reply | Private Reply | To 8 | View Replies]

To: Bluntpoint
this is coming at you out of a Lindows 4.5 box on a hme network of 4 lindows 4.0 or 4.5 boxes, on a Netmax server. All plug n'play, easy setup, clan install. We are Windoze free with Open Office.
102 posted on 01/11/2004 7:41:00 PM PST by mo
[ Post Reply | Private Reply | To 48 | View Replies]

To: antiRepublicrat
We didn't really have that problem with the Sun, HP/UX and Linux systems.

Because nobody runs Sun, HP/UX, and Linux boxes as desktops. If you run them in any other role other than a server, people will start having similar issues.
103 posted on 01/11/2004 8:22:23 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 94 | View Replies]

To: antiRepublicrat
This is an overly extreme solution too often suggested by Linux zealots.

You don't have to look too hard to see the folks who recommend this kind of nonsense almost constantly.

But in this case only a partial move away from Microsoft is necessary -- dump both and use Mozilla. Wait, you can't dump IE, oops. But you can cut your exposure a bit by at least not using it.

You can certainly disable IE with the "Set Access and Defaults" tool.
104 posted on 01/11/2004 8:23:59 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 99 | View Replies]

To: ElectricRook
If the flaw is a buffer overflow, then that is most likely a compiler issue, and will affect any software, even windows.

No. Buffer overflows are generally overt programmer errors, where somebody has allocated a stack buffer which is insufficient to accomodate a sequence of data.
105 posted on 01/11/2004 8:26:09 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 101 | View Replies]

To: Bush2000
You can certainly disable IE with the "Set Access and Defaults" tool

You can disable use of IE to browse the Web, but the bug-ridden components are still there in use by other applications.

106 posted on 01/11/2004 8:53:22 PM PST by antiRepublicrat
[ Post Reply | Private Reply | To 104 | View Replies]

To: Bush2000
Because nobody runs Sun, HP/UX, and Linux boxes as desktops. If you run them in any other role other than a server, people will start having similar issues

We had it lots on Windows servers too.

107 posted on 01/11/2004 8:57:45 PM PST by antiRepublicrat
[ Post Reply | Private Reply | To 103 | View Replies]

To: Bush2000
Practically nobody buys Windows retail and installs it themselves.

I'd better tell Best Buy and Circuit City to get rid of all those copies.

The installer is able to create a lower-privilege account at any time.

For average user desktop systems, the installer usuall won't run at a lower level account because they don't provide enough privileges, that is if that user even knows other types of privilege groups exist.

they know from experience that having a user run as a lower-privileged user will result in a greater number of support calls when the user tries to install ProductA, discovers that ProductA won't install, and calls Dell/etc asking why they can't install ProductA.

Yet on a Mac, users get it out of the box with an administrator account that can do almost everything any user could want to do, and without support calls. But yet they still don't have root access which equivalent to the Windows administrator level. Windows privileges are poorly designed.

Linux is the province of geeks only. Practically no desktop users are using it.

I wouldn't give my mom a Linux box either. But Mac is brain-dead easy to use for anyone, and it has the same privilege system and shares a lot of the components found in Linux. What about that? Would you say a Windows system out of the box is more secure than a Mac system? Why?

108 posted on 01/11/2004 9:13:26 PM PST by antiRepublicrat
[ Post Reply | Private Reply | To 92 | View Replies]

To: Bush2000
I'm not surprised you don't know what's running on your servers.

In a large diverse organization with multiple management angles and funding channels spread about a continent, it's hard to know exactly what everyone is running. We found them by scanning.

BTW, my comment about accidental IIS installation was mainly for desktops.

109 posted on 01/11/2004 9:16:18 PM PST by antiRepublicrat
[ Post Reply | Private Reply | To 93 | View Replies]

To: Bush2000
Buffer overflows are generally overt programmer errors, where somebody has allocated a stack buffer which is insufficient to accomodate a sequence of data.

But better compilers will catch possible buffer overflow situation. Everyone's right, in a sense. That's why Microsoft not only reprogrammed much of RPC for XP SP2, but also used a better compiler.

110 posted on 01/11/2004 9:19:27 PM PST by antiRepublicrat
[ Post Reply | Private Reply | To 105 | View Replies]

To: Bush2000
IIS ain't turned on by default -- and it's used by servers (not desktops)

My XP machine is running IIS, although it and the related services are stopped because I don't need IIS except for when I'm doing Web development on that machine.

111 posted on 01/11/2004 9:31:42 PM PST by antiRepublicrat
[ Post Reply | Private Reply | To 85 | View Replies]

To: Bush2000
The Shatter class of attacks are inherent windows architecture problems. Have you heard of them? Very interesting stuff, from an IT security perspective.
112 posted on 01/11/2004 9:37:14 PM PST by adam_az (Be vewy vewy qwiet, I'm hunting weftists.)
[ Post Reply | Private Reply | To 23 | View Replies]

To: antiRepublicrat
You can disable use of IE to browse the Web, but the bug-ridden components are still there in use by other applications.

The IE attack is not really a threat because it is predicated on a user/app browsing to a malicious web page. Since the likelihood of that possibility occurring approaches zero, no threat. Nice try, though.
113 posted on 01/11/2004 10:41:39 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 106 | View Replies]

To: antiRepublicrat
I'd better tell Best Buy and Circuit City to get rid of all those copies.

Yeah, and they're just flying off the shelves like hotcakes, right? /SARCASM

Not! Are you seriously denying that the vast majority of people get Windows preinstalled with their machines (and thus don't pay retail or install the software themselves) -- or do you not understand the term "practically nobody buys Windows retail and installs it themselves"?

For average user desktop systems, the installer usuall won't run at a lower level account because they don't provide enough privileges, that is if that user even knows other types of privilege groups exist.

That poor choice has nothing to do with the design of Windows.

Yet on a Mac, users get it out of the box with an administrator account that can do almost everything any user could want to do, and without support calls.

Yeah, yeah, yeah. As I pointed out in previous posts, it's an OEM choice. Apple produces OSX. It is the OEM. Consequently, I'm not surprised that Apple preconfigures its machines with appropriate accounts. But blaming Microsoft for Dell or Gateway's failure is just BS -- and you know it.

I wouldn't give my mom a Linux box either. But Mac is brain-dead easy to use for anyone, and it has the same privilege system and shares a lot of the components found in Linux. What about that? Would you say a Windows system out of the box is more secure than a Mac system? Why?

Whether something is more secure "out of the box" is a worthless consideration -- because, to be useful for the average user, the machine needs to be configured. For Apple, "out of the box" means Apple has preconfigured the machine to its specifications and delivered it to the user. For Dell or Gateway, "out of the box" means Microsoft gave them the OEM discs, Dell or Gateway preconfigured it (inadequately, as I've said before), and then delivered it to the user. Thus, out of the box is only useful if you accept the proposition that the OEM adequately configures the OS.
114 posted on 01/11/2004 10:54:00 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 108 | View Replies]

To: Bush2000
. . . would result if users were running at lower privilege levels and couldn't install aftermarket software.

I think I have told you before that on an OSX platform one does not have to have the equivalent of Windows Administrator access to install aftermarket software. Windows Administrator access does not equal OSX Administrator level.

115 posted on 01/11/2004 11:22:47 PM PST by Swordmaker
[ Post Reply | Private Reply | To 54 | View Replies]

To: adam_az
The Shatter class of attacks are inherent windows architecture problems. Have you heard of them? Very interesting stuff, from an IT security perspective.

Not really. In order to execute these kinds of attacks, you need to get code running on the box in question. Since you have no practical means of forcing me to run your malicious code, it's not a credible threat. Nice try.
116 posted on 01/11/2004 11:23:06 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 112 | View Replies]

To: Swordmaker
I think I have told you before that on an OSX platform one does not have to have the equivalent of Windows Administrator access to install aftermarket software. Windows Administrator access does not equal OSX Administrator level.

Irrelevant, Mac boy. Read the thread: Windows security profiles allow you to create user accounts with arbitrary privilege sets.
117 posted on 01/11/2004 11:24:31 PM PST by Bush2000 (tro)
[ Post Reply | Private Reply | To 115 | View Replies]

To: Bush2000; Anti-Republican
Of the advisories, only 7 are remote exploits; the rest depend upon an improbable chain of events, such as (a) browsing to a malicious webpage in IE or (b) running a malicious piece of software. Which means that practically no users are affected. Nice try, though.

This is so funny, Bushie. You seemed not to understand us when we were pointing out an even greater improbable chain of events when you were crowing about a "security issue" in Mac OSX!

Just how many pieces of "malicious software" are there for Windows? How many spyware programs invade Windows computers and run without their owners' permissions? Hilarious!

118 posted on 01/11/2004 11:27:42 PM PST by Swordmaker
[ Post Reply | Private Reply | To 55 | View Replies]

To: Bush2000
Certainly having a default administrator setting for a user is an issue -- but it isn't an operating system design flaw. OEMs configure these machines.

Gee... just the other day you were howling about a single OEM configured default setting on OSX that, in your opinion, was a "Critical" security issue, that might, after an extremely improbable chain of events, allow a local area user access to root level... and that, according to you, was a heinous flaw in the OS!

Suddenly SEVERAL flaws in WINDOWS are not "an operating system design flaw!"

You, Sir, are again hoist on your own petard!

119 posted on 01/11/2004 11:33:49 PM PST by Swordmaker
[ Post Reply | Private Reply | To 54 | View Replies]

To: antiRepublicrat
oops... I think I pinged the wrong anti to a reply two before this...
120 posted on 01/11/2004 11:40:27 PM PST by Swordmaker
[ Post Reply | Private Reply | To 62 | View Replies]


Navigation: use the links below to view more comments.
first previous 1-20 ... 81-100101-120121-140 ... 181-186 next last

Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.

Free Republic
Browse · Search
News/Activism
Topics · Post Article

FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson