Last 7 days

• Dec 24, 2009

  issue 32 (Remove const fields) commented on by alexandr...@yahoo.fr   -   this of course not a defect but just an enhancement

  this of course not a defect but just an enhancement
• Dec 24, 2009

  issue 32 (Remove const fields) reported by alexandr...@yahoo.fr   -   This just a small feature request. It would be really useful to remove (on demand) "const" fields to decrease as much as possible the size of an assembly.

  This just a small feature request. It would be really useful to remove (on demand) "const" fields to decrease as much as possible the size of an assembly.

Earlier this year

• Nov 27, 2009

  issue 31 (Microsoft SQL server 2005 does not accept fuscated assembly) Status changed by alberto.ferrazzoli   -   From image in attach seem that the problem is caused by invalid opcodes. You should obfuscate your assembly with option: --noinvalidopcodes Best regards Alberto

  Status: Accepted

  From image in attach seem that the problem is caused by invalid opcodes. You should obfuscate your assembly with option: --noinvalidopcodes Best regards Alberto

  Status: Accepted
• Nov 25, 2009

  issue 31 (Microsoft SQL server 2005 does not accept fuscated assembly) reported by Adm.SvSoft   -   What steps will reproduce the problem? 1. Create assembly, create function [Microsoft.SqlServer.Server.SqlFunction( DataAccess = DataAccessKind.None, IsDeterministic = true, IsPrecise = false, Name = "GetPointer", SystemDataAccess = SystemDataAccessKind.None)] public static long fun1() { ... } 2. comile, fiscate assembly 3. on Sql server run scrypt EXEC sp_configure 'clr enabled', 1; RECONFIGURE WITH OVERRIDE; GO CREATE ASSEMBLY [CLRPointerAssistant.MSSQL] FROM 'filename' GO I have got a message that the assembly failed verification. Not fuscated assembly works. Windows XP, SQL Server 2005 sp2

  What steps will reproduce the problem? 1. Create assembly, create function [Microsoft.SqlServer.Server.SqlFunction( DataAccess = DataAccessKind.None, IsDeterministic = true, IsPrecise = false, Name = "GetPointer", SystemDataAccess = SystemDataAccessKind.None)] public static long fun1() { ... } 2. comile, fiscate assembly 3. on Sql server run scrypt EXEC sp_configure 'clr enabled', 1; RECONFIGURE WITH OVERRIDE; GO CREATE ASSEMBLY [CLRPointerAssistant.MSSQL] FROM 'filename' GO I have got a message that the assembly failed verification. Not fuscated assembly works. Windows XP, SQL Server 2005 sp2
