Download
1 / 4
40 likes | 154 Vues
When an assembly is added, it automatically receives a new name to ensure security when encrypted into a .lox file. The AssemblyLockbox.dll works by preventing .NET from identifying the original .dll by name. By default, the assembly retains its name but changes the extension from .dll to .lox. Users can opt to use GUID with the .lox extension, further obscuring the relationship between original dlls and lox files, thus enhancing protection against intruders. The renaming style can be easily reset to ensure compliance with current security selections.
E N D
When an assembly is added it automatically gets assigned a new name for when it is encrypted into a .lox file. This is done because for the AssemblyLockbox.dll to work .Net must not be able to find the original .dll it is looking for by name. So by default when you add an assembly it retains its’ current name but with the extension changed from .dll to .lox.
You can also change the default to GUID + LOX Extension. This will not only change the file extension, but will also change the file name itself to a GUID. The advantage of this is it makes it even more difficult for an intruder to figure out which lox files represent which dlls. The harder you make it on the intruder the safer you make your code.
At any time you can change the Naming Style, select an assembly from the list, and then click the [RESET] button. This resets the name of the assembly to what it should be based on the current selection under the Renaming Style menu.
