Since almost all anti-tamper protections prevent any further post-processing with any tools, it would be good to have some ability to authenticode sign assemblies as part of the initial processing within SA.  I realise this is a bit chicken and the egg scenario, but at the moment I can't enable all of the particularly strong protections as I then cannot sign the assembly.
      
      
      
      
      Comments
1 comment
- 
                
                   I've been able to authenticode sign the assemblies post obfuscation as part of the build process. Using msbuild, my csproj looks like: I've been able to authenticode sign the assemblies post obfuscation as part of the build process. Using msbuild, my csproj looks like:<Target Name="AfterCompile"> <Exec Command="$(SmartAssemblyLocation) /build $(SmartAssemblyProjectLocation)" /> <Copy SourceFiles="$(OutputPath)$(TargetFileName)" DestinationFiles="$(IntermediateOutputPath)$(TargetFileName)" /> <Exec Command=""signtool.exe" sign /t http://timestamp.server.com /i CertName "$(IntermediateOutputPath)$(TargetFileName)"" /> </Target>
Add comment
Please sign in to leave a comment.