Hacker News new | ask | show | jobs
by halosghost 3954 days ago
It seems like you've missed the point. The problem isn't that companies are using the work without paying. The problem is that the unnamed companies are essentially lying in their marketing and violating the grsec trademark in the process.

This is not how FLOSS is supposed to go.
1 comments
blm 3954 days ago
Why do you think they are lying? Did the companies use not apply the grsecurity patches but claim they did?

If they did apply the patches AND used the grsecurity trademark in their brochures what is the problem? They arent misrepresenting grsecurity. They arent being derogatory in any way. Why can't you say that you have the kernel and you applied grsecurity patches?

It seems so funny when people are all about GPL code and "freedom" and yet act so precious about a "trademark" just like proprietary enterprises.

link
teraflop 3954 days ago
The whole point of trademark law is that the owner of the trademark gets to control how it's used in commerce. If the mark is being used to advertise a company's product, grsecurity has the right to prohibit it; the company doesn't get to make the call.

This isn't a free-speech issue -- it's just a simple acknowledgement of the fact that consumers treat names, logos, branding etc. as indicators of a product's origin, and that there's a public interest in making those indicators accurate. You can refer to the trademark as long as you don't do so in a way that misrepresents your product. In this case, unless there are specific disclaimers to the contrary, a reasonable person would think "grsecurity" means "code released and approved by the grsecurity team", instead of a version that a third party has modified.

link
bigiain 3954 days ago
From the post: "The aforementioned company has been using the grsecurity name all over its marketing material and blog posts to describe their backported, unsupported, unmaintained version in a version of Linux with other code modifications that haven't been evaluated by us for security impact. Simply put, it is NOT grsecurity"

There _are_ no "grsecurity patches" to apply for the system they're using the grsecurity trademark on.

Seems pretty clear cut from here.

link