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

The Assembly is not stongly signed #14

Open
tommylindgren opened this issue Jan 28, 2019 · 3 comments
Open

The Assembly is not stongly signed #14

tommylindgren opened this issue Jan 28, 2019 · 3 comments

Comments

@tommylindgren
Copy link

tommylindgren commented Jan 28, 2019

Please make the assembly stongly signed. This is needed to be able to add the assembly to the Global Assembly Cache.

This could be done by creating a signing key using sn.exe and adding the key to the base of the project and adding the following to the .csproj file:

<PropertyGroup> <SignAssembly>true</SignAssembly> </PropertyGroup> <PropertyGroup> <AssemblyOriginatorKeyFile>ChoPGP.snk</AssemblyOriginatorKeyFile> </PropertyGroup> <ItemGroup> <None Include="ChoPGP.snk" /> <None Include="packages.config" /> </ItemGroup>

@Cinchoo
Copy link
Owner

Cinchoo commented Feb 2, 2019

Can't, the dependency 'BouncyCastle.Crypto.dll' is not strongly signed.

@PugachA
Copy link

PugachA commented Dec 1, 2020

Please, add a strong name, because BouncyCastle.Crypto.dll has a strong name.

>sn -v BouncyCastle.Crypto.dll

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Assembly 'BouncyCastle.Crypto.dll' is valid

@GBeans
Copy link

GBeans commented Sep 1, 2021

Excellent wrapper! I would also ask that you please strongly sign the assembly.

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

4 participants