Repository navigation
Enable DLL strong name verification #459
Description
The schema supports it, but I don't believe it's enabled yet.
This issue is twofold: we need to be able to verify assembly strong names (aka tokens) within PowerShell itself; we also need to generate signed DLLs.
Activity
vors commentedon Jan 27, 2016
Related: for FullCLR builds we need strongly named assemblies (to use GAC). We can use 'delayed signing' (doesn't require private key) and skip verification on test machine, but strong name is still required.
[-]Enable DLL key signing and verification[/-][+]Enable DLL strong name verification[/+]andyleejordan commentedon Jan 28, 2016
dotnet/cli#720 tracks the support of strong name signatures on Linux.
palladia commentedon Feb 2, 2016
Revisit Set-Authenticode cmdlet once we get this working.
andyleejordan commentedon Jun 16, 2016
Assemblies are now signed. Next step is to (carefully) revert the code that was changed when the assemblies weren't signed.