Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MediaDevices.dll does not represent a strongly named assembly #20

Closed
pallavi-garg opened this issue Sep 2, 2019 · 7 comments
Closed

Comments

@pallavi-garg
Copy link

Hi Ralf,

I need to have MediaDevices package to be a strongly named assembly. Is there any signed version available? If not, how do you suggest to sign it?

Thanks & Regards,
Pallavi Garg

@pallavi-garg
Copy link
Author

Hi Ralf,

Is there any update on this?

Regards
Pallavi

1 similar comment
@pallavi-garg
Copy link
Author

Hi Ralf,

Is there any update on this?

Regards
Pallavi

@Bassman2
Copy link
Owner

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

@chcg
Copy link
Contributor

chcg commented Sep 17, 2019

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.

@pallavi-garg
Copy link
Author

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?

@Bassman2
Copy link
Owner

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

@pallavi-garg
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants