3 ms·
You typically view your licensing schemes as keeping honest customers honest. Also, violating licensing terms like that is not something that any serious compa
by bmm6o 12y ago
You typically view your licensing schemes as keeping honest customers honest. Also, violating licensing terms like that is not something that any serious company does. All it takes is one disgruntled employee to blow the whistle on your hacking and the 1) IT manager is out of a job and 2) the company is going to have an unwinnable lawsuit on its hands. It's not a risk professionals take.
And it doesn't have to be a whistle-blower. It can also come up while you are trying to get support for a problem with the software. In the log files or something your colleague didn't know he shouldn't say.
- eps 12y ago> unwinnable lawsuit To put it bluntly, this is just very naive. The financial and the resource costs of pursuing a licensing violation in court are prohibitive. Especially when it's all based on he-said evidence from a pissed off employee. When BSA/Microsoft do this, it's a publicity stunt with long-term effects, and because of that they have a budget for that. For smaller companies (read - everyone else), the only practical option is to shame violators into compliance.
- bmm6o 12y agoIt's a small sample, but every instance I'm aware of has worked out in favor of the rights holder. Are you saying that infringed companies don't usually pursue the matter, or that they do and are unsuccessful?