Money Chair Casino security/encription.

Money Chair Casino security/encription.

My friend made one it works well hes done a nice job but thing I feel he maybe lacking is the encription and other secure ways to operate one of these machines.

Could somone give hints or maybe ideas of how to secure one more. With adding in encription how to add it or guides to encription aswell security with objects talking to each other on a secure channal using encription.

Thanks

I recommend triple-rot-13. It's the same basic idea as triple-DES, but much simpler.

there more info or links to this.

Thanks

Paraphrasing Opus: "As god is my witness, I have no idea what to say."

Jessy, I think he's just kidding you. Rot13 is not good encryption.

The Wiki has some sample code for doing encryption:

http://secondlife.com/badgeo/wakka.php?wakka=llXorBase64Strings

You need to put a secret password in each object's script that will communicate together. If they have the same password and nobody else knows it, nobody else can listen in or send fake messages. The Wiki shows how to do the actual encryption using the password.

Note that the function llXorBase64Strings has been replaced by llXorBase64StringsCorrect, and that one should be used instead, but otherwise the code in the Wiki is still a good example.

I personally use a Caesar cipher with a shift of 26; this has all the security of triple rot13 but is more efficent to implement in software.

I suggest you do some research into encryption to find what is suitable for your needs.

You're right, it's O(1), where triple-rot13 is O(n). Brilliant!

As for the original poster, if you're looking for help with camping chairs you're lucky you're getting nothing worse than jokes.

LOL!!! You had me there. I didn't get that until I read Argent's reply

If having pre-shared secrets is not possible or feasible in your situation you can always use a Diffie-Hellman key exchange (/15/57/98941/1.html#post979014). Out of the methods readily available in LSL I would prefer 16/32 bit RSA encryption. Another good measure of security is after the Diffie-Hellman exchange, use the MD5 hash of your new secret converted to an integer as the channel to communicate on. Having a random communication channel will add a nice layer of obscurity, and having the messages flowing across it encrypted is the security. Also if you know what objects you are going to be communicating with ahead of time you can make a whitelist in the code and ignore messages from anything not on it. If you know what object you want to address and the message isn't time critical consider using llEmail instead, keeping your message hidden away from everyone but the two objects and the Lindens.

When designing a security system, here are some basics to look at with communication.

* Why do I trust this incoming message? Can I be sure it's coming from a trusted source?
* What barriers are in place to prevent untrusted sources reading this channel? What is allowing a trusted source to read it but untrusted sources not to?
* Does this information need to be secure? Would the system only be affected by an injected message from an untrusted source, or does merely reading the channel communication compromise the system?