| View previous topic :: View next topic |
| Author |
Message |
Happs
Joined: 13 Jul 2011
Posts: 62
Location: Sydney, Australia
|
 Posted: Tue Jul 21, 2015 7:37 am Post subject: Initial review of NET Encryptor |
 |
|
I have download the trial version of .NET Encryptor and reviewing this product to determine whether it can be use to obfuscate our products.
I have some shared class libraries (*.dlls), installed in a common location and used by multiple products.
For example:
- Shared.dll
- Notifier.dll
These dlls need to be obfuscated.
From help...
| Quote: | You then add the encrypted assemblies as embedded resources to a small "bootstrap" application project (written in VB.NET or C#).
...
The "bootstrap" project builds the application executable that you distribute to your customers. |
Above example dlls will be combine to single executable as part of bootstrap process? I am trying to understand how the .NET Encryptor will work with current shared dlls design.
Thanks |
|
| Back to top |
|
 |
Infralution
Joined: 28 Feb 2005
Posts: 5027
|
| Posted: Tue Jul 21, 2015 7:57 am Post subject: |
|
|
You can add the DLLs as encrypted resources to the bootstrap (to form a single exe) - but you don't have to. Alternatively you can continue to put the shared files in a common location and use them as you currently are. Of course they won't be encrypted. If you want them encrypted then you would need to add them to the bootstrap of each product that uses them. This typically is not as bad (in terms of distribution size) as what it sounds because the files are compressed as well as encrypted and most installer packages will efficiently compress large parts of files that are the same as other parts in the same package.
_________________
Infralution Support |
|
| Back to top |
|
|
Happs
Joined: 13 Jul 2011
Posts: 62
Location: Sydney, Australia
|
| Posted: Tue Jul 21, 2015 8:46 am Post subject: |
|
|
| Quote: | | Alternatively you can continue to put the shared files in a common location and use them as you currently are. Of course they won't be encrypted. If you want them encrypted then you would need to add them to the bootstrap of each product that uses them. |
Our product and 3rd party applications also uses this shared dlls, we want these dlls to be obfuscated. Bootstrap technique is great with single executable file, but not sure how it will fit to our needs.
Thanks. |
|
| Back to top |
|
|
Infralution
Joined: 28 Feb 2005
Posts: 5027
|
| Posted: Tue Jul 21, 2015 12:38 pm Post subject: |
|
|
If you need to allow 3rd party components to access those DLLs then you can't use .NET Encryptor for them. I would recommend investigating obfuscators instead.
_________________
Infralution Support |
|
| Back to top |
|
|
Javier
Joined: 09 Oct 2009
Posts: 215
|
| Posted: Thu Sep 24, 2015 12:02 pm Post subject: |
|
|
| Quote: | | You can add the DLLs as encrypted resources to the bootstrap (to form a single exe) - but you don't have to. Alternatively you can continue to put the shared files in a common location and use them as you currently are. Of course they won't be encrypted. If you want them encrypted then you would need to add them to the bootstrap of each product that uses them. |
Following this thread, I also have some DLLs shared by several of our products. How do you add them as encrypted resources to the bootstrap? Of course not as a pre-build event, as the rest of the assemblies, right? Please clarify. |
|
| Back to top |
|
|
Infralution
Joined: 28 Feb 2005
Posts: 5027
|
| Posted: Thu Sep 24, 2015 10:16 pm Post subject: |
|
|
Yes you add a prebuild event just like for the exe to encrypt the DLL then you add the encrypted .enc file as an embedded resource to the Bootstrap.
_________________
Infralution Support |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
