I’m wondering about the best approach to “obfuscating” Elixir source code that needs to be available for a group of software developers as they need to use the components/functions but just the component API as the internals should be a black box. I had a recent case of a group leaving the company …

You can give them a service to hit rather than the code. Most things can be decompiled these days. Lawyers instead?

:slight_smile: Yes, but I prefer to avoid having troubles. And remember I want to have an “internal/component” API so that they can customise components that they use in their source code. I believe this is an interesting question…can we control what our extended developer team can access in term…

[image] NotQuiteLagom: I prefer to avoid having troubles. Sound to me this topic is entirely about creating troubles for yourself :stuck_out_tongue:

Obfuscated code like in JavaScript can still be easily deobfuscated. Providing .beam is not secure because they can be easily decompiled (even by hand).

The BEAM languages are compiled into a fairly transparent bytecode so you absolutely cannot make it as opaque as you would like.

I would definitely approach this from what decompilation tools are available and how user friendly they are. With .NET (though this may not be true now), I could decompile a release into somewhat full featured source code files and their respective project containers. Like beam languages, the code i…

IP protection is an org-level discussion, not just a technical one. Obfuscation is way down the list of things to think about - code is always exposed to being copied, decompiled etc by someone working on the codebase and honestly, the vast majority of the time it really makes no difference. Really…