Quote:
Originally Posted by hyc
crs: SWF Verification is not a copy protection mechanism. Nor is it an effective technological measure of any kind really. The only thing it is effective at is wasting CPU cycles and electricity. (But then again, that's true of "real DRM" too...)
An "effective copy protection mechanism" is one that effectively limits how many copies can be made. SWFs are freely distributed on web servers; they are copied limitlessly, without any restrictions, in the normal course of their use. Adobe is blowing smoke when they claim SWF Verification has any pertinence to the DMCA.
|
Sorry SWF Verification is a copy protection mechanism as defined by the DMCA - "in the ordinary course of its operation, prevents, restricts, or otherwise limits the exercise of a right of a copyright owner.". SWF Verification, in the ordinary course of its operation limits which SWF's can connect to which RTMP/E streams. The fact that it is well known how SWF Verification works is irrelevant. RTMPE on the other hand is a standard Diffie–Hellman key exchange to enable RC4 encryption between a client and a server thus encrypting the content in transit and is not intended to stop non authorized clients from connecting. This is stated in many places on Adobes website. Several tool producers have been sued by adobe - I dont want to be the next one and I respect a content owners right to limit downloading if they so choose.