Comments on: Slexchange ATM Script Cracked?

By: ATM Sales

ATM Sales — Fri, 13 Mar 2009 02:40:18 +0000

Interesting fact.The scripts above aren’t ATM scripts. They are excerpts from the SLX Magic Box, something you can’t use to steal things from SLX. Also to get script byte code from things, you have to own the stuff yourself. As the ATM aren’t given out, the ATMs so far are safe.

By: Anne Otoole

Anne Otoole — Wed, 07 May 2008 00:40:57 +0000

You children are such sucks, I could d a better email spam than any of you knuckle heads put together. LL just don’t have the experienced team to deal with this. They can’t even sort out the DB issues , they should hire a real coder then all you script kiddies would have nothing to do.
Oh I think its time for my Meds.

By: obi-wan

obi-wan — Mon, 05 May 2008 00:53:55 +0000

@DiSSENT said:”One can simply upload the bytecode as-is using an slproxy patch and then open it inworld with full perms to see the LSL code. ”

This is only speculation, once LSL is compiled to bytecode you cant open it again to see the LSL source code.

DISSENT its better you only say things you have actually done. Not quoting things you think maybe possible.

By: obi-wan

obi-wan — Sun, 04 May 2008 23:00:47 +0000

My questions is this, how do you get the bytecode of a LSL script that is no mod and no copy?

By: DiSSENT

DiSSENT — Sun, 04 May 2008 21:47:58 +0000

You’re right I am talking about disassembling LSO which does not turn back into LSL but does make it more readable.
One can simply upload the bytecode as-is using an slproxy patch and then open it inworld with full perms to see the LSL code. Why would this work? Because the client compiles scripts into .lso files in the cache and uploads those to the server. The server doesn’t know the difference between that and any other .lso file your client uploads. There are no permissions settings stored inside the lso and there is no unique encryption key generated by the client to verify ownership or anything.

here is an example of disassembled lso:

======== LSOAssembly ========
==== HeaderBlock ====
TM: 16384
VN: 512
BP: 16383
SP: 16383
HR: 333
HP: 476
CS: 0
NS: 0
CE: 0
IE: 0
ER: 0
FR: 0
SLR: 0
GVR: 100
GFR: 168
PR: 0
ESR: 0
SR: 168
NCE: 1
NIE: 0
NER: 4

==== StaticBlock ====
— StaticBlockHeader —
Size of header: 6
Type of object: Integer
StringData:
— Data —
00-00-00-7B

==== StaticBlock ====
— StaticBlockHeader —
Size of header: 6
Type of object: List
StringData:
— Data —
00-00-00-01

==== StaticBlock ====
— StaticBlockHeader —
Size of header: 6
Type of object: String
StringData:
— Data —
00-00-00-6E

==== StaticBlock ====
— StaticBlockHeader —
Size of header: 6
Type of object: Float
StringData:
— Data —
3F-9D-70-A4

==== StaticBlock ====
— StaticBlockHeader —
Size of header: 6
Type of object: Vector
StringData:
— Data —
41-F0-00-00-41-A0-00-00-41-20-00-00

==== StaticBlock ====
— StaticBlockHeader —
Size of header: 6
Type of object: Key
StringData:
— Data —
00-00-00-81

==== StateFrameBlock ====
Number of states: 1
— StatePointerBlock —
Offset: 16
EventMask: 4

==== StateBlock ====
— StateBlockHeader —
Size of header: 5
StringData:
— StateBlockHandler —
Pointer to code chunk: 8
Call frame size: 4

==== EventHandlerCodeChunk ====
— CodeChunkHeader —
Size of header: 5
StringData:
— Code —
63-5B-60-42-75-7A-7A-00-66-00-00-00-00-5C-5E-00-00-00-04-70-11-08-D1-01-24-5E-00-00-00-02-5E-00-00-00-01-75-11-92-01-00-00-00-23-63-5B-60-4E-6F-2E-20-46-41-49-4C-2E-00-66-00-00-00-00-5C-5E-00-00-00-04-70-11-08-D1-01-24-90-00-00-00-1B-63-5B-60-57-6F-6D-62-61-74-00-66-00-00-00-00-5C-5E-00-00-00-04-70-11-08-D1-01-24-63-5B-56-00-00-00-1A-66-00-00-00-00-5C-5E-00-00-00-04-70-11-08-D1-01-24-01-95
PUSHE
PUSHBP
PUSHARGS “Buzz”
PUSHARGE 0
PUSHSP
PUSHARGI 4
ADD Integer, Integer
POPBP
CALLLIB_TWO_BYTE 292
PUSHARGI 2
PUSHARGI 1
EQ Integer, Integer
JUMPNIF Integer, 35
PUSHE
PUSHBP
PUSHARGS “No. FAIL.”
PUSHARGE 0
PUSHSP
PUSHARGI 4
ADD Integer, Integer
POPBP
CALLLIB_TWO_BYTE 292
JUMP 27
PUSHE
PUSHBP
PUSHARGS “Wombat”
PUSHARGE 0
PUSHSP
PUSHARGI 4
ADD Integer, Integer
POPBP
CALLLIB_TWO_BYTE 292
PUSHE
PUSHBP
PUSHGS 26
PUSHARGE 0
PUSHSP
PUSHARGI 4
ADD Integer, Integer
POPBP
CALLLIB_TWO_BYTE 292
POP
RETURN

