mezz0 Member Joined Jul 10, 2010 Messages 680 Reaction score 10 Nov 5, 2010 #1 How do I go about to compile a botbase as dll and obfuscated with {SA} ? Do I need to purchase a {sa} licence for that ?
How do I go about to compile a botbase as dll and obfuscated with {SA} ? Do I need to purchase a {sa} licence for that ?
Apoc Well-Known Member Joined Jan 16, 2010 Messages 2,790 Reaction score 94 Nov 5, 2010 #2 The DLL would not be loaded by HB without someone from the HB staff adding it to the allow list. We also prefer that 3rd parties don't obfuscate their code for obvious security reasons.
The DLL would not be loaded by HB without someone from the HB staff adding it to the allow list. We also prefer that 3rd parties don't obfuscate their code for obvious security reasons.
mezz0 Member Joined Jul 10, 2010 Messages 680 Reaction score 10 Nov 5, 2010 #3 I understand your security concerns. What other means are at our disposal to protect our code ? Besides simply not releasing it ?
I understand your security concerns. What other means are at our disposal to protect our code ? Besides simply not releasing it ?
Apoc Well-Known Member Joined Jan 16, 2010 Messages 2,790 Reaction score 94 Nov 5, 2010 #4 Usually one of the devs will obfuscate your code for you (with an embedded bit of info to ensure it was obfuscated by us). However, we are quite busy, so it usually won't happen 'right away'.
Usually one of the devs will obfuscate your code for you (with an embedded bit of info to ensure it was obfuscated by us). However, we are quite busy, so it usually won't happen 'right away'.
fpsware Community Developer Joined Jan 15, 2010 Messages 5,287 Reaction score 133 Nov 5, 2010 #5 mezz0 said: I understand your security concerns. What other means are at our disposal to protect our code ? Besides simply not releasing it ? Click to expand... 1. Don't release it. 2. I have nothing further. Take it from someone who has flogged this horse until it was ground into dust. Either release it as source or keep it private.
mezz0 said: I understand your security concerns. What other means are at our disposal to protect our code ? Besides simply not releasing it ? Click to expand... 1. Don't release it. 2. I have nothing further. Take it from someone who has flogged this horse until it was ground into dust. Either release it as source or keep it private.
mezz0 Member Joined Jul 10, 2010 Messages 680 Reaction score 10 Nov 5, 2010 #6 Keeping it private will probably be the way to go.. Thanks for the feedback !