James Seigel writes:
> It may be useful if you are trying to obfuscate how
> connections are being made, and hide protocols so
> that things stay secure.
Intercept bytecode on download.
Textual replace bogus names with valid ones.
Load the class.
It seems impossible to hide a protocol in native code
against off-line reverse engineering. It seems equally
impossible to prevent reflection and linking with
bytecode - chances are you don't even have to reverse
engineer it, you could possibly use it as black box.
I'd be very interested in solutions to encrypt network
transmissions in a way that can not be penetrated
when the client's owner is cooperating in the reverse
engineering (oh yeah), but compile time obfuscation does
not qualify IMO. I suspect this can't be solved in
software anyway.
b.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
