11

Is there a .NET obfuscation tool present for Linux? Or is there a class which can provide me a functionality of writing a obfuscation tool for byte code?

abatishchev
  • 98,240
  • 88
  • 296
  • 433
Pushkar
  • 1,300
  • 2
  • 15
  • 20
  • Just an aside: I'm not usually convinced how much obfuscation buys you.. the cheap ones can be broken; even the expensive ones can be reversed if you are determined enough. If you make the dll available (in any technology), consider it breakable. – Marc Gravell Apr 08 '09 at 11:00

4 Answers4

4

Try this tool, its free : http://www.foss.kharkov.ua/g1/projects/eazfuscator/dotnet/Default.aspx#downloads and it does what commercial products do.

JL.
  • 78,954
  • 126
  • 311
  • 459
1

You might try Spices.Obfuscator. It advertises that it supports Mono but that may be that it generates assemblies which are compatible with Mono (assuming they were in the first place) rather than runs on Mono. Since they indicate they obfuscate themselves it would suggest that their command line app stands a good chance of working (I suggest you try downloading their evaluation package)

I concur with Marc Gravell's comment on their utility, especially once you start using c# 3.0 features which make the resulting unobfuscated decompiled code pretty ugly anyway. If the code is local it can be broken, at best you remove meaningful names (at the cost of a permanent hassle for reflective scenarios).

ShuggyCoUk
  • 36,004
  • 6
  • 77
  • 101
1

Do you want an obfuscator that executes under Mono or one that outputs assemblies that will run under Mono?

If you want one that runs under Mono I don't know of any whose GUI runs under Mono but I do know that we have tested the Dotfuscator command line interface internally under Mono and it works. This is not (yet) an officially supported or extensively tested solution so your mileage may vary.

Dotfuscator accepts any standard MSIL assembly and we only emit 100% PEverifiable assemblies out so as long as your source assembly is Mono compatible the Dotfuscator output should also be Mono compatible. This can be verified using the Mono Migration Analyzer on both your source assembly and the Dotfuscator output.

Disclaimer: I do work for PreEmptive Solutions, the makers of Dotfuscator.

Joe Kuemerle
  • 6,338
  • 1
  • 23
  • 18
  • Dotfuscator community edition does not obfuscate strings. – JL. Sep 28 '09 at 08:09
  • That is correct, but Dotfuscator Community Edition also does not have a command line interface and has not been tested under Mono. – Joe Kuemerle Sep 28 '09 at 15:39
  • Please keep this feature, it's great. That's what separates you from Redgate. Can you write a bit how actviation is handled? Do you have activation? It seems likely that the excellent Dotfuscator codebase would run on Linux/Mono perfectly (who needs GUI?), but that your Dash-O stuff and your own activation stuff would not work on Linux. So please please make sure that Dotfuscator runs on Linux! – Christian Mar 24 '11 at 11:38
  • It just does not work. What he writes must be plainy wrong. Dotfuscator calls ildasm and ilasm and these tools are not available easily with mono. If you tweak the paths, then it cannot parse the result from the mono tools. – Christian Mar 22 '12 at 00:20
0

Crypto Obfuscator supports Mono apps. It itself does not run on Mono, but all assemblies obfuscated with it will run on Mono as long as the original assemblies run too.

DISCLAIMER: I work for LogicNP Software, the developer of Crypto Obfuscator.

logicnp
  • 5,796
  • 1
  • 28
  • 32