Skip to content

Use mainstream and strongly-named versions of BouncyCastle, YamlDotNet #77

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Jan 10, 2018
Merged

Use mainstream and strongly-named versions of BouncyCastle, YamlDotNet #77

merged 2 commits into from
Jan 10, 2018

Conversation

qmfrederik
Copy link
Contributor

  • Use Portable.BouncyCastle instead of BouncyCastle.NetCore. The portable version has > 1.4M downloads on NuGet and tracks upstream BouncyCastle
  • Use YamlDotNet.Signed instead of YamlDotNet.NetCore, YamlDotNet.Signed is the package maintained by the YamlDotNet author.

Split off from #76

@brendandburns
Copy link
Contributor

LGTM, thanks.

@brendandburns brendandburns merged commit edc0cfb into kubernetes-client:master Jan 10, 2018
JonJam pushed a commit to JonJam/csharp that referenced this pull request Sep 8, 2018
@qmfrederik @JonJam
Use mainstream and strongly-named versions of BouncyCastle, YamlDotNet (
cdfeda1 
kubernetes-client#77)

* Use strongly-signed NuGet packages

* Use the Signed version of Fractions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@qmfrederik @brendandburns