llMD5String

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

MD5String

llMD5String

	Security Warning!
	The MD5 hashing algorithm should not be used because it is too easy to generate collisions (two inputs which result in the same hash). http://www.kb.cert.org/vuls/id/836068

Summary

Function: string llMD5String( string src, integer nonce );

0.0	Forced Delay
10.0	Energy

Returns a string of 32 hex characters that is the  MD5 checksum of src with a  salt of ":"+nonce.

• string	src
• integer	nonce

Specification

nonce is casted to string, then appended to src after a colon (src+":"+(string)nonce). This is important to know if you are calculating a hash in another language and wish to compare with one calculated in LSL.

It is important to note here that llMD5String("example",0) != md5("example") but, llMD5String("example",0) == md5("example:0")

There is no similar md5() in LSL, because else LSL whould be to easy. It took me 2 hours to find out, 2 precious hours of my life.

LSL strings are stored in the UTF-8 format.

Examples

<lsl> llSay(0, llMD5String("Hello, Avatar!", 0)); // returns 112abd47ceaae1c05a826828650434a6 </lsl>

Linux Example

$ echo -n 'Hello, Avatar!:0' | openssl md5
112abd47ceaae1c05a826828650434a6

See Also

Functions

•

llSHA1String

Deep Notes

Signature
function string llMD5String( string src, integer nonce );