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

cipher-suites not honored from configuration file #11587

Closed
petersutty opened this issue Feb 4, 2020 · 1 comment
Closed

cipher-suites not honored from configuration file #11587

petersutty opened this issue Feb 4, 2020 · 1 comment
Labels

Comments

@petersutty
Copy link

I am trying to configure ciphers from etcd configuration file, but its not accepted by etcd

config file:
name: infra0
initial-advertise-peer-urls: https://infra0.syspay.com:2380
listen-peer-urls: https://10.0.1.10:2380
listen-client-urls: http://127.0.0.1:2379
advertise-client-urls: http://127.0.0.1:2379
initial-cluster-token: etcd-cluster-1
initial-cluster: infra0=https://10.0.1.10:2380,infra1=https://10.0.1.11:2380,infra2=https://10.0.1.12:2380
initial-cluster-state: new
peer-transport-security:
client-cert-auth: true
trusted-ca-file: /opt/bitnami/etcd/conf/ca_chained.crt
cert-file: /opt/bitnami/etcd/conf/server.crt
key-file: /opt/bitnami/etcd/conf/server.key
cipher-suites: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
logger: zap

log:
infra0 | {"level":"info","ts":"2020-02-04T10:32:43.650Z","caller":"embed/etcd.go:465","msg":"starting with peer TLS","tls-info":"cert = /opt/bitnami/etcd/conf/server.crt, key = /opt/bitnami/etcd/conf/server.key, trusted-ca = /opt/bitnami/etcd/conf/ca_chained.crt, client-cert-auth = true, crl-file = ","cipher-suites":[]}

etcd version:
etcd Version: 3.4.3
Git SHA: 3cf2f69
Go Version: go1.12.12
Go OS/Arch: linux/amd64

another docs issue:
if you go https://etcd.io/docs/v3.4.0/op-guide/configuration/ and click on "sample configuration file" - https://etcd.io/docs/v3.4.0/etcd.conf.yml.sample is missing

@stale
Copy link

stale bot commented May 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant