Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

HTTPS not authenticated in many communication channels #49

Closed
blperez01 opened this issue Apr 22, 2019 · 1 comment
Closed

HTTPS not authenticated in many communication channels #49

blperez01 opened this issue Apr 22, 2019 · 1 comment
Labels
high a high priority issue

Comments

@blperez01
Copy link

The Kubernetes system allows users to set up a PKI, but in many cases fails to use authenticated TLS between components, which negates any benefit to using a PKI.

For example, the following connections do not use authenticated HTTPS:

  • Apiserver -> Kubelet
  • Apiserver -> Pods (this doesn't even use HTTPS)
  • Apiserver -> etcd

This failure to authenticate components within the system is extremely dangerous and should be changed to use authenticated HTTPS by default. The lack of authentication for etcd alone has led to major vulnerabilities in a wide variety of applications.

@blperez01 blperez01 added the high a high priority issue label Apr 22, 2019
@blperez01
Copy link
Author

TOA-K8S-034

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
high a high priority issue
Projects
None yet
Development

No branches or pull requests

1 participant