[erlang-questions] Securing Erlang internals

[Mikl Kurkov]

In my current project I have a client part that will be deployed to untrusted
computers,
and I'm thinking about the ways of closing Erlang node internals from
inspection.
Now it's too easy to load some beams to erlang, run module_info and try to
run some interesting funs.
I understand that it's not possible to make it totaly secured as we have got
access to machine internals,
but I would like to make it not so easy as it is.
Ideally it should look like ordinal compiled program and to understand it
internals you will have
to disasm it.

For now I see several approaches:
1. SAE - not seems to work with R12B
2. Making some bundle of Erlang runtime, libs and app beams.  
As example - Silly SAE (http://git.erlang.geek.nz/?p=ssae.git;a=summary)
approach - loading beams from archive.
3. Making some source code obfuscation (renaming modules and exported
function to meaningless names).
As I'm not manipulate this names in app it seems to be possible to do.

So what would you suggest? May be someone already faced with such a task. 
May be there are some tools for bundling several files into one binary.

Thanks in advance,
Mikl

-- 
View this message in context: http://www.nabble.com/Securing-Erlang-internals-tp16273546p16273546.html
Sent from the Erlang Questions mailing list archive at Nabble.com.