http://picpaste.com/Libray_files.JPG
http://picpaste.com/Include_Files.JPG
http://picpaste.com/Executable_files_2.JPG
http://picpaste.com/Executable_Files_1.JPG
With patches SNOW-584http://jira.secondlife.com/browse/SNOW-584
and
While I understand the issue that people are banning based solely on
viewer ID, I don't see this as being a security issue. The client is
NOT being hacked, the information is just not as easy to access as it
is for a web browser.
I see the info bring gathered as nothing more than the user agent
On 05/04/2010 10:57 PM, Ricky wrote:
[...] we could easily add some functions into our various viewers to change
the string into
whatever we choose it to be. Again, just like browser useragents.
Would that be allowed under TPVp section 2.
http://secondlife.com/corporate/tpv.php#priv2c.ii?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Is the internal browser considered the viewer itself or can it have it's
own identifier? And is the user agent string of the internal browser
*the* unique viewer identifier mentioned in the TPVp? Are we gonna have
to hire a lawyer to get these
After the meeting earlier today I made some changes to the modifications in
http://jira.secondlife.com/browse/SNOW-622 to include the suggestions made
at the dev meeting.
___
Policies and (un)subscribe information available here:
On Tue, 2010-05-04 at 20:48 -0300, Tigro Spottystripes wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Is the internal browser considered the viewer itself or can it have it's
own identifier?
From what I remember, it uses something like Second Life Viewer/VERSION
(Mozilla 4.0...)