• Nov 24, 2009

  issue 30 (StringEncryption don't work with Mono) Status changed by alberto.ferrazzoli   -  

  Status: Accepted

  Status: Accepted
• Nov 23, 2009

  issue 30 (StringEncryption don't work with Mono) reported by JanRuedi...@web.de   -   --stringencrypt don't work with mono 2.4 Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for TestApp ---> System.InvalidProgram Exception: Invalid IL code in ?:DecryptString (string,int): IL_0003: stloc.0 at TestApp..ctor () [0x00000] at TestApp..cctor () [0x00000] in C:\TestApp\Core.cs:X --- End of inner exception stack trace --- at TestApp.Main () [0x00007] in C:\TestApp\Program.cs:Y

  --stringencrypt don't work with mono 2.4 Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for TestApp ---> System.InvalidProgram Exception: Invalid IL code in ?:DecryptString (string,int): IL_0003: stloc.0 at TestApp..ctor () [0x00000] at TestApp..cctor () [0x00000] in C:\TestApp\Core.cs:X --- End of inner exception stack trace --- at TestApp.Main () [0x00007] in C:\TestApp\Program.cs:Y
• Nov 06, 2009

  issue 29 (Babel msbuild task does not allow to set --noinvalidopcodes ...) changed by alberto.ferrazzoli   -  

  Status: Fixed

  Labels: Milestone-Release3.0.0.0

  Status: Fixed

  Labels: Milestone-Release3.0.0.0
• Nov 06, 2009

  issue 29 (Babel msbuild task does not allow to set --noinvalidopcodes ...) Status changed by alberto.ferrazzoli   -  

  Status: Accepted

  Status: Accepted
• Nov 05, 2009

  issue 29 (Babel msbuild task does not allow to set --noinvalidopcodes ...) reported by lesnikowski   -   It is possible to run babel from command line with two options: --noinvalidopcodes (compatible with 64bit machines) --nomsil (no issues on mono 2.4.2.3) What steps will reproduce the problem? When msbuild task is configured as follows: <PropertyGroup> <ObfuscateMsil>false</ObfuscateMsil> <EmitInvalidOpcodes>false</EmitInvalidOpcodes> </PropertyGroup> EmitInvalidOpcodes option is ignored. What is the expected output? What do you see instead? 1. You can see 'wow64' warning during obfuscation process. 2. Output assembly has 32BIT flag set: corflags XXX.dll Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 3.5.21022.8 Copyright (c) Microsoft Corporation. All rights reserved. Version : v2.0.50727 CLR Header: 2.5 PE : PE32 CorFlags : 11 ILONLY : 1 32BIT : 1 Signed : 1 Expected result: 1. No wow64 warning 2. Following corflags result: corflags XXX.dll Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 3.5.21022.8 Copyright (c) Microsoft Corporation. All rights reserved. Version : v2.0.50727 CLR Header: 2.5 PE : PE32 CorFlags : 9 ILONLY : 1 32BIT : 0 Signed : 1 What version of the product are you using? On what operating system? Babel 2.0.0.1

  It is possible to run babel from command line with two options: --noinvalidopcodes (compatible with 64bit machines) --nomsil (no issues on mono 2.4.2.3) What steps will reproduce the problem? When msbuild task is configured as follows: <PropertyGroup> <ObfuscateMsil>false</ObfuscateMsil> <EmitInvalidOpcodes>false</EmitInvalidOpcodes> </PropertyGroup> EmitInvalidOpcodes option is ignored. What is the expected output? What do you see instead? 1. You can see 'wow64' warning during obfuscation process. 2. Output assembly has 32BIT flag set: corflags XXX.dll Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 3.5.21022.8 Copyright (c) Microsoft Corporation. All rights reserved. Version : v2.0.50727 CLR Header: 2.5 PE : PE32 CorFlags : 11 ILONLY : 1 32BIT : 1 Signed : 1 Expected result: 1. No wow64 warning 2. Following corflags result: corflags XXX.dll Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 3.5.21022.8 Copyright (c) Microsoft Corporation. All rights reserved. Version : v2.0.50727 CLR Header: 2.5 PE : PE32 CorFlags : 9 ILONLY : 1 32BIT : 0 Signed : 1 What version of the product are you using? On what operating system? Babel 2.0.0.1
• Oct 28, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   Not yet. I have discussed this item with neverbirth in Babel discussion group and presently babel is not able to obfuscate "at once" assemblies so that all the public members are obfuscated without braking the whole application. Of course you can obfuscate multiple assemblies separately without a problem (all the public names remain untouched). This is a featue that I want to insert as soon as possible. Thank you, Alberto

  Not yet. I have discussed this item with neverbirth in Babel discussion group and presently babel is not able to obfuscate "at once" assemblies so that all the public members are obfuscated without braking the whole application. Of course you can obfuscate multiple assemblies separately without a problem (all the public names remain untouched). This is a featue that I want to insert as soon as possible. Thank you, Alberto
• Oct 27, 2009

  LeaveSomeNotes Wiki page commented on by ben.hildebrand.hit   -   Hi Alberto, i got quite exactly the same question as neverbirth! Is Babel in any way able to obfuscate a bunch of assemblies at once? I've got a WPF app consisting of an exe and several dlls, some of them dynamically linked at runtime. I'd really like to use Babel for obfuscation and then run the obfuscated assemblies against a setup project to distribute the stuff. PS: Good work until now :)

  Hi Alberto, i got quite exactly the same question as neverbirth! Is Babel in any way able to obfuscate a bunch of assemblies at once? I've got a WPF app consisting of an exe and several dlls, some of them dynamically linked at runtime. I'd really like to use Babel for obfuscation and then run the obfuscated assemblies against a setup project to distribute the stuff. PS: Good work until now :)
