Version 8.4.11 signing
I got an update this morning and am running into issues with my firm's anti-malware scans because the DLLs installed in /AppData/Local/LINQPad/8.4.11 and it's subdirectories and not signed the way previous versions were. Is this expected?
Comments
-
Most of the assemblies in that folder are not signed (and never were). Signed files include the LINQPad launchers and LINQPad.Runtime.dll (the container from which the assemblies in %localappdata% are extracted).
I've not considered signing every DLL, mainly because it would slow the build process to a crawl. Code signing is a real pain nowadays. Everything must be signed through a special USB dongle, and then time-stamped on a server provided by the code-signing cartel. These servers apply punitive rate limits.
-
Thanks, and understood. The specific DLL that's tripping me up is LINQPAD.DRIVERS.LINQTOSQL.DLL, which is signed in the 8.3.7 folder I have, but not in 8.4.11. Any chance that one could be?
Or, conversely I have a "safe haven" folder that is excluded from our anti-malware scans. Is it possible to point those assemblies to be extracted there rather than %localappdata%?
-
Yes - you can do this by setting the LINQPAD_LOCALAPPDATA environment variable. You can also set LINQPAD_TEMP (see Edit | Preferences > Folders).
-
I'll also get that assembly signed in the 8.5.2 build, early next week.
-
8.5.2 is available early:
https://www.linqpad.net/linqpad8.aspx#beta -
That is great, thank you so much.
