Ooops....Looks like the issue rears it's ugly head in Mozilla 1.5.1 as well---sort of..
Ok..it's not a strictly Microsoft related problem--perhaps it's in all browsers?
The only way this vulnerability works from within an email application is if you are using browser based e-mail, or Outlook Express to access your corporate mail.
The worse possible scenario was posted to NT BugTraq by Russ Cooper, where it *might* be a consumer issue if it were exploited in the financial realm. Even there, it was reasoned that most of the security (SSL, CA, etc.) used by Financial Institutions mitigates the entire realm.
Is it a problem? Of course.
Should Microsoft fix it? Of course.
Should they take care not to break anything else? Of Course..
I don't believe the original poster was saying anything about being 'elite', he was simply making a point. I, too, use IE daily at home and at work, and have never suffered because of it.
Yes, I keep things patched, yes I am firewalled, and yes I follow the security discussions, but I know others who are not as diligent as I am and have not suffered either.
To those who would sing the 'open source' song--let me remind you that just like Microsoft, you too are under attack by the legal hounds. Personally, I hope SCO loses, but at the end of the day, he who has the better lawyers will win, regardless of 'the truth'. Yes, I'm cynical about our justice system--moreso when it comes to the arena of litigation. When someone wins millions because they were stupid enough to put coffee (a beverage usually served hot--not lukewarm, not cold), between their legs in a moving vehicle and get burned because of their irresponsibility, then there is no such thing as justice.
Read John 3:16; meditate on what an act of Love it was for a Father to allow his own son to die--to be the final sacrifice for humanity.
Satan loves to hide himself; cloaked in that which is 'mysterious'. I went down that path; all I found was frustration. Salvation with God at the Center of my Life has brought me happiness and joy and prosperity.
At issue here is TCO, and unfortunately, TCO isn't limited to simply how much it costs to use, train, deploy, and support an application. There are other problems that need to be addressed; from internal customization of applications to patch management and OS updates.
Let us look at MS-Office as an example. While Open Office affords us the ability to be about 90% compatible (I have personally seen issues with conversion from/to MS.doc format), it's the other 10% that drives TCO through the ceiling. This is inflated by the use of Macros and VBA code within documents, spreadsheets and databases (BTW--I have yet to see an adequate Open Sourch replacement for Access. If anyone does know of any, please feel free to correct me.) and this use of Macros/VBA Code is where the real problem lies.
I know that we should *not* be using VBA code, but many users do--especially Excel Superusers; and this problem exacerbates the Open Source -vs- Microsoft Debate. This isn't limited to internal users, either. Many, many vendors and external users compound the issue beyond any hope of rational solution.
TCO is also exacerbated by the land of the 'instant MCSE' ( I relate those to the US Navy 'Pushbutton Petty Officers'.). Like the Pushbutton PO, they lack the experience needed to think in terms of both how to do things the right way (not necessarily a Microsoft 'Best Practice) and the secure way. This type of thinking only comes with a lot of experience in IT, and you don't get that in 9 months of night classes and some testing software to get you through the tests.
Security training to M$ admins is also an afterthought--although it is improving--and is a real sore-spot. With Unix/Linux, you have to know networking and security, but with Microsoft, you don't really need to know it. A recent editorial in MCP magazine proposed a Board-Certification for Network Engineers. You would start with the MSCE..then you would take a hands on test (like the CCIE) and follow that up with an oral examination by a board of your peers. This is designed after the Certification processes many other professions use, from Nuclear Engineers, to Doctors. I would love to see this become common practice--for all forms of Network Engineer, from Microsoft to Linux. Even Sun, HP and IBM could adopt it. Or, switching gears, make it independent of any vendor, but use a vendors own 'Network Engineer' level of certification as a basic starting point.
Microsoft is not the enemy here, the real enemy is apathy. Apathy by the Board of Directors, the CEO/COO, CIO/CFO, the Admins, the End Users, and by programmers who develop the applications. Even using an Open Source or Unix solution is still NOT the Holy Grail. Patches for Unix OS's and associated software are still required, and they still *might* break your application and thus must be tested. The sad thing is that many organizations, regardless of their solution choice, do not take the time to be aware of proper Patch Management techniques. They don't know about or are too cheap to invest in a "Production Test Environment"; where you model your Production Environment and test patches prior to deployment. Most often these monstrosities require at least their own managers, with cross-level support throughout the organization--from Operations to IT. However, in large organizations, this can be a full-time job for an entire team; because if they're not testing the latest vendor patch, they're testing developed applications, and this all adds to TCO.
While a Unix/Unix-like solution may be the lowest TCO for one company, for another it may well be a Microsoft solution, or a Novell solution, or some other solution we haven't seen yet. One thing for certain--as long as people are in the mix, the TCO will never be completely free.
Robert Heinlein said it best TANSTAAFL or There Ain't No Such Thing As AFree Lunch
If you are using a Win2K/2003 environment, then use Group Policy instead of handing out passwords. Give some adminstrative responsbility to 'tech-savvy' members of a department to perform simple tasks, such as password resets; new user creation or changing file/folder permissions. Create a Taskpad, install the adminpak on the users workstation, and show them what to do.
Drat..now I can't tell the (L)users that they need to wait for tech support to come by and replace their keyboard, and that they'll need to find another means to work until then. How does next Friday at 1pm sound for an appointment?
Even exposing contact information for a business is questionable. If you're working on penetrating a company, then this is a stop on the highway. But, without that information, then (as one poster stated) the FBI would have to get us the information we need to prosecute spammers or etc.
I don't know what the answer is either; I don't think it's simple either. This may be one (of many) invasions of our privacy we have to deal with. Banks, Mortgage Companies, Credit Cards--these all sell our information to other companies. It's sad, but this is big business, and it makes money. Utilities provide information to Local, State, and Federal Agencies all of the time; and are required to by law.
Our information is not private anymore, and hasn't been for a long time. Everyone has their hand out for it.
Actually, the number one distraction is Conversing with passengers, followed by Eating, then Reaching/leaning for things. Cell phones were a distant 8th--even behind dealing with children and reading. This data comes from a study by the University of North Carolina, and found on cnn.com
Here's the URL: http://us.cnn.com/2003/TRAVEL/08/06/distracted.dri vers/
I have actually seen people reading novels while driving down the interstate, and reading the newspaper, with it spread across the windshield.
The biggest distraction with cell phones is dialing numbers--I use a hands-free headset and voice dialing. I don't have to look at the keypad.
I haven't bought a CD since Dark Tranquillity - Damage Done which I think was late 2002.
I only support bands I like--the amount of crap on the airwaves promoted by the Recording Industry is nauseating. Most often, I'm found checking out bands at local music venues, and either buying their CD's or buying compliations of local music put together by local radio.
For one reason or another, things are different in the Windows world.
Yes, things are different in the Windows (Simplified) World. In the Windows World; you buy PC XYZ from company ABC complete with Windows. You unbox it, turn in on, and let the 'magic' do its' thing. There's no muss, no fuss and I've got a working PC. Oh, never mind that the OS isn't patched with the latest patches--the average home user doesn't know (or understand) that it needs to be--regardless of the media coverage of worm/virus Qbert. The average home user is NOT technically inclined. Therein lies the source of the problem--lack of sufficient instruction, which is the delegated responsibility of the OEM System Builder.Consequently, every little bug gets passed along, and we end up with MSBlaster type problems.
In the Linux world; the average user is technical, or has had the system set up by someone technical. They take care of the system, understand how to patch the system and ensure that it has been patched. For this reason, problems are short lived.
We live in a simplified world. From fast food; disposable diapers, razors, etc.; to all-in-one super stores; everything is simplified for us. I don't have to know how to make Veal Scallopini; I can buy it pre-made at the grocery. We want everything easy, because we don't want to take the time top do otherwise.
Granted, this is an oversimplified view. I didn't factor in regression testing of patches at the corporate level in order to ensure that the new patch doesn't break something else in use, due to the tight integration of code with the Microsoft OS (unlike Unix/Linux Applications). This takes time (stakeholders and their ilk tend to be a testy when their application breaks) and may result in infection before testing is complete. The point is people have been brainwashed into believing that computers are simple, when in fact they require a lot of attention, like a toddler or a puppy.
How did we do things without computers before? I know..paper and pencil. At least there we didn't have to worry about viruses--unless it's a cold. LOL... Maybe regression is a good thing this time?
No, 1102--you forgot the two boxes the geeks at VA Tech bought to test the environment. And lest you think Apple provided them for free; how do you think the group proved they spent the grant money? Think about the professor in 'Real Genius' for a minute.. LOL..
The rules say you can't have alcohol in the dorm, or pets, or whatever, yet you abide by those. University Computing Services is responsible to all of the students, not just you.
If you don't like the rules, no you don't have to attend. But, I'll wager for every one of you who don't attend, 3 more will fill your slot.
Demand for Linux on the Desktop would have to rise to a level approaching that of where Windows is today. True, AutoCad *used* to run on Unix, but it doesn't *now*, and business buy *now*.
As long as Microsoft Dominates the Desktop, you will not see mainstream applications that do not already support Linux/*nix now being ported across from Windows; it simply isn't going to happen anytime soon.
Another poster hit the nail on the head; they stated that there needs to be a giant like Microsoft in the Linux World. IIRC, Microsoft was actually formed in the 1970's. They didn't begin their meteoric rise until the mid to late 80's. Also, it was the concurrent rise of the PC that helped Microsoft, since their it was their version of DOS was being placed on Cloned IBM's that were cheaper than the original. Now that the clones effectively rule, Microsoft rules. It's not that simple, true, but it does paint at least a good portion of the picture.
Linux will need to answer a need--and right now it's perceived by those who control the money that it's a toy. Things take time. Personally, I don't envision it making it to the desktop world in large numbers for at least 5 years.
Yes, you must conform. In a business environment, you can't run rogue operating systems. Let us note first and foremost right now that college IS a business. Let me tell you what--if I missed a deadline for a project because the network had been disabled due to my twit next-door neighbor infecting the world with virus XYZ--I would be fairly unhappy.
The point being--the IT department has the right to say 'Only machines with {name OS} will be authorized on this network.
There are times when you have conform--codes of conduct, dress, etc. If you don't like the rules, then you don't have to be there.
BTW---I also know of a LARGE institution where if you are caught running a rogue OS that is unsupported, they will unplug your port on the switch. They limit you that way.
I've never come across a Microsoft Office document that couldn't be opened with Open Office, Mozilla hasn't crapped out on me on a website in months (excepting those poorly written ones that check UAs and kick non-IE users before they even get to the door), Evolution connects to Exchange just fine, MySQL makes a perfectly good desktop database replacement for Access (if you install the right tools) and I don't know anyone in your run-of-the-mill office job who uses anything more than that. If you have people that need specialized tools like Macromedia / Acrobat / HR and Accounting software, etc., screw Wine and plunk down a MS Windows system for that person. Stick a leaner Linux on the backend and you're done (yea, I'm well aware it's not that simple, but once you get it running it runs pretty smoothly if you have a clue and your PHBs stay out of the way).
Like everyone else who chants "Linux Apps Work just like Microsoft Apps", your thinking is narrow-minded. I would agree that it would work for probably about 50% of the users, but you fail to take into other categories of end users.
1. Mobile Users. Linux does not yet have anything as remotely useful as Synchronization. With Synchronization; mobile users can edit documents offline and the documents are automatically saved to the server when they log back in (assuming IT has set up the laptop to do so--but if you're running 2000/2003, you're doing that through Group Policies, anyway). This saves end users from having to remember to copy the file back to the server, and consequently saves the IT Guy from getting his head bitten off when the CEO loses an important file because his laptop hard drive failed.
2. CAD users. AutoCad (the de-facto standard) ONLY runs on Windows. Not only that, but they even have server software that ONLY runs on Windows Software. Where is the Open Source Equivalent for this highly valued software package? I don't see one out there that can do what AutoCad can do, I guarantee you most developers (read: Builders) use some flavor of AutoCad to produce their drawings, Architects use it, and so do utility companies.
3. GIS. What open-source solution is as powerful as ArcView? I know there are quite a few GIS applications that are open source, but ArcView is extremely powerful. To my knowledge, there is no Linux app that comes close.
4. Other software such as Maintanence Management packages, Help Desk packages, etc. I have had a number of experiences with the above systems; all ran on Oracle, and either you used an over priced and over powered HP/UX or AIX box at the backend, or you used a cheaper NT/2000 box running Oracle at the back end. We tried Linux/Oracle combinations at the backend, but the systems simply wasn't robust enough. (and yes, we had professionals tune the server for us, because our Linux experience was limited) As soon as we moved to the Windows platform, the end users were much, much happier. They never knew what we were running on the back end.
The point is this: There are simply far too many specialized applications out there that are not yet compatible with anything other than Windows. Yes, Open Office and other applications work for Office apps--until you throw VB scripting into the equation, or specialized Macros, or other modifications. I would say that 70% of the end users with Office probably only need WordPad, but like anything with volume licensing, more is better because it reduces the per unit cost, making the Finance Geeks happy.
OH, and Ximian Evolution doesn't support offline folders like Outlook does--so mobile users are slighted there, too.
Linux (and other OS) zealots are frequently narrow-minded in their focus, and they forget about the 'other' category. Making blanket statements is folly. Fully 50% of the company I used to work for were running *specialty* applications--which precludes running Linux unfortunately. Sorry, but just having low-end office apps that work isn't enough.
Windows 2000/XP only, if it's a Windows environment, or MAC otherwise. Any machines found online that violate the policy will be denied access, and the violaters fined.
I know of a couple of small colleges that are MAC only; they don't support Windows machines of any kind. To ensure this, you buy the computer when you start your term--it's part of your tuition and fees. This way, no one brings in anything unauthorized from home.
He also forced everyone, small and great, rich and poor, free and slave, to receive a mark on his right hand or on his forehead, so that no one could buy or sell unless he had the mark, which is the name of the beast or the number of his name.
A Microchip? RFID readers? And so it begins--the method by which the AntiChrist will be able to mark us, as well as that which we buy.
Slashdot Mirror
Ooops....Looks like the issue rears it's ugly head in Mozilla 1.5.1 as well---sort of.. Ok..it's not a strictly Microsoft related problem--perhaps it's in all browsers?
The only way this vulnerability works from within an email application is if you are using browser based e-mail, or Outlook Express to access your corporate mail.
The worse possible scenario was posted to NT BugTraq by Russ Cooper, where it *might* be a consumer issue if it were exploited in the financial realm. Even there, it was reasoned that most of the security (SSL, CA, etc.) used by Financial Institutions mitigates the entire realm.
Is it a problem? Of course.
Should Microsoft fix it? Of course.
Should they take care not to break anything else? Of Course..
I don't believe the original poster was saying anything about being 'elite', he was simply making a point. I, too, use IE daily at home and at work, and have never suffered because of it.
Yes, I keep things patched, yes I am firewalled, and yes I follow the security discussions, but I know others who are not as diligent as I am and have not suffered either.
To those who would sing the 'open source' song--let me remind you that just like Microsoft, you too are under attack by the legal hounds. Personally, I hope SCO loses, but at the end of the day, he who has the better lawyers will win, regardless of 'the truth'. Yes, I'm cynical about our justice system--moreso when it comes to the arena of litigation. When someone wins millions because they were stupid enough to put coffee (a beverage usually served hot--not lukewarm, not cold), between their legs in a moving vehicle and get burned because of their irresponsibility, then there is no such thing as justice.
The truth doesn't matter anymore, really.
Amen..
Read John 3:16; meditate on what an act of Love it was for a Father to allow his own son to die--to be the final sacrifice for humanity.
Satan loves to hide himself; cloaked in that which is 'mysterious'. I went down that path; all I found was frustration. Salvation with God at the Center of my Life has brought me happiness and joy and prosperity.
At issue here is TCO, and unfortunately, TCO isn't limited to simply how much it costs to use, train, deploy, and support an application. There are other problems that need to be addressed; from internal customization of applications to patch management and OS updates.
Let us look at MS-Office as an example. While Open Office affords us the ability to be about 90% compatible (I have personally seen issues with conversion from/to MS .doc format), it's the other 10% that drives TCO through the ceiling. This is inflated by the use of Macros and VBA code within documents, spreadsheets and databases (BTW--I have yet to see an adequate Open Sourch replacement for Access. If anyone does know of any, please feel free to correct me.) and this use of Macros/VBA Code is where the real problem lies.
I know that we should *not* be using VBA code, but many users do--especially Excel Superusers; and this problem exacerbates the Open Source -vs- Microsoft Debate. This isn't limited to internal users, either. Many, many vendors and external users compound the issue beyond any hope of rational solution.
TCO is also exacerbated by the land of the 'instant MCSE' ( I relate those to the US Navy 'Pushbutton Petty Officers'.). Like the Pushbutton PO, they lack the experience needed to think in terms of both how to do things the right way (not necessarily a Microsoft 'Best Practice) and the secure way. This type of thinking only comes with a lot of experience in IT, and you don't get that in 9 months of night classes and some testing software to get you through the tests.
Security training to M$ admins is also an afterthought--although it is improving--and is a real sore-spot. With Unix/Linux, you have to know networking and security, but with Microsoft, you don't really need to know it. A recent editorial in MCP magazine proposed a Board-Certification for Network Engineers. You would start with the MSCE..then you would take a hands on test (like the CCIE) and follow that up with an oral examination by a board of your peers. This is designed after the Certification processes many other professions use, from Nuclear Engineers, to Doctors. I would love to see this become common practice--for all forms of Network Engineer, from Microsoft to Linux. Even Sun, HP and IBM could adopt it. Or, switching gears, make it independent of any vendor, but use a vendors own 'Network Engineer' level of certification as a basic starting point.
Microsoft is not the enemy here, the real enemy is apathy. Apathy by the Board of Directors, the CEO/COO, CIO/CFO, the Admins, the End Users, and by programmers who develop the applications. Even using an Open Source or Unix solution is still NOT the Holy Grail. Patches for Unix OS's and associated software are still required, and they still *might* break your application and thus must be tested. The sad thing is that many organizations, regardless of their solution choice, do not take the time to be aware of proper Patch Management techniques. They don't know about or are too cheap to invest in a "Production Test Environment"; where you model your Production Environment and test patches prior to deployment. Most often these monstrosities require at least their own managers, with cross-level support throughout the organization--from Operations to IT. However, in large organizations, this can be a full-time job for an entire team; because if they're not testing the latest vendor patch, they're testing developed applications, and this all adds to TCO.
While a Unix/Unix-like solution may be the lowest TCO for one company, for another it may well be a Microsoft solution, or a Novell solution, or some other solution we haven't seen yet. One thing for certain--as long as people are in the mix, the TCO will never be completely free.
Robert Heinlein said it best TANSTAAFL or There Ain't No Such Thing As A Free Lunch
Inane, senseless, and trivial.
I prefer other pursuits--Tim Wilson, Todd Yohn, Heywood Banks..now THEY are funny
Let us not forget George Carlin...
If you are using a Win2K/2003 environment, then use Group Policy instead of handing out passwords. Give some adminstrative responsbility to 'tech-savvy' members of a department to perform simple tasks, such as password resets; new user creation or changing file/folder permissions. Create a Taskpad, install the adminpak on the users workstation, and show them what to do.
Cheap liquid ink pens from Staples. Work great..
Microsoft
Drat..now I can't tell the (L)users that they need to wait for tech support to come by and replace their keyboard, and that they'll need to find another means to work until then. How does next Friday at 1pm sound for an appointment?
Even exposing contact information for a business is questionable. If you're working on penetrating a company, then this is a stop on the highway. But, without that information, then (as one poster stated) the FBI would have to get us the information we need to prosecute spammers or etc.
I don't know what the answer is either; I don't think it's simple either. This may be one (of many) invasions of our privacy we have to deal with. Banks, Mortgage Companies, Credit Cards--these all sell our information to other companies. It's sad, but this is big business, and it makes money. Utilities provide information to Local, State, and Federal Agencies all of the time; and are required to by law.
Our information is not private anymore, and hasn't been for a long time. Everyone has their hand out for it.
Actually, the number one distraction is Conversing with passengers, followed by Eating, then Reaching/leaning for things. Cell phones were a distant 8th--even behind dealing with children and reading. This data comes from a study by the University of North Carolina, and found on cnn.com
Here's the URL: http://us.cnn.com/2003/TRAVEL/08/06/distracted.dri vers/
I have actually seen people reading novels while driving down the interstate, and reading the newspaper, with it spread across the windshield.
The biggest distraction with cell phones is dialing numbers--I use a hands-free headset and voice dialing. I don't have to look at the keypad.
As for Israel, they hate them because they stole their land.
Wrong...GOD gave that land to Abraham (Abram) and his descendants. (Genesis 12:1-3).
Now the Lord said unto Abram, Get thee out of thy country, and from thy kindred, and from thy father's house, unto a land that I will shew thee:
And I will make of thee a great nation, and I will bless thee, and make thy name great; and thou shalt be a blessing:
And I will bless them that bless thee, and curse him that curseth thee: and in thee shall all families of the earth be blessed.
I haven't bought a CD since Dark Tranquillity - Damage Done which I think was late 2002.
I only support bands I like--the amount of crap on the airwaves promoted by the Recording Industry is nauseating. Most often, I'm found checking out bands at local music venues, and either buying their CD's or buying compliations of local music put together by local radio.
It beats buying the schlock on the airwaves.
For one reason or another, things are different in the Windows world.
Yes, things are different in the Windows (Simplified) World. In the Windows World; you buy PC XYZ from company ABC complete with Windows. You unbox it, turn in on, and let the 'magic' do its' thing. There's no muss, no fuss and I've got a working PC. Oh, never mind that the OS isn't patched with the latest patches--the average home user doesn't know (or understand) that it needs to be--regardless of the media coverage of worm/virus Qbert. The average home user is NOT technically inclined. Therein lies the source of the problem--lack of sufficient instruction, which is the delegated responsibility of the OEM System Builder.Consequently, every little bug gets passed along, and we end up with MSBlaster type problems.
In the Linux world; the average user is technical, or has had the system set up by someone technical. They take care of the system, understand how to patch the system and ensure that it has been patched. For this reason, problems are short lived.
We live in a simplified world. From fast food; disposable diapers, razors, etc.; to all-in-one super stores; everything is simplified for us. I don't have to know how to make Veal Scallopini; I can buy it pre-made at the grocery. We want everything easy, because we don't want to take the time top do otherwise.
Granted, this is an oversimplified view. I didn't factor in regression testing of patches at the corporate level in order to ensure that the new patch doesn't break something else in use, due to the tight integration of code with the Microsoft OS (unlike Unix/Linux Applications). This takes time (stakeholders and their ilk tend to be a testy when their application breaks) and may result in infection before testing is complete. The point is people have been brainwashed into believing that computers are simple, when in fact they require a lot of attention, like a toddler or a puppy.
How did we do things without computers before? I know..paper and pencil. At least there we didn't have to worry about viruses--unless it's a cold. LOL... Maybe regression is a good thing this time?
No, 1102--you forgot the two boxes the geeks at VA Tech bought to test the environment. And lest you think Apple provided them for free; how do you think the group proved they spent the grant money? Think about the professor in 'Real Genius' for a minute.. LOL..
1100 G5's...that should corner the market for about a week...and give Apple a small boost to it's bottom line..
Three words...External Serial Modem.. I still have one (USR--56K) and it works with either Linux or Windows, since it's NOT a winmodem.
Ah, the glories of Technology. No matter how much we simplify things, we keep backing ourselves into corners..
The rules say you can't have alcohol in the dorm, or pets, or whatever, yet you abide by those. University Computing Services is responsible to all of the students, not just you.
If you don't like the rules, no you don't have to attend. But, I'll wager for every one of you who don't attend, 3 more will fill your slot.
Demand for Linux on the Desktop would have to rise to a level approaching that of where Windows is today. True, AutoCad *used* to run on Unix, but it doesn't *now*, and business buy *now*.
As long as Microsoft Dominates the Desktop, you will not see mainstream applications that do not already support Linux/*nix now being ported across from Windows; it simply isn't going to happen anytime soon.
Another poster hit the nail on the head; they stated that there needs to be a giant like Microsoft in the Linux World. IIRC, Microsoft was actually formed in the 1970's. They didn't begin their meteoric rise until the mid to late 80's. Also, it was the concurrent rise of the PC that helped Microsoft, since their it was their version of DOS was being placed on Cloned IBM's that were cheaper than the original. Now that the clones effectively rule, Microsoft rules. It's not that simple, true, but it does paint at least a good portion of the picture.
Linux will need to answer a need--and right now it's perceived by those who control the money that it's a toy. Things take time. Personally, I don't envision it making it to the desktop world in large numbers for at least 5 years.
Yes, you must conform. In a business environment, you can't run rogue operating systems. Let us note first and foremost right now that college IS a business. Let me tell you what--if I missed a deadline for a project because the network had been disabled due to my twit next-door neighbor infecting the world with virus XYZ--I would be fairly unhappy.
The point being--the IT department has the right to say 'Only machines with {name OS} will be authorized on this network.
There are times when you have conform--codes of conduct, dress, etc. If you don't like the rules, then you don't have to be there.
BTW---I also know of a LARGE institution where if you are caught running a rogue OS that is unsupported, they will unplug your port on the switch. They limit you that way.
I've never come across a Microsoft Office document that couldn't be opened with Open Office, Mozilla hasn't crapped out on me on a website in months (excepting those poorly written ones that check UAs and kick non-IE users before they even get to the door), Evolution connects to Exchange just fine, MySQL makes a perfectly good desktop database replacement for Access (if you install the right tools) and I don't know anyone in your run-of-the-mill office job who uses anything more than that. If you have people that need specialized tools like Macromedia / Acrobat / HR and Accounting software, etc., screw Wine and plunk down a MS Windows system for that person. Stick a leaner Linux on the backend and you're done (yea, I'm well aware it's not that simple, but once you get it running it runs pretty smoothly if you have a clue and your PHBs stay out of the way).
Like everyone else who chants "Linux Apps Work just like Microsoft Apps", your thinking is narrow-minded. I would agree that it would work for probably about 50% of the users, but you fail to take into other categories of end users.
1. Mobile Users. Linux does not yet have anything as remotely useful as Synchronization. With Synchronization; mobile users can edit documents offline and the documents are automatically saved to the server when they log back in (assuming IT has set up the laptop to do so--but if you're running 2000/2003, you're doing that through Group Policies, anyway). This saves end users from having to remember to copy the file back to the server, and consequently saves the IT Guy from getting his head bitten off when the CEO loses an important file because his laptop hard drive failed.
2. CAD users. AutoCad (the de-facto standard) ONLY runs on Windows. Not only that, but they even have server software that ONLY runs on Windows Software. Where is the Open Source Equivalent for this highly valued software package? I don't see one out there that can do what AutoCad can do, I guarantee you most developers (read: Builders) use some flavor of AutoCad to produce their drawings, Architects use it, and so do utility companies.
3. GIS. What open-source solution is as powerful as ArcView? I know there are quite a few GIS applications that are open source, but ArcView is extremely powerful. To my knowledge, there is no Linux app that comes close.
4. Other software such as Maintanence Management packages, Help Desk packages, etc. I have had a number of experiences with the above systems; all ran on Oracle, and either you used an over priced and over powered HP/UX or AIX box at the backend, or you used a cheaper NT/2000 box running Oracle at the back end. We tried Linux/Oracle combinations at the backend, but the systems simply wasn't robust enough. (and yes, we had professionals tune the server for us, because our Linux experience was limited) As soon as we moved to the Windows platform, the end users were much, much happier. They never knew what we were running on the back end.
The point is this: There are simply far too many specialized applications out there that are not yet compatible with anything other than Windows. Yes, Open Office and other applications work for Office apps--until you throw VB scripting into the equation, or specialized Macros, or other modifications. I would say that 70% of the end users with Office probably only need WordPad, but like anything with volume licensing, more is better because it reduces the per unit cost, making the Finance Geeks happy.
OH, and Ximian Evolution doesn't support offline folders like Outlook does--so mobile users are slighted there, too.
Linux (and other OS) zealots are frequently narrow-minded in their focus, and they forget about the 'other' category. Making blanket statements is folly. Fully 50% of the company I used to work for were running *specialty* applications--which precludes running Linux unfortunately. Sorry, but just having low-end office apps that work isn't enough.
Psychobabble again. Plenty of individuals overcome what their environment should make them become.
As the Eagles song says:
You're mamma's too thin and your daddy's too fat. Get Over It. All this whinin', cryin', pitchin' a bitch, Get Over It...
That's when you set forth the rules.
Windows 2000/XP only, if it's a Windows environment, or MAC otherwise. Any machines found online that violate the policy will be denied access, and the violaters fined.
I know of a couple of small colleges that are MAC only; they don't support Windows machines of any kind. To ensure this, you buy the computer when you start your term--it's part of your tuition and fees. This way, no one brings in anything unauthorized from home.
He also forced everyone, small and great, rich and poor, free and slave, to receive a mark on his right hand or on his forehead, so that no one could buy or sell unless he had the mark, which is the name of the beast or the number of his name.
A Microchip? RFID readers? And so it begins--the method by which the AntiChrist will be able to mark us, as well as that which we buy.
Interesting....