Indemnification Roundup 120
Skapare writes "O'Reilly Network's LinuxDevCenter has a great article summarizing the indemnification possibilities for businesses considering switching to (or staying with) Linux. Author Tom Adelstein covers the business risk mitigation aspects of using Linux today, and details available indemnification offerings from Novell, HP, Red Hat, and OSRM. So why not print a copy and send it to your company CEO."
Am I safe just running Microsoft stuff? (Score:5, Interesting)
Here we have an allegedly pro-Linux site promoting the same false statement. That if you run Linux, you have an increased legal risk and hence should shop around for a vendor that indemnifies its users or buy insurance to do so.
If you're going to do an article like this, at least remove the distinction between FOSS (free and open source software) and proprietary software. For example, have a section that lists Microsoft, and then has a statement that says Microsoft does not indemnify their customers.
All these risks people are throwing out about FOSS play right into the hands of proprietary software vendors trying to figure out ways to up the TCO of Linux. Shame on LinuxDevCenter for playing along.
Re:Am I safe just running Microsoft stuff? (Score:3, Insightful)
In the case of FOSS, it's usually support, and if it's not support, it'll be insurance. And if it's not insurance, it'll be protection money.
Barriers To Entry (Score:5, Insightful)
The most politically attractive tool for removing small vendors from a market is overwhelming economic force (free as in beer). Current case in point, Gmail will destroy small ISPs by teaching users to demand hundreds of megabytes of email storage. Yahoo & Hotmail have already responded.
Indemnification will do the same for Linux distributions. You may be able to roll your own distro, but it will be increasingly difficult to distribute it without legal exposure (not only to the publisher, but the distribution channel, e.g. SourceForge/OSDN).
After economic consolidation comes political consolidation (regulation). Sender-pays email, state-issued ID for publication, bank-issued ID for consumption, firewall liability insurance in exchange for permission to face the public network, VOIP-driven consolidate of "offline" and "online" IDs -- and just when you're about to go insane with boundary barriers: premium green-light services that guarantee swift passage to those who can afford it.
Creative anarchy will remain possible within organized economic pools that can negotiate regulatory barriers to entry and evolution.
Pressure from where? LargeCorp marketing dept? (Score:1)
I wonder if comporate consumers are ever motivated by price competition? Hmm...
I agree. (Score:2, Insightful)
Re:I agree. (Score:5, Insightful)
Well, anyone can sue anyone for any reason, so there are risks for just existing. Any larger company has a legal department and a legal budget as it is.
My point is, there's nothing to stop some small software maker in Australia from claiming that a technology inside Microsoft SQL server violates their patent or copyright and threaten to sue end users of SQL server (which I seem to recall actually did happen).
Risks are everywhere. Please stop supporting the myth that using Linux is extra risky.
Correct, but there's more. (Score:2)
"Past infringement cases have focused on software makers rather than end users. For example, Microsoft has encountered many infringement cases from companies like Eolas, Stac, Burst, Netscape, Sun, and InterTrust. None of the Microsoft cases have fallen over to consumers."
While there is nothing to stop anyone from filing a claim against anyone else, one company filing a claim against the end users of a different company has NEVER happened before.
The threats can be (and have been) made, bu
Re:I agree. (Score:2)
Re:Am I safe just running Microsoft stuff? (Score:5, Informative)
Do I need to buy or worry about this kind of stuff when I buy Microsoft software?
No, but then Microsoft software is all done in house. 95% (give or take) of software included in a Red Hat distribution was not created by Red Hat, so they don't have the same level of accountability as Microsoft. With an indemnification plan, they are taking on the accountability of the linux kernel writers, which might give a justified peace of mind to any potential customer.
Re:Am I safe just running Microsoft stuff? (Score:5, Insightful)
Does Microsoft not hire programmers that used to work at other firms, for example? Couldn't they "accidently" contribute code from a former employer's products? Are you willing to indemnify all users of Microsoft that they are not under any legal risk for using Microsoft software if you are so sure?
Re:Am I safe just running Microsoft stuff? (Score:3, Insightful)
In some sense, it's similar to the Napster (the Napster of yesteryear, not the name-whoring music store) vs. Kazaa from the RIAA's perspective. Microsoft is like Napster in that there is a central place of accountability, so the RIAA can just go there (in this case, Napster's s
Re:Am I safe just running Microsoft stuff? (Score:3, Insightful)
In legal terms, never assume a company will come to bat for you, or that an entity suing will pick Microsoft and not you -- especially if you look like an easier target for a win that will set some precedence for them.
Re:Am I safe just running Microsoft stuff? (Score:2, Interesting)
And what type of precedent do you think that would set? One that discourages using Microsoft products? Microsoft is in the business of making money. If Microsoft's customers were being sued left and right you can sure as hell bet that they wouldn't just sit there with their thumbs in thei
Re:Am I safe just running Microsoft stuff? (Score:2)
SCO's plan was to get IBM to buy them out. Even the lawyer's payment terms were geared towards that. You don't see a possibility that a Microsoft customer might get sued for some bogus copyright claim with an eye towards Microsoft buying them out?
I don't see any big differences here.
Whoa there (Score:2)
In fact, here is the link (Score:2)
Has this even come up ...... (Score:2, Insightful)
Re:Am I safe just running Microsoft stuff? (Score:2)
Why do you think NT and beta versions of Win2k worked on the Alpha - but got canned when Compaq bought Digital out.
Re:Am I safe just running Microsoft stuff? (Score:3, Insightful)
Waht exactly are you smoking this morning? as not even crack can make a person that wacked out.
it applies to microsoft and ALL microsoft products exactly the same UNTIL microsoft comes out and says, "we will take the fall for YOU no matter what."... an
Re:Am I safe just running Microsoft stuff? (Score:5, Interesting)
The difference here is that Microsoft has the legal muscle to get virtually anyone to back down from them...even if MS was actually in the wrong.
You can't afford to hire MS's lawyers if SCO decides to sue you next...thats what you would want indemnification for.
Frankly, I am surprised that anyone is still discussing this as if its really a viable option anyways. SCO's suits are all but over, paying indemnication fees to anyone at this point is a waste of money, no matter who you are.
Re:Am I safe just running Microsoft stuff? (Score:1)
That's a pretty bold and gutsy statement: can you back that up with evidence?
Re:Am I safe just running Microsoft stuff? (Score:2)
Re:Am I safe just running Microsoft stuff? (Score:1)
You are wrong: stealing isn't when you use source code under an appropriate license - and the BSD license certainly allows for this. Try again.
Re:Am I safe just running Microsoft stuff? (Score:2)
Re:Am I safe just running Microsoft stuff? (Score:2)
Stac Electronics, which accused Microsoft of stealing its data compression code and using it in MS-DOS 6 [4]
Sendo, which accused Microsoft of terminating their partnership so it could steal Sendo's technology to use in Windows Smartphone 2002 [5]
Apple Computer, which accused Microsoft of stealing QuickTime code and using it in Windows Media Player
This was just a quick google too. There was once a documentary on TV a
Re:Am I safe just running Microsoft stuff? (Score:2)
Microsoft end users have been sued (Score:5, Informative)
http://www.theregister.co.uk/2003/02/20/sql_ser
From the evidence that exists so far, it is clear that msft end-users are the ones more likely to be sued.
Of course the most likely to be sued of all, are end-users of scox proprietary products. For the simple reason that scox has made it a normal business practice to sue anybody who has any sort of contract with scox. So far that includes: ibm, chrysler, autozone, and novell.
What was it scox spokesman blake stowell said? "Lawsuits are what you use against people you have a contract with."
Re:Microsoft end users have been sued (Score:2)
Here's a clickable link [theregister.co.uk] to that article.
Re:Microsoft end users have been sued (Score:1)
Definitely Not. (Score:5, Informative)
For your consideration:
One could make some very good objections to using Linux, but liability is not one of them. If anything, the fact that the source code is freely available means that absent frivolous plaintiffs (*cough* SCO *cough*) there is a very small risk of being sued. Unlike the proprietary, closed source model, cases of actual infringement can be mitigated by the end user. If I was sued for IP infringement and didn't have the source code, my only option (assuming that infringement really took place) is to pay royalties and licensing fees. But if I do have the source code, I can simply remove the infringing material, substantially reducing the damages that a plaintiff could collect.
And for all you Microsoft-vs-Linux trolls, save it. Microsoft and Linux are just good examples of the relative strengths and weaknesses of open versus closed source. The argument would apply equally well to Adobe Photoshop vs. Gimp or Oracle vs Postgresql, etc...
Re:Definitely Not. (Score:2)
Saying there's no way to determine what's in a closed source project is ridiculous. It's not as if the d
Re:Definitely Not. (Score:2)
Well, yes, functionality wins hands down. There's little point in installing software you can't really use.
But the whole security through "code auditing" thing is a farce. What does auditing matter when the company itself is willing to steal the code of others and infringe patents at will?
The Timeline case is a perfect example. Timeline gave Microsoft their code, and someone at Microsoft decided to ship it with SQL server. It's not as if it was an accident (and if it was, there goes your auditing
Yeah, and... (Score:2)
Just once I'd like to see Open Source apps that didn't pretend to be a cheap knock-off of someone else's successful product.
Why is it that FS developers insist on following Microsoft's lead? .NET is a stupid idea, and .Mono even worse - why would you build a virtual machine if it would never be ported to other platforms, and why spend effort optimizing said machine when modern compilers can already generate much faster code?
Oh, I know - the challenge. Rather than writing code which actually solves p
And Microsoft never copies? (Score:2)
Betcha can't do it. Not even one.
Re:Am I safe just running Microsoft stuff? (Score:2)
Re:Am I safe just running Microsoft stuff? (Score:1)
I am close to having a "ceremonial burning" of all my computers, software and docs...then go fishing for the next few years until I expire.
If enough of us refuse to buy software under these "licenses", i.e., you get between them and that cash register, they'll drop that shxx in a heartbeat. But not un
All of this concern.. (Score:5, Insightful)
These companies backing their products with legal aid are simply doing it as a marketing ploy. RedHat, HP, Novell.. they know there's nothing to worry about, that's why they've all been so eager to extend these "services."
I can't wait until the whole SCO case is just over. We all here know that SCO will lose.
Re:All of this concern.. (Score:3, Insightful)
Will the Judge rule that way though. The masses were all sure OJ would be convicted as well.
Re:All of this concern.. (Score:1, Funny)
OJ was tried by a jury, and juries are not noted for their in-depth knowledge of the law. So long as SCO vs IBM stays in front of competent legal minds, I have much less worry that the wrong verdict will be reached.
Re:All of this concern.. (Score:2)
There is no way that SCO can prevail. Their main argument with DaimlerChrysler is about whether a list of Unix registered CPUs constitutes a list when
Re:All of this concern.. (Score:2)
Re:All of this concern.. (Score:1)
Re:All of this concern.. (Score:2)
The man is a slime-ball.
Re:All of this concern.. (Score:1)
Definitely a farse, for sure. But to business executives, it is also a legal reality that cannot be ignored. And the fear is not that SCO might ever win anything, but that they might be expected to have to defend against such an attempt. And the counter-suit to recover legal defense costs might well get nothing because of the financial problems at SCO. So it isn't a matter of knowing that SCO will lose. The risk is getting struck by its dying attacks.
Re:All of this concern.. (Score:2)
To my mind, anyway, there's a huge distinction between Red Hat and Novell saying, "You have nothing to worry about over buying our product -- we guarantee it!" and Perens & Groklaw Insurance saying, "If you buy our 'insurance', we'll (sort of) protect you from getting sued over Red Ha
Bad opening statement... (Score:5, Insightful)
Re:Bad opening statement... (Score:2)
Re:Bad opening statement... (Score:1)
How many of you are reading this now, as paid daytime employees who write F/OSS software in the evenings, not aware of the Intellectual Property clauses in your employment contract, nor of the legal cases over direct or indirect (subconscious) copying of software - meaning that your day work could spill over into your evening work, meaning that you employer may actually have grounds to take you on in a law suit some day?
I'm not sure if there is a could hanging over F/OSS, but there certainly seem to risks
Re:Bad opening statement... (Score:2)
Re:Bad opening statement... (Score:2, Informative)
Of course it's different, but it's a legitimate issue to raise now that we're talking about F/OSS and indemnification.
"And IANAL, but I really don't think an employer who had an employee contracted not to produce work for anyone other than the employer would be able to sue anyone besides the employee who broke contract."
It's clear that your not a lawyer, because the circumstances are blindingly obvious: employee "moonlights", then employer claims that employee contributed unauthorised
Re:Bad opening statement... (Score:2)
Re:Bad opening statement... (Score:1)
Of course, but lawyers understand them just as well as developers understand multiple-inheritance, polymorphism and dynamic dispatch.
"Say my next door neighbor works in an autoshop, and is under contract not to compete with his employer... so if I ask him to help me fix something on my car, is he commiting a crime?"
Possibly, but it depends on a number of factors. Did he just fix your car? Or does it fix other peoples cars as well? Does he use tools from the w
Re:Bad opening statement... (Score:2)
Re:Bad opening statement... (Score:2)
Article repost before the slashdot-ing hordes (Score:2, Informative)
by Tom Adelstein
06/28/2004
Little doubt exists; a legal cloud hangs over Linux from infringement claims of the SCO Group, Inc. In spite of that cloud, Linux server sales grew 56.9 percent in the first quarter of the year. Linux sales in 2004 follows six consecutive quarters of double-digit growth for the free operating system during unprecedented legal attacks from SCO over the same period.
Advertisement
Linux success helped push all server growth to 7.3 pe
Re:Article repost before the slashdot-ing hordes (Score:1)
Please don't repost our articles without permission. (I've never denied permission to anyone who asked, but we have several speedy servers and a lot of bandwidth.)
hmm.. (Score:2, Informative)
Re:hmm.. (Score:1)
Are you babbling about running SQL Server on Linux, and then making up numbers for costs?
I don't know what you're referring to by seats... if you're talking about SQL Server, do you mean server OS installs? If you're talking about CALs, then you have to pay per "user" on the server side. If you're talking about OS licensing on the server, if you're going to run RHEL ES, then it'll cost you more than a grand.
Forced upgrades? Do commercial Linux vendor
The risk of not using Linux or GPL software (Score:2)
Just proving them right (Score:5, Insightful)
"Look, these Linux users are getting indemnification
stuff for fools to buy. (Score:3, Interesting)
it's a bunch of empty and useless words that the companies are throwing out there. if you read it very closely I am betting that there are clauses and loopholes that relieve them of their "protection" in many ways.
if it makes a PHB heppy and shut's him up, then it may have value in that way. but it has ZERO value in any courtroom or for any protection for a company.
anyone with even a slight legal background can see this.
ZERO value? (Score:2)
but it has ZERO value in any courtroom or for any protection for a company.
So you haven't read it, but you can state that it has ZERO value?
anyone with even a slight legal background can see this.
I am sure that any slight legal background that you have comes from being prosecuted. You have zero knowledge of contract law.
Presumptuous of me to say?
Yeah, I thou
Re:ZERO value? (Score:2)
http://h10018.www1.hp.com/wwsolutions/linux/dow
Nothing is full protection "like you never got sued", but indemnification isn't entirely worthless, either.
Game over. Thanks for playing.
-PM
Imdemification for only $100 (Score:3, Funny)
Re:Imdemification for only $100 (Score:1)
Re:Imdemification for only $100 (Score:2)
(Hmmm, thinks...) "From Tex to Tux - all that's needed is 'U'!"
Re:Imdemification for only $100 (Score:2)
"From Tex to Tux - all that's needed is 'GNU'!
Re:Imdemification for only $100 (Score:2)
Damn, much better! Thank GNU very much!
Why worry? (Score:2, Interesting)
If I want to use an Open Source OS that had settled the UNIX IP matter long ago, I pick FreeBSD.
If for some reason I want the GNU tollset I could pick GNU/FreeBSD.
Too bad Tom Adelstein couldn't be bothered to point out how the SCO claims of UNIX IP vs Open Source OS was solved years ago by the BSDi crew.
Re:Why worry? (Score:1)
You and I, and I am sure Tom Adelstein, all know that SCO's case is meritless. But the real problem is that some companies still get sued by a dying company. Executives don't want their company to have to be the one that has to pay a lawyer to bring the BSDi facts into a courtroom. Indemnification will help for those companies where the decision to go with Linux is being held back due to the legal risk (not of losing, but of having to defend).
This isn't helping (Score:3, Insightful)
I know, I know. It's awfully hard to prove them wrong when they won't say exactly what they claim. So sue me. err, no... Sue them! That's what IBM, RedHat, and a few others are doing right now.
CEO (Score:5, Informative)
Unless you're in a very small company, the CTO would be a better bet.
If you're in a really big company, then the chances are it should be going to the Director of IT.
Don't immediately shoot yourself in the foot by annoying people whose job is not to consider/deal with these issues.
Re:CEO (Score:1)
While the CTO would be the person to move forward on decisions like using Linux (and a good CTO would well understand the lack of merit in SCO's case), a CEO might well be involved in addressing the legal issue. If anything, the CTO should be the one doing the printing of it and putting it on the CEO's desk.
If you're not the company CTO or Director of IT, it probably is best to pass it up the pecking order. But it should be intended for the CEO ... or maybe even the CFO ... as that is where legal risks c
indemnification agreements could be deadly too (Score:1)
the simple fact that you need an indemnification agreement when buying linux is enough for your email too go smell the trash-bin.
a responsible CEO cannot act in a "so, sue me" manner!
and btw stop bashing SCO, its not their fault .. the real culprit is the american justice system that allows them to do what they do!
The costs of linux (Score:2, Insightful)
Huge Stuff for the Gunshy (Score:5, Interesting)
It's a problem. Businesses that use 3rd party products need those products to perform WITHOUT giving them the added legal expense. I think your ROI really drops when it includes a few suits. Small businesses, in specific, aren't about to take that chance. That being said, they're less likely to be targeted, but often the chance isn't worth it.
They want someone to point a finger at if something goes wrong...the software breaks, it destroys data, or they get sued for infringement in order to recoup lost money. With open-source, you have no one to point at. (usually)
Why is Novell's solution better? (Score:2, Insightful)
Novell offers legal protection, but Red Hat is basically offering the ability to carry on operations without worrying about the lawsuit. I understand that legal liability is important, but the real threat is not having a solution that you are legally able to use. To me, this reduces the real uncertainty in the situation. Novell's users might not have to worry about the legal fees, but what do they do with their business
I have a question (Score:1)
Who OWNS tabbed browsing? Is there a patent on it yet? Compared to a lot of the other ridiculously silly patents out there in IP land,and all these disputes, it seems to be a major big one. It is so useful any innovation (imo) that most people who use it will hardly ever be satisfied again with any non tabbed enabled browser.
Indemnification the great con! (Score:2)
Typical small company, "Oh dear we had batter settle we can not afford to loose a suit like that!"
Smart company, "If the comapny we bought this from did wrong why are you not sueing them? Could it be that you are going after those that are too weak to fight you and betting they will just cave in?"
What a
I don't think... (Score:1)
dont' pay for indemnification... (Score:1)
Just let SCO and patents die (Score:2)
Why on earth would I do that? The first thing (s)he'll ask is
"So there's truth behind all this SCO stuff?" At which point I'll say
"Er, well no, it's all a buncha hooey"
"So why are you showing me this?"
"Err.. uhhh"
I'm aware of the litigious world we live in, but even acknowledging that there's a possibility all this patent/SCO crap is right plays into their hands.
SCO is dying, and with it (I can hope) the threat of patent infringement lawsuits, at le
This is bullshit (Score:2)
FUD terrorists (Score:2)
Simple. (Score:1, Informative)
Uh ... (Score:2)
Because she's functionally illiterate?
Can OSS insurance work? (Score:1)
If those insurers cover the kernel (or any other ubiquitous component) then they're a joke, IMHO.
Let's say Linus blunders and commits in something that really violates a patent. Now when the patent holder sues everybody... it's like if all the cars crashed in an instant for a car insurer. The insurance company would go broke in a second.
Am i missing something?
new competition? (Score:1)
Is it me, or does having all these companies offering indemnification services for (roughly) the same product look like a market being re-opened up to competition again? Even when it comes to legal services for something you probably don't need, you STILL have more choices with Linux than with Windows.
SCO's next target (Score:1)
SCO plans to continue to threaten people who know very little about the state of its information technology shops.
First thing I think this means is that SCO is threatening companies that are not well informed about the history of Unix and Linux. And if what the experts of Unix and Linux are saying SCO is one of those companies that doesn't fully unders
Wierd SCOX stock behavior on Wednesday (Score:2)
Last Wednesday, around 11 am, SCOX suddenly went up to $6.25, in heavy trading. [yahoo.com] Somebody made that happen. It wasn't a random event. But whomever d
do the big boys offer this (Score:2)
We don' need no steenking indemnification... (Score:1)
The whole deal revolves around SCO's allegations that IBM borrowed copyrighted Unix code and incorporated it into Linux to improve Unix program compatibility, thus hurting SCO's business. SCO would be severely impacted if the Unix-alike, Linux, were now Just-Like Unix, and people no longer needed to pay for a genuine Unix solution - they could get it for free, or perhaps with some