Obfuscation of a C ++ shared library

I was asked to help obfuscate the library (written in C ++), which will be distributed to clients. I have already discussed why obfuscation is not necessarily a good idea, and when I see that licensing will be integrated into software, many of the problems associated with copy protection are controversial.

Despite this, I was asked to research the methods anyway. I searched for the title (etc.), as well as HARES, but I can’t find much that I can use for the library (naturally, these things can destroy any form of API that would be useless for the library).

What methods can I apply that will work for libraries? Although I would appreciate recommendations regarding tools (or compiler flags, etc.) that might be useful, I would like to emphasize that this is not a tool-oriented issue (i.e., Closed), but rather oriented on applicable methods.

+4
source share
2 answers

I would not put much effort into this very carefully, because the reverse engineer will win this round.

https://softwareengineering.stackexchange.com/questions/155131/is-it-important-to-obfuscate-c-application-code

Obfuscating ++ - . , , - , IDA Pro , , .

  • .

, , - , - . - , STL, .

  • ,

- . -, , ollydbg.

. , , , . , RE, .

  • , .

, . .

  • , - . , , , . - , .

  • , 20- .

  • , .

  • , , , -.

, , ++ . C (, , Java), . , API OpenGl, .

, - . , . , . , .

, . , , .

+5

, , 2 ,

  • Disassembley

, , , , ( decrypter )

, , , , .

, - "" (, , , , ,

+1

All Articles