==== HeapBlock ====
Size of data: 24
Type of object: List
Reference count: 1
Data: 00-00-00-05-00-00-00-20-00-00-00-2B-00-00-00-36-00-00-00-44-00-00-00-57

==== HeapBlock ====
Size of data: 4
Type of object: Integer
Reference count: 1
Data: 00-00-00-00

==== HeapBlock ====
Size of data: 4
Type of object: Float
Reference count: 1
Data: 3F-80-00-00

==== HeapBlock ====
Size of data: 7
Type of object: String
Reference count: 1
Data: 32-20-6D-75-63-68-00

==== HeapBlock ====
Size of data: 12
Type of object: Vector
Reference count: 1
Data: 41-50-00-00-41-40-00-00-41-30-00-00

==== HeapBlock ====
Size of data: 16
Type of object: Rotation
Reference count: 1
Data: 40-80-00-00-40-40-00-00-40-00-00-00-3F-80-00-00

==== HeapBlock ====
Size of data: 12
Type of object: String
Reference count: 1
Data: 61-62-72-61-63-61-64-61-62-72-61-00

==== HeapBlock ====
Size of data: 1
Type of object: String
Reference count: 1
Data: 00

lso is actually binary but the information given to the herald was disassembled lso so that people could more clearly see what it is that they are dealing with. It looks much better too.

By: Day Oh

Day Oh — Sun, 04 May 2008 19:54:32 +0000

lol omg

By: Aidan Thornton

Aidan Thornton — Sun, 04 May 2008 17:51:42 +0000

whisper2u: I think you’re getting slightly mixed up. The usual trick is to capture the bytecode for your script, then upload a dummy script together with the actual bytecode. That way, if anyone reads the script, they won’t see the actual code. (I actually wrote some code to do this myself a while back, for other reasons.)

DiSSENT: I think you’re getting your decompilers confused with your disassemblers. Disassemblers for LSL are out there (there’s even one in the official client code, IIRC) and are probably enough for what you’re doing, but they don’t give you LSL source code back.

Melissa Yeuxdoux: having played around with LSL bytecode, the original variable names aren’t available anyway for recent code. Also, while it’s theoretically possible to decompile bytecode back to LSL (mainly because the compiler is really simple), I don’t know of anyone who’s done it. It’s not exactly trivial to do even for something this simple.

By: Montana Corleone

Montana Corleone — Sun, 04 May 2008 17:16:08 +0000

Hey guys I’m like SUPER raged and posting under like OVER A THOUSAND alts but too stupid to hide it.

By: Impressed By The Experts

Impressed By The Experts — Sun, 04 May 2008 15:37:14 +0000

So, we left it to the experts, and they, er, spammed themselves lol.

Worse than a dodgy construction worker.

This surely will win LULZ of the year, for complete incompetence, at next year’s LULZ conference. And the winner is: DiSSENT aka Adromor (I don’t want my SL business to get involved) Wierwight aka whisper2u aka d3eadlyc0ckup

By: whisper2u Can't Read

whisper2u Can't Read — Sun, 04 May 2008 15:20:57 +0000

Clearly, like all the kiddies who post here, and the staff of this joke of a site, whisper2u can’t read. Nowhere does it say anyone is mounting an army, twat.

Still, fact and truth never was exactly a strong point here was it? And calling an organisation after a wrestling competition is mature? lol. What are they going to do, wrestle prims to the ground? :-O

No wonder none of their campaigns work, it helps to be able to read before you can write.

Tell me, how is your spamming campaign coming on again boys? The apologies by DiSSENT *are* EPIC LULZ, lmfao.