This repository has been archived by the owner on Apr 7, 2020. It is now read-only.
Update golang version to 1.11.5 #3
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
**What this PR does / why we need it**: > We have just released Go 1.11.5 and Go 1.10.8 to address a recently reported security issue. We recommend that all users update to one of these releases (if you’re not sure which, choose Go 1.11.5). > > This DoS vulnerability in the crypto/elliptic implementations of the P-521 and P-384 elliptic curves may let an attacker craft inputs that consume excessive amounts of CPU. > > These inputs might be delivered via TLS handshakes, X.509 certificates, JWT tokens, ECDH shares or ECDSA signatures. In some cases, if an ECDH private key is reused more than once, the attack can also lead to key recovery. > > The issue is CVE-2019-6486 and Go issue golang/go#29903. See the Go issue for more details. K8S issue kubernetes/kubernetes#73238 **Which issue(s) this PR fixes**: n/a **Special notes for your reviewer**: **Release note**: <!-- Write your release note: 1. Enter your release note in the below block. 2. If no release note is required, just write "NONE" within the block. Format of block header: <category> <target_group> Possible values: - category: improvement|noteworthy|action - target_group: user|operator --> ```improvement operator NONE ``` /cc @ThormaehlenFred
|
Done with e9bb84b |
zanetworker
pushed a commit
that referenced
this pull request
Oct 31, 2019
from 0.2.3 to 0.2.4 ``` improvement user github.com/gardener/cert-management #3 @MartinWeindel bug fix: create secret copy if two managed ingress with same TLS hosts and same secret name are defined in two namespaces (issue #2) ```
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
K8S issue kubernetes/kubernetes#73238
Which issue(s) this PR fixes:
n/a
Special notes for your reviewer:
Release note:
/cc @ThormaehlenFred