Re: [PATCH] Blacklist binary-only modules lying about their license

[Stefan Smietanowski <stesmi@stesmi.com>]

Hi.

> The purpose of the workaround is not to circumvent any protection, but 
> to fix a real usability issue for systems in the field, which, as an 
> expert you perhaps do not see, but users definitely massively felt and 
> complained about.

That's like saying that someone hates getting a speeding ticket from
those automatic cameras that are cropping up everywhere now.

He then promptly removes his license plate so he can't be tracked and
then he can continue to speed along.

Now - To the entity that is issuing tickets it appears that that
person is now a law abiding citizen and does not speed anymore when
in truth he removed the plate so it would appear that way.

The speeding ticket is printed message.

Yes, it might or should be changed to print it once or once
per $MODULE_VENDOR or license or whatever, but the issue remains.

It wasn't YOU that installed the speed camera nor set the speed
limits (ie created the tained flag and the code that prints a
message when such a module is inserted) but claiming that
"but it's only a workaround because I was getting so many tickets"
doesn't make it any better.

Yes, Linux is such an open system that a user can install a kernel
that doesn't print anything for tained kernels (remove speed cameras)
but that doesn't mean that YOU can do anything about it from the side
of the car (module).

Also note that neither the speed camera nor the kernel actually make
any limits on speeding (loading proprietary modules).

// Stefan