c++ - Does symbol visibility protect shared library from abuse/crack? -
the gcc visibility feature enables strip off apis in our shared library don't want customer see. indeed can't use ldopen call hidden functions, wonder if secure enough protect our sensitive apis.
i want brief explanation of reliability/security of hidden apis in shared library, can balance effort , risk. asked question because can't find adequate description regarding concern in documentations of gcc.
please reopen question.
the genuine purpose visibility attribute library doesn't expose parts of aren't meant used directly. makes little difference trying crack it. still have disassemble code, , it's not terribly hard figure out entry points functions (have yourself!). yes, it's hard work work way through megabytes of code, experience know sort of things for, can skip on huge amount of code.
Comments
Post a Comment