We ought to set up some kind of public fund that goes into researching prior art and filing challenges with the patent office to have the patents overturned as they are approved.
If we can get upwards of 70% of patents thrown out or rewritten within the first year, surely it will affect the change the patent office so desperately needs in the short term, so we can work toward reform (and perhaps abolition) in the long term.
According to Brocious himself, the company has known about this vulnerability for at least 3 years.
That's three years that they had to issue a fix.
And this vulnerability is so trivial, that anyone with even a modicum of electrical knowledge and minimal programming experience can overcome it. There is, simply, no reason this vulnerability should still be in shipping locks.
They have no excuses. They should be paying for this.
The lock itself doesn't use any encryption, and the cards use a very weak 32-bit encryption based on the site code. The lock itself exposes everything via the programming port on the bottom. When I say everything, I mean that includes the site code (the unique code for the hotel) and everything that's in active memory.
Unlocking it is a simple matter of finding the sitecode and issuing an unlock request.
At least with the Humble Bundle, I'm guaranteed that all or nearly all of the games will have native Linux ports. With Indie Royale, it's a crapshoot - if I'm not lucky enough to get a Linux port of a game, there's a good chance it won't work in Wine either.
The problem was that while Windows was the most-deployed OS in the country at the time, US Government export controls on encryption standards prevented anything with stronger than 40-bit encryption from being allowed to enter their country.
They came up with SEED because they needed strong crypto. The fact that the AtiveX control is the only way to use it is an artifact of that effort. They essentially had no choice at the time.
SEED is so old now that it's probably exceptionally difficult to port it to current browsers that support NPAPI or Pepper, both of which differ subtly from the original API SEED was developed against for Netscape browsers.
If you're going to blame someone, blame the US Gov't.
... as content producers and distributors, they rely on the very freedoms and fair use exceptions that they are constantly seeking to curtail.
As sad as the eventuality would be, it would amuse me immensely if they succeeded in curtailing Fair Use. Watching their own ability to produce and distribute become curtailed to the point where they can no longer profit from their content would be hilarious.
How do we show them that this is self-destructive?
I've been racking my brain trying to think of a way to show them that these kinds of rules are like putting a gun to their own heads - enforcing it will only kill them in the long run as their market ultimately abandons them and their assets shrink to nothing.
If they manage to get fair use outlawed, only outlaws will have the creativity to create. And then where will they get the content and inventions to sell?