[sahapro33]

Decompile this test plug-in!

[WildCard65]

Originally Posted by sahapro33 Decompile this test plug-in!

So what exactly did you do to get an opcode "stackadjust"?

PHP Code:

/* ERROR PREPROCESSING! java.lang.Exception: Unrecognized opcode: stackadjust */
 function "bh" (number 1) 


Edit: stackadjust was nuked from SM 1.8

[asherkin]

This shit is pointless, there are only three ways it can go:

1. Lysis is updated to handle decompiling the modifications made to the plugin.
2. SourceMod is updated to reject loading plugins where modifications have been made to break Lysis.
3. Both of the above.

Eventually they will converge, and all plugin binaries will either be fully decompilable by Lysis or not load.

[SourceSamil]

Decompile that's pls

[sahapro33]

Originally Posted by WildCard65 So what exactly did you do to get an opcode "stackadjust"? PHP Code: /* ERROR PREPROCESSING! java.lang.Exception: Unrecognized opcode: stackadjust */  function "bh" (number 1)  Edit: stackadjust was nuked from SM 1.8

PHP Code:

public OnPluginStart() GroupId:CreateAdmGroup(""); 


[WildCard65]

Originally Posted by SourceSamil Decompile that's pls

PHP Code:

// Bad section size for section .tags. Trying to repair.
// Unknown section ".".
// Recovered name of previous section as ".___.natives".
// Unknown section "".
// Recovered name of previous section as "_dbg.info".
// Missing section ".dbg.info".
// Missing section ".dbg.natives".
// Section "_dbg.info" is probably (0.857143) missing section ".dbg.info".
// Section ".___.natives" is probably (0.600000) missing section ".dbg.natives". 


[Peace-Maker]

Originally Posted by sahapro33 Decompile this test plug-in!

PHP Code:

public bh()
{
    if (GetRandomInt(5, 6) == 4)
    {
        CreateAdmGroup("ddd");
    }
    return 0;
} 


Originally Posted by SourceSamil Decompile that's pls

That runs into an infinite loop because i didn't get to finish |break| and |continue| support in loops yet i guess. That's why some of the switches get so insanely large too, because they include the same blocks multiple times. I'll see if i get time to tackle them again anytime soon..

EDIT: Well, i took the time now. Here's what it might look like.

[friagram]

Originally Posted by asherkin This shit is pointless, there are only three ways it can go: Lysis is updated to handle decompiling the modifications made to the plugin. SourceMod is updated to reject loading plugins where modifications have been made to break Lysis. Both of the above. Eventually they will converge, and all plugin binaries will either be fully decompilable by Lysis or not load.

Why not just have all compiled plugins also contain a compressed copy of the plaintext SP, as well as checksums for the SP and binary data?
You can build in legacy support for this by having old plugins run through lysis and be repacked in this manner as they are first loaded.

If the plugin isn't correct, don't allow it to run.

[ImACow]

Originally Posted by friagram Why not just have all compiled plugins also contain a compressed copy of the plaintext SP, as well as checksums for the SP and binary data? You can build in legacy support for this by having old plugins run through lysis and be repacked in this manner as they are first loaded. If the plugin isn't correct, don't allow it to run.

1) Server gets compromised
2) Private plugins in the form of binaries are acquired
3) Profit.


now they have to decompile & actually do work to "steal" a binary

[Dr. McKay]

Originally Posted by ImACow 1) Server gets compromised 2) Private plugins in the form of binaries are acquired 3) Profit. now they have to decompile & actually do work to "steal" a binary

2 won't happen without 1. This is in no way a good reason for why this shouldn't be done.