kubernetes/cmd/kubelet/app
k8s-merge-robot 0fc573296d Merge pull request #26169 from victorgp/master
Automatic merge from submit-queue

Setting TLS1.2 minimum because TLS1.0 and TLS1.1 are vulnerable

TLS1.0 is known as vulnerable since it can be downgraded to SSL
https://blog.varonis.com/ssl-and-tls-1-0-no-longer-acceptable-for-pci-compliance/

TLS1.1 can be vulnerable if cipher RC4-SHA is used, and in Kubernetes it is, you can check it with
`
openssl s_client -cipher RC4-SHA -connect apiserver.k8s.example.com:443
`

https://www.globalsign.com/en/blog/poodle-vulnerability-expands-beyond-sslv3-to-tls/

Test suites like Qualys are reporting this Kubernetes issue as a level 3 vulnerability, they recommend to upgrade to TLS1.2 that is not affected, quoting Qualys:

`
RC4 should not be used where possible. One reason that RC4 was still being used was BEAST and Lucky13 attacks against CBC mode ciphers in
SSL and
TLS. However, TLSv 1.2 or later address these issues.
`
2016-05-29 13:24:46 -07:00
..
options Merge pull request #25972 from luxas/remove_arch_constants 2016-05-28 04:48:59 -07:00
plugins.go Adding vSphere Volume support for vSphere Cloud Provider 2016-05-21 11:00:14 -07:00
server_linux.go kubelet: Add --exit-on-lock-contention flag 2016-05-18 16:21:47 -07:00
server_test.go kubelet: Add --exit-on-lock-contention flag 2016-05-18 16:21:47 -07:00
server_unsupported.go kubelet: Add --exit-on-lock-contention flag 2016-05-18 16:21:47 -07:00
server.go Merge pull request #26169 from victorgp/master 2016-05-29 13:24:46 -07:00