Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About StephanSwitch

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for all your answers! First I have to point out, that the only change to the viewer (that's under TOS of Linden) is reading a password from a special file, so I think this is correct: Obviously, the aim is to hide the password, so the user can't login with the default SL Viewer right away, but still, no deal with the viewer itself. Regarding this comment and the password trouble I wanna do it like this (Remember, nothing to do with the viewer, its a second step and can be done manually or with a javascript): The actual password will be encrypted, and split into two parts, data and key. Restoring the key is no problem, it just needs the two pieces of data. The user will be free to choose what to do with those two pieces. If the user decides to hold both parts, there's no problem at all I think. To summarize: The viewer will not do any changes ever to the user's account.
  2. Greetings everryone! I'm in need of some help understanding if a modification of a viewer is allowed or not. What I want to do is this: I take an existing viewer and add another login function. The user can still login with username / password combo just as usual. If there's a special password file, the viewer takes the hashed password from there and uses it for the login mechanic. That's the only change to the viewer. Am I allowed to do this and distribute the viewer? Regards, Steph
  • Create New...