29 replies
by dynoe
by leehellcat
I agree, unless you are prepared to part with some serious money, or dabble with Linux than IIS id your only real choice.
As for IE, it comes with Windows and almost every user has it installed at home, so they are familiar with it. You would need a good argument to purchase a seperate Browser. It's similar to buying new wheels for a car that comes with a perfectly functional set of round wheels. It only appeals to people who want to be different or make a statement.
As for security, no software is 100% secure, or otherwise Hackers would never have got started, and I'm confident that Microsoft products are no worse than any other, they just get more flack for it that other companies because of their market dominance.
by dave howe
by debunker
The Xitami web server is quite good - the base version is free and the pro version (with SSL and enhanced logging) is about $100, if I remember correctly...
On the client side, Opera works very nicely and the improvements in both security and functionality make it worth the $20 or so they want for turning of the ad panel in the freeware version. Sites that reject non-IE browsers can frequently be fooled by using Opera's option to have it identify itself as IE5. This still won't help you with sites that use Microsoft's bastardized incompatible Java implementation, however. Which is exactly what Microsoft wants.
by alphaa10
What do you think all the uproar is about, if
not the DYSfunctions of IE and IIS? This is not
perfectly functional.
Does this mean alternatives are flawless? Of
course not. Hackers have an appetite for any OS
oles, regardless, and most Linux and other users
do not insist theirs is perfect.
But in terms of cost of needless overhead,
needless licensing restrictions and needless
expense, a lot of former Microsoft customers are
giving renewed and serious looks at the
alternatives. Which of late they are getting very
competitive, even without referencing the list of "needless" MS faults, above.
by dave howe
IIS and IE (particularly the latter) are worth every penny to microsoft. by making both the scripting language for IIS and the "extensions" for IE as non-standard as possible, Microsoft have produced a whole generation of websites that just *can't* work unless running on microsoft-os servers, and viewed using a microsoft-produced browser only available for microsoft-os workstations.
Microsoft would have gladly paid for Dreamweaver and similar packages to default into using IE extended properties, so it was a happy coincidence that they provided this for free....
by duane pelkey
by carock
by oceanhai
The OS and the Applications need to be secured, through total rewrites. It will take a radical re-engineering to do this.
Until Microsoft can layer their OS security so it no longer automatically exposes application automation services, that canbe launched at will by remote servers, their OS will always be too insecure. MS OS gets picked on for two major reasons: highly availabilty and the richness of exploitation opportunities.
MS Applications are bringing in their own barrels of problems. Office replaces 150 system OS DLLs with it's own, and IE, and now MSN, has become tightly bonded into the OS. This all increases linkage to the web. This degree of 'integration' also presents the primary points of exposure. Exposing everything to the web, few questions asked, is a very insecure way to operate. It seems like vaunted security features, like Zones, always include bypasses -- all numeric URLs, the cross-domain MSN GUID cookie passing.
Contrast this to BeOS or Unix operating systems which layer and partition what is allowable for applications and operating system to do.
There's plenty to say about this, but I have to imagine Longhorn will have to be a radical change if MS actually hopes to come up with a realsecure option.
by spikeymike
You are Naive to think that the security vulnerabilities constantly found in Microsoft's products are due to their market share. Don't you realize that people HAVE poured through Apache's SOURCE CODE???
These holes found in M$ products are being discovered at an alarming rate, without the benefit of reading its source. For every 1 flaw discovered, I'll wager there are 100's more yet to be discovered.
If the source code was closed for these other products, then I might agree with you. But since hackers have access to the source code - your argument does not hold water.
-Mike
by bnordberg
I think too many people are making these arguements without looking at the big picture. Any OS I have worked with (Linux, IRIX, Unix, AIX, Windows, OS X, Mac OS, OS 400) has required security patches as soon as anything with real functionality is added to it that opens it up to the world. Look at Apache and SSL. The big question we need to ask is: Is the functionality worth it? Do we really need people to access our information over the web. Do vendors need to store our credit card information.I personally would rather enter my credit card information each time I make a purchase rather than having the vendor store it for my convenience and make it accessable over the web. Do we really need customized web site that require us to login and that have personal information stored on their backend.
I question much of the functionality I see out there. The whole I.T. industry needs to step back and analyze, just because something can be done does not mean it should be done.
by netrx
Agreed.
But the question is not only do we really need all this added functionality but do we really need to take on the EXPENSE of owning all this 'functionality'. Each time some proprietary new 'function' is added we seem to take 2 steps backward in the compatibility arena, i.e. chipset incompatibility, OS incompatibility and incompatibility with similar competitor software.
In addition to incompatibility costs, the cost of ownership, training and even the base OS costs soar. (I wonder if the price of $250 for full version XP Pro is what the original Bill Gates had in mind when he set out to make computers 'affordable' for everyone...I think that somewhere along the line, he has lost his vision).
Along with new 'functionality' also comes higher programming complexity...which brings us to the point where we are today...even Microsoft's own products won't run in unison because the versions of all the installed applications are out of sync or they were just released full ofbugs. Now we need more expensive service agreements, and a staff 100's of techs to babysit these increasingly fragile repositories of possibly misguided 'functionality' and to combat the blue screen of death.
I wonder why we aren't all just running out and buying XP like hotcakes for thousands of PC's? Hmmm...perhaps it just takes some creative Enron accounting to make it happen and then in a year or so we'll all be out of business and won't have to worry about it any more. Or maybe we can just lay off a few hundred more IS people to pay for it and outsource the troubleshooting?
by bmfraley1
Although low-key, this is still simple MS Bashing. Apache and all the others have bugs that can be exploited. When a bug pops up in IIS/IE it's usually only a matter of days before it's corrected.
The REAL problem with security in MS products is when they are put in the hands of people who are not specialists with MS products.
by alphaa10
Apparently, this article made you see "MS
bashing", but not all bashing is undeserved.
Maybe all the rancor should alert you to
something about the product itself, rather than
lead you to try to bash the critics by sneering
they are not sufficiently "specialist" with the
products they were sold. If some admins seem to
play Pollyanna with their required patches,
plenty of others have legitimate complaints
based on matters-- unpatched-- intrinsic to the
product.
Most OS communities try to correct errors, and
most admit to having them. But the sheer volume
of problems coming from Microsoft is only
gasoline to the fires of discontent from
other MS practices stemming from its basically
cavalier, monopolist attitudetoward the mass of
users, and the admins you dismiss as amateurs.
Microsoft sometimes 'fesses up to having
"already known about" some obscure flaw only
days after a user posts the problem somewhere
on the net. Microsoft has been caught in denial
multiple times-- the raw sockets issue is one
example of many.
The very existence of the MS patching machine
for Windows Update shows the process of fixing
MSware has become so hideously complex, only
an admin with no life of his own could stay on
top of it. And even following MS instructions
will occasionally get you into trouble, as it
did last spring when the Windows Update
Patching machine went bonkers.
by talleywho
While Apache is not bug free, it us uhh...free. So, the real problem is IIS costs tons of $$, when a free alternative is just as good (arguably better).
The thing that seemed to have got lost is that a bunch of IT people saw a fast food solutionin MS and to ease their job recommended it to their boss. Through the marketing powers of MS, these corporate suckers blew all of their cash on the software.
I guess no one has heard of cost/benefit analysis.
Regarding putting MS products in the hands of people who are not specialists...many of these people happen to put MCSD by thier name.
by cnd
Whether or not it's worth it to Microsoft is not an issue to me - they have successfully closed me out of their loop of user input. This is a horrendous misuse of a Spiral Model or Concurrent Engineering software life cycle model, much less bad P.R.
IE is embedded deeply in XP. Therefore bugs in IE make XP unstable - there is no denying this, and I find arguments to the contrary somewhat lacking when it comes to the bottom line: Actual usability.
Recently, I've had 6 XP machines of friends come to me (doesn't it stink when you're the computer guru in the group) - all users have assiduously downloaded every single little patch. SP1 sent 2 of the systems - Dells - into reboot lockup. The remaining 4 have had all sorts of problems related to IE 6 - to the point where, yes, maybe XP is stable, but one could not use Office XP/2000... Even Norton was having the problem.
No. XP is NOT a stable operating system, and it does not cater for the masses who do not have broadband. Microsoft, as usual, released too early - and now they are paying the price.
Do I care whether MS can afford anything? Certainly not. They've done an outstanding job of bringing PCs to the masses, but now they have unceremoniously dumped them into the laps of their users in the hope that the users will catch up.
If, in fact, suicide is painless, then why do I keep seeing Microsoft twist under it's own knife?
Sad. Now, if you'll excuse me, I have to help a company port their databases over to Linux.
by dlw6
Bottom line: Vote with your dollars. If you don't like MS products, buy something else, but don't continue to use MS products while complaining about them. And, for the record, I agree with the article that MS made a mistake to bundle software and try to provide a software product for every possible need.
Sites that reject non-IE browsers aren't worth visiting, are they? I haven't heard of such a site, but then I use IE browsers (out of laziness) so I wouldn't know.
Like the author of the article, I set my security pretty high, and when I encounter a web site that can't provide public-access information without using active content, my usual answer is "either they don't want my business, or their product is weak and needs to bepropped up with flashy visual effects," and go somewhere else.
Good fortune,
Don
by talleywho
I tell you, the cloth over some of you Winblows admins eyes is just hilarious...what are you talking about IIS being the "standard"?? Apache rules the roost, look at the numbers!
http://www.netcraft.com/survey/
Apache owns around 65% of the market, while IIS has ONLY approx 25%. Does that seem to tell you that most admins say IIS is NOT worth it? I'd say so.
by kijanka
The question posed by this article ("Are IE and IIS worth the trouble for Microsoft?") lacks historical perspective. When Netscape was making a *big* splash, around 1996, it was becoming clear that the NS server/browser suite and Netscape ONE provided the basis of a cross-platform operating system shell. As the article states, Windows is one of only two of Microsoft's cash cows. With Windows' marketplace dominance threatened, Microsoft acted to defend its turf. The Microsoft imperative was,therefore, to kill Netscape at all costs, and that meant competing on Netscape's playing field. Even though Microsoft's early efforts were highly inferior to Netscape's existing offerings, Microsoft persisted and overcame Netscape's lead with a combination of improved technology and marketing shenanigans.
Microsoft would be a very different company today if Netscape "owned" the internet. It's laughable to suggest that Microsoft would have been better off had they adopted a "hands-off" approach to the internet.
by alphaa10
I quote your comment below, which itself shows lack
of historic perspective-
"When Netscape was making a *big* splash, around 1996, it was becoming clear that the NS server/browser suite and Netscape ONE provided the basis of a cross-platform operating system shell... With Windows' marketplace dominance threatened, Microsoft acted to defend its turf. The Microsoft imperative was, therefore, to kill Netscape at all costs..."
And I respond... briefly
Netscape's server and browser offerings were
indeed cross-platform, but that fact is not
implicit hostility or doom to any company committed to true market competition. Cross-platform includes
Windows users. Cross platform does, however, threaten the empire of a monopolist, and killing Netscape or any other rival "at all costs" is sufficient proof of a core MS ethic which is anti-marketplace, criminal and un-American.
To presume as you do that Netscape would have
been the Next Monopolist if given the chance
is the mindset of every totalitarian, who cannot
conceive of any regime format but tyranny and
presumes everybody else is a covert wannabe.
by netrx
Hmmm...let me ponder this question for a nanosecond....
NO!
by alphaa10
IE and IIS are magnets for trouble from hackers
and MS, itself. MS not only botched the creation
of patches, but "unfixed" the fixes it urged us to
install. XP improved some things, but only to
highlight the old problems, some of which
continue in XP and some of which are entirely
new.
Is anyone else even close to this kind of record?
We are not on the MS payroll and should not
have to put up with it. MS cannot pride itself for
finally solving problems it created and shovedour way, and cannot hoist the lame excuse its
software is buggy because it's software. They
turn the rest of us into unpaid beta testers, at
our own time and expense.
Now that the threat of legal action is finally in
low profile, MS shows little sign of being either
more competent or customer friendly. Look at
MS licensing, if you want a bellweather of its
future behavior, now that it believes it has
the world by the operating system. By the new
MS subscription model, and with the naive
public perception there are no alternatives, MS
can turn the screws as tightly as it wants.
Professionals avoid doing business with
organized crime and these convicted monopolists
deserve something besides reproach. Smart
adminsare getting away from the MS
merry-go-round as fast as possible. All the
others listen to MS sales pitches, throw up their
hands, and tell budget and accounting Microsoft
is the only game in town. They are in over their
heads, already, anddon't know it.
IIS: Not worth the trouble. I have had to maintain both IIS and Apache in small installations. Apache was far easier to lockdown and maintain and patch and scale up. There are other choices as well, but some those web servers have more or more serious known holes than either IIS or Apache. Always investigate your choices.
IE: For me I have no choice. I do have a handful of sites which ONLY work with IE, spoofing the browser ID does no good. Some examples of IE ONLY sites: my company's timesheet application, my company's contracted professional developement training application, many of my financial service provider's online access, Microsoft's knowledgebase and critical update portals, etc, etc, etc.
On top of that many Windows apps use IE's HTML rendering engine, like MS Outlook, MS Office, MS Money, TurboTax, StarOffice 5.2, Quicken, and other non-MS and Open Source apps.
Because of this I keep IE around fully patched. I do use another browser for everything which doesn't require IE. IS IE worth it? Barely, and only because I have to.
by frankb
First - MCSDs are developers. Many know little or nothing about system administration. These certs are often worthless as well. Many just indicate how well someone memorized Transcender answers. It's unfortunate because many people work hard on these. I once interviewed a guy with a MCSE who couldn't tell me what an IP netmask was. Certs mean very little in reality.
Second, Open source is WAY out in front of Microsoft in volume of problems. Microsoft has released 43 patches in 2002. Redhat has released 80. Debian over 100. SUN released 68.
Apache may be free but you have to run it on something. If you run it on Linux, it doesn't cost much but then you have to deal with the patch volumes. If you run it on Windows, you're just not thinking. IIS comes with Windows at no extra charge. It is simple to administer and it flys. Every version of IIS gets better too. If you pay for Windows and then go to the extra trouble of running Apache there because you think it's moresecure, I would contend 1) you're wrong and 2)you spent more in admin time to make it work than you know. If you didn't pay for Windows and you're running it anyway, you're part of a different problem.
Microsoft stuff works and works well. Whenmanaged by people who know what they're doing, it is as secure or more secure than ANY open source environment.
by frankb
by talleywho
you think that the fact that MS has released fewer patches is a good thing??
LOL
you could also view this as the open source community being more proactive in creating patches for their software products, while M$ sees every patch as somethingthat hinders their bottom line (the mighty dollar), and only necessary when the situation demands (they exploit has been found and publicized).
this is my last post in this forum, take it for what you will.
by spikeymike
This discussion is closed to new replies.
Trending Security posts
Sort by Trending