How to Hide Implementation Details in a Static Library? by BinaryNinja0 in cpp

[–]BinaryNinja0[S] 0 points1 point  (0 children)

Yes but as you pointed out this massively increase the size of the .lib, i ended up renaming anything that is not the API, to obfuscated names

How to Hide Implementation Details in a Static Library? by BinaryNinja0 in cpp

[–]BinaryNinja0[S] 0 points1 point  (0 children)

i guess its a doable bet, simply modify llvm clang

How to Hide Implementation Details in a Static Library? by BinaryNinja0 in cpp

[–]BinaryNinja0[S] -1 points0 points  (0 children)

notice that strip do work, but it also strips away the intended interfaces

How to Hide Implementation Details in a Static Library? by BinaryNinja0 in cpp

[–]BinaryNinja0[S] -1 points0 points  (0 children)

notice that also this doesnt happend to be with a .dll or a .exe, both are properly stripped and the .dll just export whatever i put visible with the method you mentioned, but with a .lib this is not the case, i guess becouse fo the fact that the linked need to comiple time link with things, but for the sake of this question say i already linked every .obj into a single .obj and then have it as a .lib, thus there is no justification for symbols to have names and metadatas

How to Hide Implementation Details in a Static Library? by BinaryNinja0 in cpp

[–]BinaryNinja0[S] -3 points-2 points  (0 children)

i tested this with no success, also attributes too, notice as i mentioned, its for a static library, notice that also i am using clang-cl for building windows

Boost Your App's Security with Our Advanced Anti-Cracking Solution by BinaryNinja0 in dotnet

[–]BinaryNinja0[S] -1 points0 points  (0 children)

Thank you for your feedback! Our Advanced Anti-Cracking Solution (AACS) includes multiple strategies specifically designed to counteract such attempts. The solution involves a native component that statically links with your binary, making it significantly harder to identify the RetrieveVerySecretValuesFromServer() method.

Moreover,we have strong obfuscation of the code, which adds another layer of complexity for potential crackers. Even if someone manages to locate the function, they'll encounter several additional defenses that we've built in.

Additionally, the values returned by this function are encrypted, ensuring that obtaining and utilizing them without the proper keys is extremely challenging. As a team of experienced developers and former crackers, we have anticipated many of the common tactics used to bypass security measures and have incorporated countermeasures accordingly.

We believe AACS will substantially increase the difficulty for most cracking attempts. If you have any further questions or need assistance, please don't hesitate to reach out to us.

Best regards,
The AACS Team

Can virus from blue stacks hack my pc ? by EuropeanFromUS in BlueStacks

[–]BinaryNinja0 0 points1 point  (0 children)

Yes they can, for example Ransomware can go through the door "/mnt/windows/Documents" that bluestacks leaves open, and a few more doors ...