• Oct 21, 2009

  LeaveSomeNotes Wiki page commented on by neverbirth   -   Is Babel able to obfuscate multiple assemblies at once in order to correctly obfuscate references? I haven't seen any info regarding this subject, and wouldn't want to avoid obfuscating all public class and method names.

  Is Babel able to obfuscate multiple assemblies at once in order to correctly obfuscate references? I haven't seen any info regarding this subject, and wouldn't want to avoid obfuscating all public class and method names.
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) commented on by alberto.ferrazzoli   -   Ok the options seems correct: you used --noinvalidopcodes on x64 and that is fine. Now it will be useful to have your application to resolve this issue, better a simple test project that shows the same problem of your case. Best regards Alberto

  Ok the options seems correct: you used --noinvalidopcodes on x64 and that is fine. Now it will be useful to have your application to resolve this issue, better a simple test project that shows the same problem of your case. Best regards Alberto
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) commented on by i...@bohannongroup.com   -   I also tried a different computer, 32-bit windows XP, had same problem. I have a .net 2.0 Class Library dll and main.exe that i'm obfuscating , if I just obfuscate the Class Lib and not the .exe it seems to work.

  I also tried a different computer, 32-bit windows XP, had same problem. I have a .net 2.0 Class Library dll and main.exe that i'm obfuscating , if I just obfuscate the Class Lib and not the .exe it seems to work.
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) commented on by i...@bohannongroup.com   -   C:\Program Files\Babel>babel "c:\Documents and Settings\Administrator\My Documen ts\Visual Studio 2008\Projects\Tradeplan\StockScreener\bin\Release\StockScreener .exe" --noinvalidopcodes Processing StockScreener.exe ... Analyzing... Building call graph... Running Agent... Encrypting strings... Obfuscating msil... Obfuscating names... Writing c:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\Tradeplan\StockScreener\bin\Release\BabelOut\StockScreener.exe... Statistics: PostReader phase, elapsed time 00.062s Call Graph phase, elapsed time 00.093s Call graph nodes: 572 Call graph edges: 1092 Agent phase, elapsed time 00.156s Reflected enum types: 0 symbol(s) not obfuscated. Serializable types: 0 symbol(s) not obfuscated. Reflected type names: 0 symbol(s) not obfuscated. Reflected types: 1 symbol(s) not obfuscated. Attribute using type name: 0 symbol(s) not obfuscated. Symbol with attribute: 8 symbol(s) not obfuscated. Types derived: 1 symbol(s) not obfuscated. Encrypt Strings phase, elapsed time 00.062s Number of encrypted strings: 442 Control Flow Obfuscation phase, elapsed time 00.250s Number of iterations: 3 Number of obfuscated functions: 151 Average number of branch instruction per function: 5.125828 Type Obfuscation phase, elapsed time 00.109s Unicode normalization: True Flatten namespaces: True Virtual functions: True Symbols statistic: 3/[ 16] types: 18.75 % 0/[ 0] events: 0.00 % 99/[ 142] methods: 69.72 % 7/[ 21] properties: 33.33 % 222/[ 239] fields: 92.89 % 331/[ 418] overall: 79.19 % Emit phase, elapsed time 00.187s Total elapsed time (00:00:00.9218750)

  C:\Program Files\Babel>babel "c:\Documents and Settings\Administrator\My Documen ts\Visual Studio 2008\Projects\Tradeplan\StockScreener\bin\Release\StockScreener .exe" --noinvalidopcodes Processing StockScreener.exe ... Analyzing... Building call graph... Running Agent... Encrypting strings... Obfuscating msil... Obfuscating names... Writing c:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\Tradeplan\StockScreener\bin\Release\BabelOut\StockScreener.exe... Statistics: PostReader phase, elapsed time 00.062s Call Graph phase, elapsed time 00.093s Call graph nodes: 572 Call graph edges: 1092 Agent phase, elapsed time 00.156s Reflected enum types: 0 symbol(s) not obfuscated. Serializable types: 0 symbol(s) not obfuscated. Reflected type names: 0 symbol(s) not obfuscated. Reflected types: 1 symbol(s) not obfuscated. Attribute using type name: 0 symbol(s) not obfuscated. Symbol with attribute: 8 symbol(s) not obfuscated. Types derived: 1 symbol(s) not obfuscated. Encrypt Strings phase, elapsed time 00.062s Number of encrypted strings: 442 Control Flow Obfuscation phase, elapsed time 00.250s Number of iterations: 3 Number of obfuscated functions: 151 Average number of branch instruction per function: 5.125828 Type Obfuscation phase, elapsed time 00.109s Unicode normalization: True Flatten namespaces: True Virtual functions: True Symbols statistic: 3/[ 16] types: 18.75 % 0/[ 0] events: 0.00 % 99/[ 142] methods: 69.72 % 7/[ 21] properties: 33.33 % 222/[ 239] fields: 92.89 % 331/[ 418] overall: 79.19 % Emit phase, elapsed time 00.187s Total elapsed time (00:00:00.9218750)
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) commented on by alberto.ferrazzoli   -   Sorry one question again. Can you post also the babel command line used to obfuscate the application? Bye

  Sorry one question again. Can you post also the babel command line used to obfuscate the application? Bye
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) Status changed by alberto.ferrazzoli   -   Can you post the assembly that give this problem? Thank you

  Status: Accepted

  Can you post the assembly that give this problem? Thank you

  Status: Accepted
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) commented on by i...@bohannongroup.com   -   Actually it was running fine with an earlier release build, but when I rebuilt my release version and obfuscated it, it now crashes just like the obfuscated debug version did.

  Actually it was running fine with an earlier release build, but when I rebuilt my release version and obfuscated it, it now crashes just like the obfuscated debug version did.
