Qt-jambi-interest Archive, November 2007
Obfuscating jambi code
Message 1 in thread
Hello!
Anyone has any recommendation on which obfuscator to choose when
obfuscating Java code with massive use of jambi? We've been testing
proguard, but it seems that it has difficulty understanding the strings
beeing used in Jambi for signal/slot connections. If it renames a jambi
slot, then it must also rename the string beeing used in the signal
connection.
Any ideas?
Regards,
Helge Fredriksen
Message 2 in thread
maybe good not to use strings:
http://labs.trolltech.com/blogs/2007/09/28/when-you-dont-trust-strings/
On 11/3/07, Helge Fredriksen <hf@xxxxxxxxxxx> wrote:
>
> Hello!
>
> Anyone has any recommendation on which obfuscator to choose when
> obfuscating Java code with massive use of jambi? We've been testing
> proguard, but it seems that it has difficulty understanding the strings
> beeing used in Jambi for signal/slot connections. If it renames a jambi
> slot, then it must also rename the string beeing used in the signal
> connection.
>
> Any ideas?
>
> Regards,
> Helge Fredriksen
>
>
Message 3 in thread
You can use an AOT compiler, though I'm not sure if there AOT's for platforms other than windows.
Best regards,
Ron Ofir.
-------- Original Message --------
From: Helge Fredriksen <hf@xxxxxxxxxxx>
Apparently from: qt-jambi-interest-request@xxxxxxxxxxxxx
To: "qt-jambi-interest@xxxxxxxxxxxxx" <qt-jambi-interest@xxxxxxxxxxxxx>
Subject: Obfuscating jambi code
Date: Sat, 03 Nov 2007 21:01:29 +0100
> Hello!
>
> Anyone has any recommendation on which obfuscator to choose when
> obfuscating Java code with massive use of jambi? We've been testing
> proguard, but it seems that it has difficulty understanding the strings
> beeing used in Jambi for signal/slot connections. If it renames a jambi
> slot, then it must also rename the string beeing used in the signal
> connection.
>
> Any ideas?
>
> Regards,
> Helge Fredriksen
