I just fixed all unit test cases in the latest change set.
↧
New Post: Source code doesn't match binary
↧
Updated Release: 2.0 RC 2 (Dec 29, 2013)
The changes since last commit on Google Code include,
- Merged all patches from RemObjects' fork.
- Unicode chars can be used as obfuscated names.
- Better dependency resolution.
- Various other small fixes (I could not yet verify every one, as there is no corresponding unit test cases).
- Merged patches from @AngryAnt (Emil Johansen)'s fork
- Korean chars can be used as obfuscated names.
- New tags are introduced (I could not yet verify every one, as there is no corresponding unit test cases).
- Add an option to automatic exclude of public types and members so that public API is kept.
- Add an option to automatic include all non-public types and members so that private API is obfuscated.
- Various bug fixes.
↧
↧
Released: 2.0 RC 3 (Dec 29, 2013)
The changes since last commit on Google Code include,
- Merged all patches from RemObjects' fork.
- Unicode chars can be used as obfuscated names.
- Better dependency resolution.
- Various other small fixes (I could not yet verify every one, as there is no corresponding unit test cases).
- Merged patches from @AngryAnt (Emil Johansen)'s fork
- Korean chars can be used as obfuscated names.
- New tags are introduced (I could not yet verify every one, as there is no corresponding unit test cases).
- Add an option to automatic exclude of public types and members so that public API is kept.
- Add an option to automatic include all non-public types and members so that private API is obfuscated.
- Various bug fixes.
↧
Updated Release: 2.0 RC 3 (Dec 29, 2013)
The changes since last commit on Google Code include,
- Merged all patches from RemObjects' fork.
- Unicode chars can be used as obfuscated names.
- Better dependency resolution.
- Various other small fixes (I could not yet verify every one, as there is no corresponding unit test cases).
- Merged patches from @AngryAnt (Emil Johansen)'s fork
- Korean chars can be used as obfuscated names.
- New tags are introduced (I could not yet verify every one, as there is no corresponding unit test cases).
- Add an option to automatic exclude of public types and members so that public API is kept.
- Add an option to automatic include all non-public types and members so that private API is obfuscated.
- Various bug fixes.
↧
New Post: Error caused by inexistant path
https://code.google.com/p/obfuscar/wiki/Configuration
This fork still follows the same rule, where it won't accept a .dll to be passed as argument.
This fork still follows the same rule, where it won't accept a .dll to be passed as argument.
↧
↧
New Post: Source code doesn't match binary
Great, thanks!
Eric
Eric
On 12/29/2013 1:33 AM, lextm wrote:
From: lextm
I just fixed all unit test cases in the latest change set.
↧
New Post: Source code doesn't match binary
Hi lextm,
I just downloaded RC3 source, rebuilt and two of the unit tests fail:
·ObfuscarTests.OutPathTests.CheckInvalidOutPath:
Exception was expected to be of type ApplicationException.
Expected: True
But was: False
·ObfuscarTests.SkipEventTests.CheckDropsEvents:
Some of the methods for the type are missing.
Expected: 8
But was: 4
I actually just fixed the first, by running the Nunit test as administrator. But I’m worried about the second test, since I don’t know if this is a bug in the unit test or in the obfuscation logic. What are your thoughts?
PS: I have not changed any code, other than: copy the ILSpy and cecil folders from my previous run – these were downloaded from the internet on Dec 27th, and fix up a missing package error in the solution. And I’m using VS 2013 instead of VS 2012…
↧
New Post: Source code doesn't match binary
Further to the previous email regarding the failure of the CheckDropsEvents test, the problem is that the type A.A works fine, but it has a nested type, called A.A/a, and the - expected 8, but was 4 - error occurred in the sub-type.
Here’s an ILSpy image of the test before obfuscation
And here’s the test DLL after obfuscation:
Does this make sense?
↧
Updated Wiki: History
The popularity of managed programming languages and their ease of decompilation introduce a common issue, "How can I protect my binaries?" 1
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
It started to gain popularity and soon the following releases were published,
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 20101213.
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes17.
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub18.
Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
*2
*3
*4
*5
*6
*7
*8
*9
*10
*11
*12
*13
*14
*15
*16
*17
*18
*19
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
Started by drcforbin
@drcforbin announced the first release of an open source obfuscator named obfuscar on May 3, 20072, while the initial checkin on Google Code occurred in late April3.It started to gain popularity and soon the following releases were published,
Resumed by Werner
Werner (@webbie) first contributed an important patch to the project on June 19, 20078. He seemed to be taking care of the project since April 2009, and made the following releases,He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 20101213.
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Various Forks After 2010
Carlo Kok from RemObjects has participated in the project since around Oct 8, 200914. RemObjects releases a commercial obfuscator called Oxfuscator in early 2010, which is based on Obfuscar15. However, RemObjects still keeps an open source version available16.@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes17.
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub18.
Inherited by Lex Li
Lex Li was working on his commercial project #SNMP Pro in Apr 2013, and came across Emil's fork. He soon created a new fork and started to merge various patches he could find from the Internet to this19.Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
References
*1*2
*3
*4
*5
*6
*7
*8
*9
*10
*11
*12
*13
*14
*15
*16
*17
*18
*19
↧
↧
Updated Wiki: Home
Project Description
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
![Obfuscation Example]( "Obfuscation Example")
The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
![Donate]( "Donate")
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
News
- Feb 2, 2014 Discussion board is going to be shut down. Please post questions to StackOverflow using obfuscar tag.
Documentation
Documentation section contains most information you need, and also a detailed history of this project all through the years.The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
Issues
If you have a patch to contribute, a feature to request, or a bug to report, please post to the Issue Tracker.Donation
If you find this project useful and want to donate to my efforts on this project, please use the following link,
↧
Updated Wiki: Home
Project Description
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
![Obfuscation Example]( "Obfuscation Example")
The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
![Donate]( "Donate")
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
News
- Feb 2, 2014 Discussion board is going to be shut down. Please post questions to StackOverflow using obfuscar tag.
Documentation
Documentation section contains most information you need, and also a detailed history of this project all through the years.The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
Issues
If you have a patch to contribute, a feature to request, or a bug to report, please post to the Issue Tracker.Donation
If you find this project useful and want to donate to my efforts on this project, please use the following link,↧
Updated Wiki: History
The popularity of managed programming languages and their ease of decompilation introduce a common issue, "How can I protect my binaries?" (*1)
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
It started to gain popularity and soon the following releases were published,
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(12)(13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(*17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(*18).
Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
*2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
*3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
*4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
*5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
*6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
*7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
*8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
*9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
*10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
*11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
*12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
*13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
*14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
*15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
*16 http://code.remobjects.com/p/obfuscar
*17 https://bitbucket.org/darktable/obfuscar/wiki/Home
*18 https://github.com/AngryAnt/obfuscar
*19 https://github.com/lextm/obfuscar
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
Started by drcforbin
@drcforbin announced the first release of an open source obfuscator named obfuscar on May 3, 2007(2), while the initial checkin on Google Code occurred in late April(3).It started to gain popularity and soon the following releases were published,
- 1.0.1 on May 10, 2007 (*4)
- 1.1.0 on May 18, 2007 (*5)
- 1.3.0 on July 12, 2007 (*6)
- 1.3.1 on Sept 12, 2007 (*7)
Resumed by Werner
Werner (@webbie) first contributed an important patch to the project on June 19, 2007(*8). He seemed to be taking care of the project since April 2009, and made the following releases,- 1.4.0 on April 24, 2009 (*9)
- 1.5.0 on Nov 6, 2009 (*10)
- 1.5.2 on Nov 20, 2009 (*11)
- 1.5.4 on ??
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(12)(13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Various Forks After 2010
Carlo Kok from RemObjects has participated in the project since around Oct 8, 2009(14). RemObjects releases a commercial obfuscator called Oxfuscator in early 2010, which is based on Obfuscar(15). However, RemObjects still keeps an open source version available(*16).@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(*17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(*18).
Inherited by Lex Li
Lex Li was working on his commercial project #SNMP Pro in Apr 2013, and came across Emil's fork. He soon created a new fork and started to merge various patches he could find from the Internet to this(*19).Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
References
*1 http://en.wikipedia.org/wiki/Obfuscation_(software)*2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
*3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
*4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
*5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
*6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
*7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
*8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
*9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
*10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
*11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
*12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
*13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
*14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
*15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
*16 http://code.remobjects.com/p/obfuscar
*17 https://bitbucket.org/darktable/obfuscar/wiki/Home
*18 https://github.com/AngryAnt/obfuscar
*19 https://github.com/lextm/obfuscar
↧
Updated Wiki: History
The popularity of managed programming languages and their ease of decompilation introduce a common issue, "How can I protect my binaries?" (+1)
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
It started to gain popularity and soon the following releases were published,
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(12)(13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(+17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(+18).
Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
+2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
+3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
+4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
+5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
+6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
+7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
+8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
+9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
+10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
+11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
+12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
+13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
+14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
+15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
+16 http://code.remobjects.com/p/obfuscar
+17 https://bitbucket.org/darktable/obfuscar/wiki/Home
+18 https://github.com/AngryAnt/obfuscar
+19 https://github.com/lextm/obfuscar
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
Started by drcforbin
@drcforbin announced the first release of an open source obfuscator named obfuscar on May 3, 2007(2), while the initial checkin on Google Code occurred in late April(3).It started to gain popularity and soon the following releases were published,
- 1.0.1 on May 10, 2007 (+4)
- 1.1.0 on May 18, 2007 (+5)
- 1.3.0 on July 12, 2007 (+6)
- 1.3.1 on Sept 12, 2007 (+7)
Resumed by Werner
Werner (@webbie) first contributed an important patch to the project on June 19, 2007(+8). He seemed to be taking care of the project since April 2009, and made the following releases,- 1.4.0 on April 24, 2009 (+9)
- 1.5.0 on Nov 6, 2009 (+10)
- 1.5.2 on Nov 20, 2009 (+11)
- 1.5.4 on ??
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(12)(13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Various Forks After 2010
Carlo Kok from RemObjects has participated in the project since around Oct 8, 2009(14). RemObjects releases a commercial obfuscator called Oxfuscator in early 2010, which is based on Obfuscar(15). However, RemObjects still keeps an open source version available(+16).@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(+17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(+18).
Inherited by Lex Li
Lex Li was working on his commercial project #SNMP Pro in Apr 2013, and came across Emil's fork. He soon created a new fork and started to merge various patches he could find from the Internet to this(+19).Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
References
+1 http://en.wikipedia.org/wiki/Obfuscation_(software)+2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
+3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
+4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
+5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
+6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
+7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
+8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
+9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
+10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
+11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
+12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
+13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
+14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
+15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
+16 http://code.remobjects.com/p/obfuscar
+17 https://bitbucket.org/darktable/obfuscar/wiki/Home
+18 https://github.com/AngryAnt/obfuscar
+19 https://github.com/lextm/obfuscar
↧
↧
Updated Wiki: History
The popularity of managed programming languages and their ease of decompilation introduce a common issue, "How can I protect my binaries?" (&1)
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
It started to gain popularity and soon the following releases were published,
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(&12)(&13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(&17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(&18).
Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
&2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
&3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
&4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
&5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
&6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
&7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
&8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
&9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
&10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
&11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
&12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
&13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
&14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
&15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
&16 http://code.remobjects.com/p/obfuscar
&17 https://bitbucket.org/darktable/obfuscar/wiki/Home
&18 https://github.com/AngryAnt/obfuscar
&19 https://github.com/lextm/obfuscar
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
Started by drcforbin
@drcforbin announced the first release of an open source obfuscator named obfuscar on May 3, 2007(&2), while the initial checkin on Google Code occurred in late April(&3).It started to gain popularity and soon the following releases were published,
- 1.0.1 on May 10, 2007 (&4)
- 1.1.0 on May 18, 2007 (&5)
- 1.3.0 on July 12, 2007 (&6)
- 1.3.1 on Sept 12, 2007 (&7)
Resumed by Werner
Werner (@webbie) first contributed an important patch to the project on June 19, 2007(&8). He seemed to be taking care of the project since April 2009, and made the following releases,- 1.4.0 on April 24, 2009 (&9)
- 1.5.0 on Nov 6, 2009 (&10)
- 1.5.2 on Nov 20, 2009 (&11)
- 1.5.4 on ??
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(&12)(&13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Various Forks After 2010
Carlo Kok from RemObjects has participated in the project since around Oct 8, 2009(&14). RemObjects releases a commercial obfuscator called Oxfuscator in early 2010, which is based on Obfuscar(&15). However, RemObjects still keeps an open source version available(&16).@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(&17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(&18).
Inherited by Lex Li
Lex Li was working on his commercial project #SNMP Pro in Apr 2013, and came across Emil's fork. He soon created a new fork and started to merge various patches he could find from the Internet to this(&19).Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
References
&1 http://en.wikipedia.org/wiki/Obfuscation_(software)&2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
&3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
&4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
&5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
&6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
&7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
&8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
&9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
&10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
&11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
&12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
&13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
&14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
&15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
&16 http://code.remobjects.com/p/obfuscar
&17 https://bitbucket.org/darktable/obfuscar/wiki/Home
&18 https://github.com/AngryAnt/obfuscar
&19 https://github.com/lextm/obfuscar
↧
Updated Wiki: Contributors
Contributors to this project include,
- Ryan Williams (drcforbin@gmail.com)
- Werner (webbie@cablemail.de)
- Przemysław Rajpold (@rejpon in Google Group)
- Carlo Kok (@carlokok on Twitter/GitHub)
- Calvin Rien (@darktable on Twitter/GitHub)
- Emil Johansen (@AngryAnt on Twitter/GitHub)
- Lex Li (@lextm on Twitter/GitHub)
↧
Updated Wiki: History
The popularity of managed programming languages and their ease of decompilation introduce a common issue, "How can I protect my binaries?" (&1)
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
It started to gain popularity and soon the following releases were published,
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(&12)(&13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(&17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(&18).
Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
&2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
&3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
&4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
&5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
&6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
&7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
&8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
&9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
&10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
&11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
&12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
&13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
&14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
&15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
&16 http://code.remobjects.com/p/obfuscar
&17 https://bitbucket.org/darktable/obfuscar/wiki/Home
&18 https://github.com/AngryAnt/obfuscar
&19 https://github.com/lextm/obfuscar
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
Started by Ryan
Ryan Williams (@drcforbin) announced the first release of an open source obfuscator named obfuscar on May 3, 2007(&2), while the initial checkin on Google Code occurred in late April(&3).It started to gain popularity and soon the following releases were published,
- 1.0.1 on May 10, 2007 (&4)
- 1.1.0 on May 18, 2007 (&5)
- 1.3.0 on July 12, 2007 (&6)
- 1.3.1 on Sept 12, 2007 (&7)
Resumed by Werner
Werner (@webbie) first contributed an important patch to the project on June 19, 2007(&8). He seemed to be taking care of the project since April 2009, and made the following releases,- 1.4.0 on April 24, 2009 (&9)
- 1.5.0 on Nov 6, 2009 (&10)
- 1.5.2 on Nov 20, 2009 (&11)
- 1.5.4 on ??
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(&12)(&13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Various Forks After 2010
Carlo Kok from RemObjects has participated in the project since around Oct 8, 2009(&14). RemObjects releases a commercial obfuscator called Oxfuscator in early 2010, which is based on Obfuscar(&15). However, RemObjects still keeps an open source version available(&16).@darktable created a fork on BitBucket on Oct 24, 2012 and included his changes(&17).
Emil Johansen@AngryAnt forked @darktable's fork, and hosted it on GitHub(&18).
Inherited by Lex Li
Lex Li was working on his commercial project #SNMP Pro in Apr 2013, and came across Emil's fork. He soon created a new fork and started to merge various patches he could find from the Internet to this(&19).Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
References
&1 http://en.wikipedia.org/wiki/Obfuscation_(software)&2 https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
&3 https://code.google.com/p/obfuscar/source/list?num=25&start=10
&4 https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
&5 https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
&6 https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
&7 https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
&8 https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
&9 https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
&10 https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
&11 https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
&12 https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
&13 https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
&14 https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
&15 http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
&16 http://code.remobjects.com/p/obfuscar
&17 https://bitbucket.org/darktable/obfuscar/wiki/Home
&18 https://github.com/AngryAnt/obfuscar
&19 https://github.com/lextm/obfuscar
↧
Updated Wiki: History
The popularity of managed programming languages and their ease of decompilation introduce a common issue, "How can I protect my binaries?" (1)
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
It started to gain popularity and soon the following releases were published,
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(12)(13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Calvin Rien (@darktable) created a fork on BitBucket on Oct 24, 2012 and included his changes(17).
Emil Johansen (@AngryAnt) forked Calvin's fork, and hosted it on GitHub(18).
Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
2https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
3https://code.google.com/p/obfuscar/source/list?num=25&start=10
4https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
5https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
6https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
7https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
8https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
9https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
10https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
11https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
12https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
13https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
14https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
15http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
16http://code.remobjects.com/p/obfuscar
17https://bitbucket.org/darktable/obfuscar/wiki/Home
18https://github.com/AngryAnt/obfuscar
19https://github.com/lextm/obfuscar
Obfuscation has been invented to add some protection. But most of obfuscator products are commercial and really expensive.
Started by Ryan
Ryan Williams (@drcforbin) announced the first release of an open source obfuscator named obfuscar on May 3, 2007(2), while the initial checkin on Google Code occurred in late April(3).It started to gain popularity and soon the following releases were published,
- 1.0.1 on May 10, 2007 (4)
- 1.1.0 on May 18, 2007 (5)
- 1.3.0 on July 12, 2007 (6)
- 1.3.1 on Sept 12, 2007 (7)
Resumed by Werner
Werner (@webbie) first contributed an important patch to the project on June 19, 2007(8). He seemed to be taking care of the project since April 2009, and made the following releases,- 1.4.0 on April 24, 2009 (9)
- 1.5.0 on Nov 6, 2009 (10)
- 1.5.2 on Nov 20, 2009 (11)
- 1.5.4 on ??
He was trying to upgrade the project to work with latest Cecil at that moment under 2.0 branch, but that work was not finished.
Przemysław Rajpold(@rejpon) contributed two patches on July 29, 2010(12)(13).
@mikael.hansen.idevio also contributed one patch on May 26, 2009.
Various Forks After 2010
Carlo Kok from RemObjects has participated in the project since around Oct 8, 2009(14). RemObjects releases a commercial obfuscator called Oxfuscator in early 2010, which is based on Obfuscar(15). However, RemObjects still keeps an open source version available(16).Calvin Rien (@darktable) created a fork on BitBucket on Oct 24, 2012 and included his changes(17).
Emil Johansen (@AngryAnt) forked Calvin's fork, and hosted it on GitHub(18).
Inherited by Lex Li
Lex Li was working on his commercial project #SNMP Pro in Apr 2013, and came across Emil's fork. He soon created a new fork and started to merge various patches he could find from the Internet to this(19).Gradually Lex gained knowledge about Cecil and Obfuscar and started to heavily change the obfuscation process so as to better serve his own needs.
Carlo from RemObjects also contributes to this new fork, since Jan 2014. The collaboration aims to keep the two forks in sync in all possible ways, though due to the varied needs and design goals of two parties the forks still present significant differences.
The project homepage is now switched to CodePlex, and the latest release is 2.0 RC*.
References
1http://en.wikipedia.org/wiki/Obfuscation_(software)2https://groups.google.com/forum/#!topic/obfuscar/2QL0ObML40o
3https://code.google.com/p/obfuscar/source/list?num=25&start=10
4https://groups.google.com/forum/#!topic/obfuscar/ctAN-hUaIB8
5https://groups.google.com/forum/#!topic/obfuscar/SrPG1BDZgrM
6https://groups.google.com/forum/#!topic/obfuscar/aH6I8v9Q_uI
7https://groups.google.com/forum/#!topic/obfuscar/554b9QOYsx4
8https://groups.google.com/forum/#!topic/obfuscar/__vjzvP9m1o
9https://groups.google.com/forum/#!topic/obfuscar/TLyU9ybfsKg
10https://groups.google.com/forum/#!topic/obfuscar/o61if_nFeog
11https://groups.google.com/forum/#!topic/obfuscar/vsVCfSMYk3U
12https://groups.google.com/forum/#!topic/obfuscar/PYs0KNps8mk
13https://groups.google.com/forum/#!topic/obfuscar/2LY3WoU72IQ
14https://groups.google.com/forum/#!topic/obfuscar/Fy0wFMVpA9Y
15http://blogs.remobjects.com/blogs/mh/2010/01/12/p303
16http://code.remobjects.com/p/obfuscar
17https://bitbucket.org/darktable/obfuscar/wiki/Home
18https://github.com/AngryAnt/obfuscar
19https://github.com/lextm/obfuscar
↧
↧
Updated Wiki: Home
The project logo comes from Legendora Icon by Teekatas Suwannakrua.
Project Description
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
![Obfuscation Example]( "Obfuscation Example")
The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
![Donate]( "Donate")
Project Description
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
News
- Feb 2, 2014 Discussion board is going to be shut down. Please post questions to StackOverflow using obfuscar tag.
Get Started
Documentation section contains most information you need, and also a detailed history of this project all through the years.The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
Issues
If you have a patch to contribute, a feature to request, or a bug to report, please post to the Issue Tracker.Donation
If you find this project useful and want to donate to my efforts on this project, please use the following link,↧
Updated Wiki: Home
The project logo comes from Legendora Icon by Teekatas Suwannakrua.
Project Description
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
![Obfuscation Example]( "Obfuscation Example")
The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
![Donate]( "Donate")
Project Description
Obfuscar is an open source .NET obfuscator released under MIT license. It provides basic obfuscation features that help secure secrets in a .NET assembly.
News
- Feb 2, 2014 Discussion board is going to be shut down. Please post questions to StackOverflow using obfuscar tag.
Get Started
Documentation section contains most information you need, and also a detailed history of this project all through the years.The source repository for this project is at GitHub.
This tool has been heavily in Lex Li's personal project (#SNMP Pro).
Issues
If you have a patch to contribute, a feature to request, or a bug to report, please post to the Issue Tracker.Donation
If you find this project useful and want to donate to my efforts on this project, please use the following link,↧
Updated Wiki: Basic Example
There is a basic example project included in the code base. To build and obfuscate the BasicExample, get the source from Git, navigate to the BasicExample path, and run "msbuild release.proj".
![example.png]( "example.png")
The example consists of a solution that includes and executable and a dll. The release.proj script builds the solution, copies the output to a temporary input path. The files are then obfuscated into a temporary output path. After obfuscation, the files are copied along with the map file to their final output path.
The reason for this indirection is safety. The release process should be as follows:
In the event that the obfuscator fails, an in-place obfuscation could allow files to enter the release without being obfuscated. Having the obfuscator explicitly save to a different location and using files from that location means that failure results in missing files.
The example consists of a solution that includes and executable and a dll. The release.proj script builds the solution, copies the output to a temporary input path. The files are then obfuscated into a temporary output path. After obfuscation, the files are copied along with the map file to their final output path.
The reason for this indirection is safety. The release process should be as follows:
- Files that will not be obfuscated should be copied directly to the final output path.
- Files to be obfuscated should be copied to a temporary location (Obfuscator_Input, in the example), along with their dependencies.
- Files to be obfuscated should be obfuscated from the first location (Obfuscator_Input) to a different location (Obfuscator_Output, in the example).
- Obfuscated files should be copied from the obfuscation output location (Obfuscator_Output) to the final output path.
- Package files in final output path (beyond the scope of this document ;)
In the event that the obfuscator fails, an in-place obfuscation could allow files to enter the release without being obfuscated. Having the obfuscator explicitly save to a different location and using files from that location means that failure results in missing files.
↧