• Oct 14, 2009

  issue 28 (Minor issue: can't execute debug version of my app when its ...) reported by i...@bohannongroup.com   -   What steps will reproduce the problem? 1. obfuscated the .net 20 debug assemblies of my app 2. ran the .exe the babel\output 3. I immediately get the "this program has stopped working" popup What is the expected output? What do you see instead? app should run. it doesn't What version of the product are you using? On what operating system? Vista X64, babel 2.0.0.1 Please provide any additional information below. (Babel works just fine on my release build) Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: stockscreener.exe Problem Signature 02: 1.0.0.0 Problem Signature 03: 4ad63105 Problem Signature 04: System Problem Signature 05: 2.0.0.0 Problem Signature 06: 4889de7a Problem Signature 07: 352a Problem Signature 08: 91 Problem Signature 09: TZGQR4KTZ5CLNKYMWU2XGQWCJZ00C3RA OS Version: 6.0.6001.2.1.0.256.4 Locale ID: 1033 Read our privacy statement: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

  What steps will reproduce the problem? 1. obfuscated the .net 20 debug assemblies of my app 2. ran the .exe the babel\output 3. I immediately get the "this program has stopped working" popup What is the expected output? What do you see instead? app should run. it doesn't What version of the product are you using? On what operating system? Vista X64, babel 2.0.0.1 Please provide any additional information below. (Babel works just fine on my release build) Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: stockscreener.exe Problem Signature 02: 1.0.0.0 Problem Signature 03: 4ad63105 Problem Signature 04: System Problem Signature 05: 2.0.0.0 Problem Signature 06: 4889de7a Problem Signature 07: 352a Problem Signature 08: 91 Problem Signature 09: TZGQR4KTZ5CLNKYMWU2XGQWCJZ00C3RA OS Version: 6.0.6001.2.1.0.256.4 Locale ID: 1033 Read our privacy statement: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
• Sep 25, 2009

  LeaveSomeNotes Wiki page edited by alberto.ferrazzoli   -   Revision r35 Edited wiki page through web user interface.

  Revision r35 Edited wiki page through web user interface.
• Sep 23, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   Yes correct. After babel obfuscation, original pdb file does not work because they are no more aligned with the assembly. This feature was removed because babel now does not depends from Phoenix anymore. The pdb file is a feature I'd like to have in a future release but now is not on top of my list. Bye

  Yes correct. After babel obfuscation, original pdb file does not work because they are no more aligned with the assembly. This feature was removed because babel now does not depends from Phoenix anymore. The pdb file is a feature I'd like to have in a future release but now is not on top of my list. Bye
• Sep 22, 2009

  LeaveSomeNotes Wiki page commented on by hl7spy   -   Hi Alberto, 2.0 is working great for me. Thank you. I noticed in your release notes that .pdb file support was removed. Does this mean that pdb generated by VS will, or will not work, with the babeled binary? From my experimenting it looks like the pdb will not work. Can you please confirm? Thanks in advance

  Hi Alberto, 2.0 is working great for me. Thank you. I noticed in your release notes that .pdb file support was removed. Does this mean that pdb generated by VS will, or will not work, with the babeled binary? From my experimenting it looks like the pdb will not work. Can you please confirm? Thanks in advance
• Sep 21, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) Status changed by alberto.ferrazzoli   -  

  Status: Fixed

  Status: Fixed
