Baba wrote: > Encryption is dumb. Any usefully strong encryption would > slow things to intolerable levels. Bad encryption just > slows things down for no reason.
(rhetorical) Why do you lock you house door at night? Don't you know that my 15 pound maul can easily open it? And if that doesn't... AN+fuel= real brute force attack. (end rhetorical) It's not technical matter... but a LEGAL one. In order to enforce parts of the DMCA (or similar laws in other country's) you have to show intent. The DMCA makes it a crime to divulge information about how to circumvent copy protection systems. It does not specify how strong the encryption has to be. I am saying that simply compiling in a random 256 byte sequence and XOR'ing the data would comply with the legal requirements. data = data XOR m_key[i AND 0xFF]; --- Zero Linden Says: in blog http://blog.secondlife.com/2006/12/21/a-big-change-youll-barely-notice/#more-632 "Using HTTP proxy caches for textures: Outside of Linden Lab’s networks, no. Access to textures still requires an authenticated, secure channel, and HTTP doesn’t allow caching in those cases (since the cache itself isn’t authenticated)." This implies that LL will not allow a separate proxy cache system unless the cache is secure. A separate proxy cache system would benefit a lot of users. You would get performance improvements even if you only had one client connected since users could use a second (probably older) PC to cache the data. -- Bill, Grumble _______________________________________________ Libsecondlife-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/libsecondlife-dev
