MediaDevices.dll does not represent a strongly named assembly about mediadevices HOT 7 CLOSED

You can find the strong name file in the Signed folder.

from mediadevices.

Hi Ralf,

Is there any update on this?

Regards
Pallavi

from mediadevices.

Hi Ralf,

Is there any update on this?

Regards
Pallavi

from mediadevices.

Hello Pallavi,

what kind of signing do you mean?

On the one hand, you can sign the assembly with a self-made certificate (sn -k ) that does not give you high security and on the other hand you can buy a code signing certificate. This costs a few hundred dollars a year that I do not want to pay.

Why do not you take the DLL and sign it yourself?
al /out: /keyfile:

Ralf

from mediadevices.

See https://docs.microsoft.com/en-us/dotnet/standard/assembly/enhanced-strong-naming

However, strong name keys don’t contain any reliable information about the publisher, nor do they contain a certificate hierarchy. A strong name signature does not guarantee the trustworthiness of the person who signed the assembly or indicate whether that person was a legitimate owner of the key; it indicates only that the owner of the key signed the assembly. Therefore, we do not recommend using a strong name signature as a security validator for trusting third-party code. Microsoft Authenticode is the recommended way to authenticate code.

from mediadevices.

Thanks Ralf for your reply!
We need signing not for security but identity so no monitory cost is involved if you do it.
Please refer to this: https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming
Can you please make a signed version available?

from mediadevices.

Thank you so much Ralf. I am closing this issue.

from mediadevices.