• Sep 21, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) Status changed by alberto.ferrazzoli   -  

  Status: Fixed

  Status: Fixed
• Sep 21, 2009

  issue 24 (Part of .dll is probably lost with Babel 2.0.0.1) Status changed by alberto.ferrazzoli   -  

  Status: Fixed

  Status: Fixed
• Sep 18, 2009

  issue 13 (Unresolved virtual symbol) Status changed by alberto.ferrazzoli   -  

  Status: Fixed

  Status: Fixed
• Sep 17, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) commented on by alberto.ferrazzoli   -   Should be a problem due to dependency properties. Thank you.

  Should be a problem due to dependency properties. Thank you.
• Sep 17, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) Status changed by alberto.ferrazzoli   -  

  Status: Started

  Status: Started
• Sep 15, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) commented on by alberto.ferrazzoli   -   Yes sure at: alberto.ferrazzoli@gmail.com Bye

  Yes sure at: alberto.ferrazzoli@gmail.com Bye
• Sep 15, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) commented on by inside686   -   I have created a test project that uses the obfuscated assembly and it works so I tried to remove as possible things I could in the original project in order to discover the problem. Now original project and test project are almost identical, one is loading the obfuscated assembly and the other no. I can't understand what is going wrong in the original project. Could I send you both project privately ?

  I have created a test project that uses the obfuscated assembly and it works so I tried to remove as possible things I could in the original project in order to discover the problem. Now original project and test project are almost identical, one is loading the obfuscated assembly and the other no. I can't understand what is going wrong in the original project. Could I send you both project privately ?
• Sep 15, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) commented on by alberto.ferrazzoli   -   Can you upload the VS solution or a test project to reproduce the issue ?

  Can you upload the VS solution or a test project to reproduce the issue ?
