Slashdot Mirror
Ask Slashdot: Dealing With the Business Software Alliance?
Kagetsuki writes "We've just gotten a letter from an attorney representing the Business Software Alliance stating someone (we're certain it's a disgruntled former employee) submitted information we are using illegally copied software. The thing is... we're not using illegally copied software. We have licenses for all the commercial software we are using. Still, according to articles on the BSA, that's irrelevant and they'll end up suing us anyway. So we now need a lawyer to deal with their claims and we don't have the money — this will surely be the end of the company into which I've sunk all my savings and three years of my life. Has anybody dealt with the Business Software Alliance before? What action should I take? Is there any sort of financial recourse, or at least a way cover our legal fees?"
Everything I've heard about the BSA is that they employ our now corporate police departments to force audits/etc.
If they don't find shit, they don't have shit.
With that in mind, do your own audit first .
You have licenses for everything? Really? Even the software that wanker down in the mail room installed on his PC? Not yours? Not for work? Wasn't you, was just the employee?
Doesn't matter.
Don't agree to any BSA demands or requests. Find a lawyer experienced with dealing with the BSA.
If you agree to an audit, it's highly probable they will find something illegal, regardless of whether you did anything illegal or not. You need a proof of purchase for every copy of an installed software product. If you use a Windows environment, you need proof that you had sufficient CALs for everything, on effective audit date.
If anything's not in order, or you can't find one proof of purchase for 1 license of XXX, the BSA will insist the software is pirated (even if you bought it good and legal), tack on huge fines, etc
"We've just gotten a letter from an attorney representing the Business Software Alliance stating someone (we're certain it's a disgruntled former employee)"
Be prepared to sue that former employee, for all damages and costs your business incurred as a result of their allegation, If they made a frivolous/false claim that hurt your business, and you can show who it is, take them to court. Maybe they (and others) will think twice, before making false reports to the BSA racket people.
The BSA needs their evidence to sue you, make sure you force the BSA to divulge the identity of the person reporting. Again, you will need legal counsel to help you with this
My guess is that if you let them in the door you will be screwed.
Keep in mind that while they like to act as if they are a government / law enforcement agency they are merely a private party that is hoping that people will be impressed enough with their act to hand over enough information to hand themselves.
While you would think that being reasonable and cordial is the right thing to do, you've given the BSA a letter they can use against you. If they find even one copy of software which you can't find the receipt, they'll use the letter. Get a lawyer first which will advise you of what to do. Remember, the BSA has started out with a threat not a cordial letter themselves. From that stance I would surmise that even if they are wrong, they don't care.
Well, there's spam egg sausage and spam, that's not got much spam in it.
Not really. That's why the GP pointed out that this is a civil, rather than a criminal matter. In criminal cases we have the principle of "innocent until proven guilty," but that's not true in civil cases. For civil cases, the judgment is supposed to go to the party that offers the preponderance of evidence in favor of their argument. If the BSA comes in and says it has an affidavit from a former employee that says he was eyewitness to license violations, and you come in with "no, we're fine"... well, that might not cut it. You'll want to provide some evidence in your favor.
Do you have a receipt for every copy of Photoshop or Office your company is using? Do you have the original media with the label showing the serial number? No? Well how did you get those serial numbers, then?
If it gets to the point that you're going to trial and you allow the BSA to determine the terms and nature of the audit, you will probably lose. What company doesn't have a few license violations here and there? Whether the violations are intentional or not, if you come before a judge and swear you are in absolute compliance and you have no reason to deal with the BSA, and the BSA shows proof of license violations, it will look bad for you.
Breakfast served all day!
Posting near the top to state the bleeding obvious- 99% of Slashdotters are IANALs and many will offer advice that sounds sensible to them, but may turn out to be woefully misguided and possibly have unintended consequences and land you in hot water (e.g. advice like this). This is because the legal system does not always actually work like geeks think it does (regardless of whether it *should* work that way).
Bottom line- unless the person is a lawyer, or has actual experience of having gone through this (and the consequences that ensued), you should not be taking their advice. And as I said in the post linked above, the problem is sorting out the ones who *actually* know what they're talking about from the armchair lawyers arrogant enough to think that they do.
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
I'm really glad the software shop I'm working with is on Linux. No Windows crap in sight. We could get one of those BSA letters and all have a good laugh.
I feel sorry for anyone that has to deal with the BSA. My condolences, but you should have chosen software without licensing issues. The idea of keeping track of the sales receipts as well as the licenses themselves is ridiculous. What would they do if you paid cash for the licenses? The source of the license does not matter as long as the license itself is not a forgery.
Send and *affidavit* AND quoted *license numbers* to the BSA upon a request.
I am not wearing a tin-foil hat, but, you sir, you seem like someone who works for the BSA.
This sort of a letter will be the single most damaging piece of evidence against the victim in the court.
I agree with the above, but I would go further.
Ask that they state which software package is being used without proper licensing and on which machines so that you may properly investigate it yourself.
If the police come to your door and say, "I know you are breaking the law because of an unnamed snitch, please allow me to look around to see what I can find to use against you...and by the way, I get a commission from convictions." Would you allow them in?
Fight Spammers!
Of course. Example: I used to run IT at a graphic design firm, where the designers were always hungry for more memory and faster CPUs. Each time they got a new Mac, I'd set it up with all their software and maybe swap it out while they were on lunch. As soon as I did that, I was in violation -- two Macs had copies of the same software with the same serial on them! Technicality? The vendor would probably give you a break for it? Sure. But what does "give you a break" mean if it's already heading for court?
Thinking about graphic design firms again, just suppose you were completely on top of it and had all your licenses for Photoshop, Illustrator, etc. in order. (We were actually pretty good about this.) What about fonts? Every font is a copyrighted piece of software. Is every computer in your shop with a copy of a font on it licensed for that font? Are you sure? Suppose one of your partners, clients, or a contractor e-mailed one of your designers some files and included the fonts in a Zip: violation. In fact, I'd wager if you don't have a site license from Adobe then you're almost certainly in violation -- and sometimes even then.
What about servers? Is your server software licensed based on the number of clients? Does it have a hard control over how many clients can connect to it? If it doesn't, are you sure you're in full compliance? Have you hired anyone lately?
There are countless examples, and most of them happen without actual malice. Unfortunately, nobody has to prove malice.
Breakfast served all day!
This is both a question and a point but don't US courts require at least basic evidence before a suit can be brought?
Not generally, no. They require that the "pleading" or "complaint" state a claim on which relief can be granted, but they do not require evidence before you bring the suit. Evidence is produced through a process called "discovery" after the courts are formally involved (although they don't really do anything during discovery, and asking them to because you're in a fight about whether something is discoverable usually gets them mad at you. They don't like to get down in the mud, as it were). If there is no evidence after discovery, the matter will be dismissed, but if there is conflicting evidence, it will go to trial (usually).
At least, that is true in theory. In reality, the VAST majority of cases are settled.
They do require a little more than they used to--pleading standards were raised within the last few years--but they are not terribly high. The higher they are, the harder it is to sue someone who really deserves it but tries to hide evidence; the lower they are, the worse one can be harassed and the more someone can use lawsuits to reveal private company information.
Still, if you have absolutely no evidence--not even the testimony of someone who knows something happened--it would be highly inadvisable and possibly criminal to file a lawsuit. YMMV, IANAL, and consult an attorney if this is any way relevant to you, rather than purely academic.
-- IANAL, this isn't legal advice, and definitely isn't legal advice for you. Also, Squee!
you're suggesting that leaving the invalidly licensed software on the machines is a better course of action? LOL
Yes, don't USE the unlicensed software, but be aware that deleting it, once an investigation has started or been promised, could be a crime. Most important advice: talk to your lawyer, not Slashdot!
If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
Instead of doing the right thing--giving them your advice, and when they refused to follow it, politely saying you could no longer work for them--you administrated the illegal software, took their money for doing do, then turned right around to the BSA and took their money (offer) for ratting out your co-conspirators. You probably put an engineering company employing over 30 people out of business and got paid for doing so.
The company was advised they needed licenses, they were advised that not having the licenses would make the employee liable, and they said they didn't care. Frankly, at that point any moral obligations that an employee should have towards his employer have just disappeared in a puff of smoke.
At that point the employee has no moral reason to quit immediately, without having another job lined up, but is free to do what is best for him or her. That is make sure to avoid any liability, possibly by ratting, appear to be doing the job, take the salary, and look for another job. He can be sure that his boss is doing the same thing.
I don't happen to find any other post that mentions the elementary fact that unless you signed an agreement somewhere that gives the BSA the right to make an audit, you can just tell them to STFU and GTFO. If you bought everything at retail, for example, Best Buy, Provantage, PC Connection, etc, no such agreement would apply. It's when you buy site licenses or have to sign an agreement to make the purchase that you get roped in.
If there's something in the shrink wrap somewhere, then it gets murky. That's where they can claim that you "agreed" to something you never did, just by opening the package.
So step one is to ask them for their explicit basis of authority in your case.
What morons rated this up to +5 insightful?
He didn't just turn the company in one day for shits and giggles, he was told by management that he was liable if anyone ever found out that they were using pirated software. The company put him in a position to be thrown under the bus should anything happen in the future, and this was long before he did anything to hurt the company.
The proper solution in this case (both legally and ethically) was to inform the BSA (or at least someone) that this was going on. It would have been illegal and unethical of him to continue to use the software it would be equally wrong of him to simply leave the company knowing full well what was happening. Furthermore, if he didn't report them and simply left the company he could still be liable in the future if the company claimed that he caused these problems before he left.
They're something to be said for being loyal to your employer, but this loyalty ends when your employer isn't loyal to you. This loyalty ends even faster when your employer tells you straight out that they aren't loyal to you, as they did in this case.
-1 disagree is not a modifier for a reason. -1 troll, flaimbait, redundant, overrated are NOT acceptable substitutes.
Freetards are always great for a good laugh.
Laughs are great, but it looks like the freetards get the last one, doesn't it?
That 20-page license agreement for your superior closed-source $oftware pretty much sets you up for this kind of invasive nonsense, and you have very little recourse. Be sure to factor that in when you're doing your comparative "cost of use" estimations. If you actually did anything like that, of course...
if someone at NASA and Thiokol had 'snitched' on their management to the media, then the Challenger would never have gone up in cold weather, the o-rings wouldn't have failed, the gas wouldn't have erupted into the main tank, the tank wouldn't have ruptured, and 7 people would be alive.
but hey. i guess 'not snitching' is more important than the lives of seven people.
glad you have your principles in the right place.