1. This forum is ARCHIVED! Visit the new Cloud Sixteen forums, codename Eden, at https://eden.cloudsixteen.com. These forums will remain archived for a few months before being closed down, so try to encourage plugin developers to begin moving their content across to the new forums.
Dismiss Notice
Hi Guest, you need a Steam account to register and post on these forums. Login with Steam at the top of the forums to get started!
Dismiss Notice
Hi Guest, do you want to buy HL2RP or another Clockwork schema? Visit the Cloud Sixteen Store to get started!

Preventing plugin.ini modification

Discussion in 'Development' started by duck, Jun 27, 2014.

  1. duck

    duck Phant0m Legend

    Right, so here's a simple method to stop people from modifying your plugin.ini.

    http://i.imgur.com/Ev758Ys.png
    http://pastebin.pw/8nex4r

    It is very easily bypassed, but people that don't really know anything about Lua won't be able to do it unless told how. You should encrypt everything with CloudAuthX.
     
  2. Interesting way of protecting the integrity of your plugins, I like it. I'll probably be too lazy to start using this but it's definitely helpful.
     
  3. Polis

    Polis Guest

    Interesting and a little bit educational. Thanks. :)
     
  4. TheHipster

    TheHipster rhenz is a fairly decent fellow

    Duck has saved the day again from stopping scumbags from stealing plugins and claiming them as their own... Curses.. I will steal your plugins one day, Duck..
     
  5. Tomo742

    Tomo742 Guest

    All this does is stop idiots who don't know lua from doing it, however mix this in with a bunch of other encryptions that you're all making and it goes a long way. Cool.
     
  6. Better start writing obfuscated code am I right?
     
  7. Tomo742

    Tomo742 Guest

    However, while making obfuscated code may also protect your code further as well as encrypting it. It will never truly protect your code from a person who so wishes to get into it.
     
  8. Can't really see anyone being so horny for plugin code they'd go through decryption. But you never know.
     
  9. duck

    duck Phant0m Legend

    The code is meant to be encrypted. If you don't encrypt it, you a foo. If they're smart enough to know how to bypass this, they're probably smart enough to know how to make whatever your plugin is anyways.
     
  10. Polis

    Polis Guest

    -snip-
     
  11. Tydosius

    Tydosius I am deeply sorry.

    I'm still moderately amateur to coding, so I'd like to ask why the function to check whether anything was tampered with is there twice but in different sections, and how it knows whether it's a plugin or not by testing '!plugin'.

    Talking about the first post in the thread.
     
  12. Polis

    Polis Guest


    I just edited it again and finalized it so it may be a little more understandable now.

    It checks whether if it is first present and edited- it also checks if it is enabled/disabled twice so it knows whether to disable it or tell you whether it is disabled. Sorry if that's not clear, I don't have a way with words.


    !plugin basically checks if the plugin exists under the legitimate name. It is in different sections as the first section runs if it has been modified, and the second runs when 'else' (meaning anything 'else'), which also means un-modified in this case.

    Hopefully that makes sense...
     
  13. Polis

    Polis Guest

    -snip-
     
  14. sparkz

    sparkz FUCK! Clockwork Customer

    I'm getting into the whole plugin making and lua coding stuff. I might try this. Thanks!
     

Previous Readers (Total: 0)