• Sep 15, 2009

  issue 27 (Ofuscating silverlight assemby in xap package) reported by inside686   -   What steps will reproduce the problem? 1. Unzipping xap package 2. Using babel (babel.exe sl3assembly.dll --noildasm --nomsil --noinvalidopcodes) > Assembly is ofuscated without problem 3. Zipping files with ofuscated assembly to xap package 4. "View in Browser" in VS (run without compilation) What is the expected output? -To visualize the silverlight website. What do you see instead? -The browser page remains blank. What version of the product are you using? On what operating system? -Last version on Windows XP pro Please provide any additional information below. -Version of Silverlight: 3 GDR2 (last release)

  What steps will reproduce the problem? 1. Unzipping xap package 2. Using babel (babel.exe sl3assembly.dll --noildasm --nomsil --noinvalidopcodes) > Assembly is ofuscated without problem 3. Zipping files with ofuscated assembly to xap package 4. "View in Browser" in VS (run without compilation) What is the expected output? -To visualize the silverlight website. What do you see instead? -The browser page remains blank. What version of the product are you using? On what operating system? -Last version on Windows XP pro Please provide any additional information below. -Version of Silverlight: 3 GDR2 (last release)
• Sep 14, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   Xap package are not managed yet. You should first unzip the xap. If you find some problem with Silverlight application, please submit an issue to the bug traking (ISSUES tab that you find at the top of this page). Bye.

  Xap package are not managed yet. You should first unzip the xap. If you find some problem with Silverlight application, please submit an issue to the bug traking (ISSUES tab that you find at the top of this page). Bye.
• Sep 14, 2009

  LeaveSomeNotes Wiki page commented on by inside686   -   Ok, thank you. Just one more question: If I obfuscate a silverlight project, in the command line <assembly file> should be the path of the xap package or should I first unzip the xap file and use babel on the dll inside ?

  Ok, thank you. Just one more question: If I obfuscate a silverlight project, in the command line <assembly file> should be the path of the xap package or should I first unzip the xap file and use babel on the dll inside ?
• Sep 09, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) commented on by alberto.ferrazzoli   -   Hello. I have obfuscated your dll. Unfortunately the only thing I can test is a babel crash (and this not happens). To analyze the bug it is necessary to have a liitle VS solution that reproduce this issue at least. I know that 99% of the time is not possible upload the origina VS project, that's understandable. So you may prepare an example solution that resonably reproduce your problem. Run your obfuscated dll under the debugger and try to find the point where the crash occurs. You may be helped by disabling namespace obfuscation and type name obfuscation: --noflatns --notypes when you spot the bug prepare a project that can be run into the debugger. I will help you and release a new version of babel as soon as possible. Bye

  Hello. I have obfuscated your dll. Unfortunately the only thing I can test is a babel crash (and this not happens). To analyze the bug it is necessary to have a liitle VS solution that reproduce this issue at least. I know that 99% of the time is not possible upload the origina VS project, that's understandable. So you may prepare an example solution that resonably reproduce your problem. Run your obfuscated dll under the debugger and try to find the point where the crash occurs. You may be helped by disabling namespace obfuscation and type name obfuscation: --noflatns --notypes when you spot the bug prepare a project that can be run into the debugger. I will help you and release a new version of babel as soon as possible. Bye
• Sep 09, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) Status changed by alberto.ferrazzoli   -   Thank you.

  Status: Started

  Thank you.

  Status: Started
• Sep 09, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) commented on by paulgcook   -   Hi, I've attached an assembly that cannot be obfuscated. Can you take a look and see if theres a fix for it? It may just require a combination of settings I haven't found yet. Thanks, Paul.

  Hi, I've attached an assembly that cannot be obfuscated. Can you take a look and see if theres a fix for it? It may just require a combination of settings I haven't found yet. Thanks, Paul.
• Sep 06, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) commented on by alberto.ferrazzoli   -   Sorry for that. I'd like to improve Silverlight compatibility next version of babel. Please upload any assembly that was broken by babel. Bye

  Sorry for that. I'd like to improve Silverlight compatibility next version of babel. Please upload any assembly that was broken by babel. Bye
• Sep 06, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) commented on by paulgcook   -   Hello again! I've tried obfuscating another assembly in my project and unfortunately have run into another problem. Are there any other switches you recommend trying? Will you be able to spend any time on Silverlight compatibility in the near future? Thanks, Paul.

  Hello again! I've tried obfuscating another assembly in my project and unfortunately have run into another problem. Are there any other switches you recommend trying? Will you be able to spend any time on Silverlight compatibility in the near future? Thanks, Paul.
