Strong name validation failed
ispysoftware opened this issue · 8 comments
Note: for support questions, please use stackoverflow or special repository on [github.com](in special repository github.com). This repository's issues are reserved for feature requests and bug reports.
-
**I'm submitting a ... **
- [ x] bug report
- feature request
- support request or question => Please do not submit support request or questions here, see note at the top of this template.
-
Do you want to request a feature or report a bug?
Kind of both -
What is the current behavior?
Some deployments of our app is crashing on startup. Probably something to do with an environment policy setting. It looks like the FFmpeg.AutoGen.dll file is badly signed - it needs to either be not signed or properly signed. I tried with 6.1.0.0 as well and had the same issue. -
*If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem:
run
sn -v FFmpeg.AutoGen.dll
against the nuget dll.
ffmpeg.autogen\6.1.0\lib\netstandard2.0>sn -v FFmpeg.AutoGen.dll
Microsoft (R) .NET Framework Strong Name Utility Version 4.0.30319.0
Copyright (c) Microsoft Corporation. All rights reserved.
Failed to verify assembly -- Strong name validation failed.
-
What is the expected behavior?
Either has no strong name or a valid one -
What is the motivation / use case for changing the behavior?
Getting errors from deployed applications
Error:Unhandled Exception: System.TypeInitializationException: The type initializer for 'CoreLogic.Statics' threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'FFmpeg.AutoGen, Version=6.0.0.2,
Culture=neutral, PublicKeyToken=9b7632533a381715' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityException: Strong name validation failed.
(Exception from HRESULT: 0x8013141A)
- Please tell us about your environment:
windows 64
- version:
all current
- Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
It's not really a duplicate as strong naming needs to be either working or removed. As it is it's breaking applications.
We're getting reports of this happening several times a day now - any ETA on a fix for it? I think all that needs to happen is remove the delay-sign check on the build.
If I drop it will it fix the problem? I'll update packages today without strong name.
I think it'll fix my problem - i built from source and removed the strong naming and it passes validation
Strange it started to occur in first place.
Okay 6.1.0.1 is on nuget.org
@ispysoftware can we close it? I think others can use 3rd party nuget packages to re sign to add strong name if needed.