The article does not mention which patent suit this was. But if it was the Edison vs Swan litigation, I had the impression that this case ended up being settled rather than 'won', and that the settlement led to the merger of the two sides companies.
In terms of what the ISP can do with the site, the terms and conditions of use say that they are allowed to disable it if they feel like it. But see below.
I've just had been supplied with information on the relavent bit of the Act, and it's seems to be about circumventing copy protection mechamisms. I'm supprised we have such lunacy in our Law.
Thus that page may well fall foul of English Law.
So don't bother the ISP, they are taking a reasonable course of action.
I guess I basically need to visit a Solicitor on Monday.
Basically, this package is the reverse engineered version of a program called DeCSS, something which can be used to authenticate with and unlock a DVD player.
No it's not it's the original source to DeCSS. I've got a copy of that. If it was reverse engineered then the CSSauth.cpp file wouldn't be identical to that in the "proper" DeCSS source and remarkably similar to the code in my CSS authenticion package.
DeCSS will be available under the GPL, but as its source had not been released yet
Actually the source accidentally escaped when DeCSS was originally published.
But it contains code written by someone else (also on the list), and it was GPL'ed - that code was originally assembler and then turned into C (the assembler was reverse engineered).
Actually the Algorithm was determined from inspection of the x86 assembler, and then a new implementation of that algorithm was written. This C implementation is what I then GPL'ed.
The legality is a biggy
Not at all - an individual expression of the CSS authentication algorithm may be copyrighted, but the alogrithm itself cannot be.
But it contains code written by someone else (also on the list), and it was GPL'ed - that code was originally assembler and then turned into C (the assembler was reverse engineered).
Actually the Algorithm was determined from inspection of the x86 assembler, and then a new implementation of that algorithm was written. This C implementation is wahat was GPL'ed.
Slashdot Mirror
Quite.
The article does not mention which patent suit this was. But if it was the Edison vs Swan
litigation, I had the impression that this case ended up being settled rather than 'won',
and that the settlement led to the merger of the two sides companies.
Note - that was only the authentication algorithm.
DF
Try reading a bit more of the history...
No it's not the Cascading Style Sheets thing, its the basic _authentication_ algorithm.
DF
In terms of what the ISP can do with the site,
the terms and conditions of use say that they
are allowed to disable it if they feel like it.
But see below.
I've just had been supplied with information on
the relavent bit of the Act, and it's seems to
be about circumventing copy protection mechamisms.
I'm supprised we have such lunacy in our Law.
Thus that page may well fall foul of English Law.
So don't bother the ISP, they are taking a
reasonable course of action.
I guess I basically need to visit a Solicitor
on Monday.
Derek Fawcus
No actually what I said was that the authentication code was mine and that since it was GPL'ed, this whole source release is now GPL infected.
Derek Fawcus
No it's not it's the original source to DeCSS. I've got a copy of that. If it was reverse engineered then the CSSauth.cpp file wouldn't be identical to that in the "proper" DeCSS source and remarkably similar to the code in my CSS authenticion package.
DeCSS will be available under the GPL, but as its source had not been released yet
Actually the source accidentally escaped when DeCSS was originally published.
Actually the Algorithm was determined from inspection of the x86 assembler, and then a new implementation of that algorithm was written. This C implementation is what I then GPL'ed.
The legality is a biggy
Not at all - an individual expression of the CSS authentication algorithm may be copyrighted, but the alogrithm itself cannot be.
Actually the Algorithm was determined from inspection of the x86 assembler, and then a new implementation of that algorithm was written. This C implementation is wahat was GPL'ed.