• Sep 05, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   Recently I got an issue with silverlight project and babel 2.0.0.1 The workaround is to obfuscate with options: --noildasm --nomsil --noinvalidopcodes The fixes will be released with the next version of babel Bye

  Recently I got an issue with silverlight project and babel 2.0.0.1 The workaround is to obfuscate with options: --noildasm --nomsil --noinvalidopcodes The fixes will be released with the next version of babel Bye
• Sep 05, 2009

  LeaveSomeNotes Wiki page commented on by inside686   -   Hello, Does Babelobfuscator support Silverlight projects?

  Hello, Does Babelobfuscator support Silverlight projects?
• Sep 02, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) commented on by paulgcook   -   Hi, I have ended up using the following options: --nomethods --noinvalidopcodes --noildasm I had to add --nomethods to the list as I was getting an Xaml error. Viewing the obfuscated assembly now crashes Reflector ;-) ! For now I have added a post-build event, however I would prefer to get it running with buildtargets but I cannot get it configured correctly. Its not major but would be nice to have. Thanks for your help, Paul.

  Hi, I have ended up using the following options: --nomethods --noinvalidopcodes --noildasm I had to add --nomethods to the list as I was getting an Xaml error. Viewing the obfuscated assembly now crashes Reflector ;-) ! For now I have added a post-build event, however I would prefer to get it running with buildtargets but I cannot get it configured correctly. Its not major but would be nice to have. Thanks for your help, Paul.
• Sep 01, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) Status changed by alberto.ferrazzoli   -   I have good news, the bug was fixed. I have to say that your project was very usefull and well arranged, thank you for that. The problem was due to two different things. First a little bug on Metadata header that force 32 bit required even when no msil obfuscation is required. Second is a difference between Silverlight and the standard framework. SL2 does not have SuppressIldasmAttribute type so an exceprion is raisen because this type is required when babel run with standrd options. I'll release a fix as soon as possible. Meanwhile I think there is a work-around with babel 2.0.0.1 try to run obfuscation with following options: --nomsil --noinvalidopcodes --noildasm Thank you again. Best Regards.

  Status: Fixed

  I have good news, the bug was fixed. I have to say that your project was very usefull and well arranged, thank you for that. The problem was due to two different things. First a little bug on Metadata header that force 32 bit required even when no msil obfuscation is required. Second is a difference between Silverlight and the standard framework. SL2 does not have SuppressIldasmAttribute type so an exceprion is raisen because this type is required when babel run with standrd options. I'll release a fix as soon as possible. Meanwhile I think there is a work-around with babel 2.0.0.1 try to run obfuscation with following options: --nomsil --noinvalidopcodes --noildasm Thank you again. Best Regards.

  Status: Fixed
• Sep 01, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) Status changed by alberto.ferrazzoli   -   Thank you.

  Status: Started

  Thank you.

  Status: Started
