|
Eddy Stryker
libsecondlife Developer
Join date: 6 Jun 2004
Posts: 353
|
07-21-2006 22:01
I've just finished a new service for LSL scripts that allows you to make RPC calls to my server to extend the ability of LSL scripts. Right now only one function exists, as a proof of concept: preg_match(). It takes a regular expression and a string and returns either 0 or 1 depending if a match was found. I have an LSL example that has a regex to match an e-mail address, so you can check whether a string is a valid e-mail or not.
I'm wondering what kind of functions would scripters find useful that aren't available in LSL? More string handling? Key generation or encryption? RSS feed grabbing? LindeX data and buy/sell functions?
_____________________
http://www.libsecondlife.org From: someone Evidently in the future our political skirmishes will be fought with push weapons and dancing pantless men. -- Artemis Fate
|
|
Eloise Pasteur
Curious Individual
Join date: 14 Jul 2004
Posts: 1,952
|
07-21-2006 23:25
Can I suggest that encryption is unlikely...
It's not meant as a personal attack, so sorry if it comes across that way... but how is it safe to send my data to you to be encrypted and sent back, to then be received and sent to you for decryption and sent back?
If I encrypt my data first with the admittedly poor lsl tools, I'm just adding more potential for interception, plus I'm trusting you not to store the data and have a nice big database of how to try and crack my poorly encrypted material. You might well be totally trustworthy, but trusting other people with encrypted data is kind of counter to the main thrust of encrypting it in the first place, no?
|
|
Eddy Stryker
libsecondlife Developer
Join date: 6 Jun 2004
Posts: 353
|
07-22-2006 00:56
Encryption is possible directly in LSL, even at reasonable speeds with some tricks. One of the issues though is getting keys. With this server setup you can have one account registered per user. A possible example would be script A calls generate_key which sends a private key to script A to use. script B calls get_key which sends the same private key to script B (where generate_key and get_key are linked to individual accounts, so no one else could get your keys), and now script A and B have a pre-shared key that can be used for whatever encryption routine you wish. Another example might be a direct Diffie-Hellman key exchange between script A and B, but outsource some of the heavier processing to the server so larger key generation is possible.
For reference though, none of the function calls or function parameters are ever logged on the server; this would slow down processing speed and create numerous privacy concerns. When it becomes officially available all RPC will be done through an SSL link to the server as well.
_____________________
http://www.libsecondlife.org From: someone Evidently in the future our political skirmishes will be fought with push weapons and dancing pantless men. -- Artemis Fate
|