tag:blogger.com,1999:blog-7808773133895502659.post7215778636310228998..comments2022-04-07T13:13:29.961+02:00Comments on Babel Obfuscator: Plans for next release v.1.4Alberto Ferrazzolihttp://www.blogger.com/profile/04139326250440208057noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-7808773133895502659.post-21497516045436868702008-12-18T18:00:00.000+01:002008-12-18T18:00:00.000+01:00Thanks Alberto, I think that the solution will be ...Thanks Alberto, I think that the solution will be good. As long as a typical amateur using Reflector or other such tool can't view the code, I'm cool with it. I can't be too paranoid about it, as I'm well aware that if someone really wants to read my code, they will find a way to do it. :) Thanks again!Unknownhttps://www.blogger.com/profile/09342909223700545675noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-2287429923024272362008-12-16T21:16:00.000+01:002008-12-16T21:16:00.000+01:00Hello Nathaniel,Yes issue 8 the one that make me l...Hello Nathaniel,<BR/>Yes issue 8 the one that make me losing sleep :).<BR/>I am joking. Good work Nathaniel and thank you again for your help and time.<BR/><BR/>Ok 64 bit compatibility is the most important issue at the moment.<BR/>As I wrote in the original post, this incompatibility seem to be originated by the invalid IL opcodes inserted by babel to hide the inner method opcodes.<BR/><BR/>First of all I think that this kind of obfuscation is weak (but sometime useful) and does not add to much to the IL scrambling performed by the software.<BR/><BR/>In the next version of babel this feature will not be removed completely. Instead I have added the possibility to switch it off.<BR/>So if you compile for 64 bit as well as 32 bit targets you have just to turn it off.<BR/><BR/>The command line option that turn off bad IL opcode injection is now named:<BR/><BR/>--[no]invalidopcodes<BR/>Emit invalid opcodes (default: enabled)<BR/><BR/>As you can see it is enabled by default. <BR/>So any time you compile for 64bit you need to add to the babel command line the switch<BR/><BR/>--noinvalidopcodes<BR/> <BR/>What is your opinion about this option?<BR/>Do you like it?<BR/><BR/>Now, I am writing a set of helper classes that allow me to generate easily managed types within Phoenix. This because I want to add in babel some ready made string encryption methods.<BR/>This task is not easy and will take me a lot of time.<BR/>The agent feature is ready and it will be the most important feature for the next release. Hope you like it.<BR/><BR/>Thank you for all, and have a you a Wonderful Christmas time.<BR/><BR/>Bye.Alberto Ferrazzolihttps://www.blogger.com/profile/04139326250440208057noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-4911008166758454532008-12-16T17:40:00.000+01:002008-12-16T17:40:00.000+01:00Hi Alberto, I was the one that reported that issue...Hi Alberto, I was the one that reported that issue about 64 bit compatibility. I would have to say that it would be very important in my case to have 64 bit functionality because of the nature of the code that I am obfuscating. I re-host the Windows Workflow Foundation designer in my application, and it uses an internal .NET compiler to output stand-alone workflow executable files. Unfortunately, the .NET class does not allow me to specify a target platform for the build, so if it's built on a 64 bit OS, it will output a 64 bit assembly. Since the dlls that it references are all obfuscated using babel, they are references in WOW64 mode, and therefore do not work. My option would be to use 'corflags' on the resulting assembly, but that's very clunky and I don't even know if I can redistribute corflags. <BR/><BR/>Secondly, having all obfuscated dlls run in 32 bit mode kind of defeats any performance gains that one could get being able to use 64 bit mode. <BR/><BR/>Hopefully I've made my case...I'm voting for 64 bit compatibility to be in the next release :) Have a good holiday, and thanks for working on such a great product!Unknownhttps://www.blogger.com/profile/09342909223700545675noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-32078714776541233842008-11-25T20:07:00.000+01:002008-11-25T20:07:00.000+01:00Ok I'll try to update the Wiki page athttp://code....Ok I'll try to update the Wiki page at<BR/><BR/>http://code.google.com/p/babelobfuscator/wiki/BabelRules<BR/><BR/>With more rules.<BR/><BR/>Anyway there is an open issue with 64 bit operating systems see:<BR/><BR/>http://code.google.com/p/babelobfuscator/issues/detail?id=8<BR/><BR/>may be you found the same problem.<BR/><BR/>Bye.Alberto Ferrazzolihttps://www.blogger.com/profile/04139326250440208057noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-46787540215779338292008-11-25T06:15:00.000+01:002008-11-25T06:15:00.000+01:00I'm all for the changes you outline for version 1....I'm all for the changes you outline for version 1.4.<BR/><BR/>It would be great to have some rules file example, or default that fixes the enum issue you address. <BR/><BR/>I've been using the babel for quite some time and are very happy with. It is just that every now and then I run into a problem which is diffifult to resolve, and at times forces me to NOT obfuscate the code. This is more common when I use the obfuscated assembly on Vista x64. I guess I have to dig further into the documentation...grimskog62https://www.blogger.com/profile/14091538331436510283noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-29444477694686187032008-11-18T11:25:00.000+01:002008-11-18T11:25:00.000+01:00You are absolutely correct! I figured that out mom...You are absolutely correct! I figured that out moments after I posted my comment. Also I apologize for the previous comment which does not belong here. On another note, someday I will visited Italy, the birth place of my grandparents. Thank you for the Babel project.Frank Gennarohttps://www.blogger.com/profile/15773813713064333830noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-80464763891137655402008-11-18T00:46:00.000+01:002008-11-18T00:46:00.000+01:00It seem that you had not installed the right versi...It seem that you had not installed the right version of Phoenix framework.Alberto Ferrazzolihttps://www.blogger.com/profile/04139326250440208057noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-48360818820830247022008-11-17T21:30:00.000+01:002008-11-17T21:30:00.000+01:00I get the following error:Unhandled Exception: Sys...I get the following error:<BR/><BR/>Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'phx, Version=0.64.30627.0, Culture=neutral, PublicKeyToken=31bf<BR/>3856ad364e35' or one of its dependencies. The system cannot find the file specified.<BR/>File name: 'phx, Version=0.64.30627.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'<BR/> at ?.Main(String[] args)<BR/><BR/>WRN: Assembly binding logging is turned OFF.<BR/>To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.<BR/>Note: There is some performance penalty associated with assembly bind failure logging.<BR/>To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].Frank Gennarohttps://www.blogger.com/profile/15773813713064333830noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-9628201259367059332008-11-15T09:42:00.000+01:002008-11-15T09:42:00.000+01:00Yes you can.My email is alberto.ferrazzoli@gmail.c...Yes you can.<BR/>My email is alberto.ferrazzoli@gmail.comAlberto Ferrazzolihttps://www.blogger.com/profile/04139326250440208057noreply@blogger.comtag:blogger.com,1999:blog-7808773133895502659.post-21226531063383302852008-11-15T04:10:00.000+01:002008-11-15T04:10:00.000+01:00hi alberto, babel is cool!! can i contact u by ema...hi alberto, babel is cool!! can i contact u by email? i'm very instered in using phoenix framework. thxUnknownhttps://www.blogger.com/profile/17123724366347794632noreply@blogger.com