• Sep 01, 2009

  issue 25 (Sys.InvalidOperationExceprion: InitializeError error #2105 i...) commented on by paulgcook   -   Hi, I have put together a small solution which demonstrates the problem. You should be able to just load this up in VS2008 (with SL2 sdk) and run it. Take a look at the ObfuscateTest project you'll see the References folder. If you reference the assembly in the Bin\Debug of the GanttChartControls project then the app loads okay. If you reference the assembly in Bin\Debug\BabelOut then you get the error. Here is my targets file - I have disabled nearly everything: <FlattenNamespaces>false</FlattenNamespaces> <UnicodeNormalization>false</UnicodeNormalization> <ObfuscateTypes>false</ObfuscateTypes> <ObfuscateEvents>false</ObfuscateEvents> <ObfuscateMethods>false</ObfuscateMethods> <ObfuscateProperties>false</ObfuscateProperties> <ObfuscateFields>false</ObfuscateFields> <VirtualFunctions>false</VirtualFunctions> <ObfuscateMsil>false</ObfuscateMsil> <ILIterations>3</ILIterations> <EmitInvalidOpcodes>false</EmitInvalidOpcodes> <StringEncryption>false</StringEncryption> <SuppressIldasm>false</SuppressIldasm> <DeadCodeElimination>false</DeadCodeElimination> <ShowStatistics>false</ShowStatistics> <VerboseLevel>2</VerboseLevel>

  Hi, I have put together a small solution which demonstrates the problem. You should be able to just load this up in VS2008 (with SL2 sdk) and run it. Take a look at the ObfuscateTest project you'll see the References folder. If you reference the assembly in the Bin\Debug of the GanttChartControls project then the app loads okay. If you reference the assembly in Bin\Debug\BabelOut then you get the error. Here is my targets file - I have disabled nearly everything: <FlattenNamespaces>false</FlattenNamespaces> <UnicodeNormalization>false</UnicodeNormalization> <ObfuscateTypes>false</ObfuscateTypes> <ObfuscateEvents>false</ObfuscateEvents> <ObfuscateMethods>false</ObfuscateMethods> <ObfuscateProperties>false</ObfuscateProperties> <ObfuscateFields>false</ObfuscateFields> <VirtualFunctions>false</VirtualFunctions> <ObfuscateMsil>false</ObfuscateMsil> <ILIterations>3</ILIterations> <EmitInvalidOpcodes>false</EmitInvalidOpcodes> <StringEncryption>false</StringEncryption> <SuppressIldasm>false</SuppressIldasm> <DeadCodeElimination>false</DeadCodeElimination> <ShowStatistics>false</ShowStatistics> <VerboseLevel>2</VerboseLevel>
• Aug 31, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   Ok babel.exe has this protection from early version when encrypted string was introduced. The default encryption of string is a simple xor on string bytes. Instead babel.exe define two custom method EncryptString and DecryptString that use the public key as key to decrypt/encrypt the string in babel.exe. This kind of protection can be implemented by every babel user by means of writing these two methods, it'is quite simple to do. See babel html help document to get the method signature and detailed description of string encryption.

  Ok babel.exe has this protection from early version when encrypted string was introduced. The default encryption of string is a simple xor on string bytes. Instead babel.exe define two custom method EncryptString and DecryptString that use the public key as key to decrypt/encrypt the string in babel.exe. This kind of protection can be implemented by every babel user by means of writing these two methods, it'is quite simple to do. See babel html help document to get the method signature and detailed description of string encryption.
• Aug 31, 2009

  LeaveSomeNotes Wiki page commented on by fakhru.rahman   -   It's passed Assembly.GetName().GetPublicKey() as key for encrypt and decrypt string. So altering assembly and resign it simple make decryption fail, it's was easy to compromize, but better than simply encrypt string alone. And is BabelObfuscator support obfuscation public classes except Serialize type ?

  It's passed Assembly.GetName().GetPublicKey() as key for encrypt and decrypt string. So altering assembly and resign it simple make decryption fail, it's was easy to compromize, but better than simply encrypt string alone. And is BabelObfuscator support obfuscation public classes except Serialize type ?
• Aug 31, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   What is binding string encryption into assembly token ?

  What is binding string encryption into assembly token ?
• Aug 30, 2009

  LeaveSomeNotes Wiki page commented on by alberto.ferrazzoli   -   I don't know SmartAssembly. Plase tell me about binding string encryption into assembly token, what does it means? Thank you.

  I don't know SmartAssembly. Plase tell me about binding string encryption into assembly token, what does it means? Thank you.
• Aug 30, 2009

  LeaveSomeNotes Wiki page commented on by fakhru.rahman   -   Any plan add cache string decryption value, and binding string encryption into assembly token like SmartAssembly do ?

  Any plan add cache string decryption value, and binding string encryption into assembly token like SmartAssembly do ?