Key Transparency VS etcd

However, a MITM controlling the signaling server could manipulate any attempt to communicate the fingerprint between the endpoints. Hence why certificate verification should be out-of-band (with regards to the signaling server). The most common solution I've seen is that the call participants can just read the fingerprints to each other and ensure they match. But there are other solutions including using a trusted third party, or even key transparency... because blockchain.

Archived. Not sure when. :( I'm not sure what if anything is a decent replacement/substitute.

In the README examples I see text about what I think is Certificate Transparency. That was definitely the first thing this made me think of. There's also a lot of talk in the project about CONIKS[1], & associate research papers are about 'bringing key transparency to end users'.

The scenarios[2] are interesting, but I'm not sure fully how this project helps. They explicitly call out Upspin for encrypted storage, which was linked recently[3].

It appears to make heavy use of the Trillian cryptographically verifiable data store[4].

[1] https://www.schneier.com/blog/archives/2016/04/coniks.html

[2] https://github.com/google/keytransparency/blob/master/docs/s...

[3] https://news.ycombinator.com/item?id=31520559

[4] https://github.com/google/trillian

Key Transparency is an example of such a system, built on a highly scalable backend system (Trillian, which powers Certificate Transparency), but it's been under development for several years without a production deployment.

sudo dnf -y install curl wget vim ETCD_RELEASE=$(curl -s https://api.github.com/repos/etcd-io/etcd/releases/latest|grep tag_name | cut -d '"' -f 4) echo $ETCD_RELEASE wget https://github.com/etcd-io/etcd/releases/download/${ETCD_RELEASE}/etcd-${ETCD_RELEASE}-linux-amd64.tar.gz tar xvf etcd-${ETCD_RELEASE}-linux-amd64.tar.gz cd etcd-${ETCD_RELEASE}-linux-amd64 sudo mv etcd* /usr/local/bin ls /usr/local/bin /usr/local/bin/etcd --version

Reading the standard library will give you ideas/insight about various Go idiomatic patterns/approaches, and you can see a full website/API implementation in the pkg.go.dev repository (https://github.com/golang/pkgsite). Projects like https://github.com/etcd-io/etcd may be interesting too.

Failure Detection and Recovery It’s not enough to have backup systems. It’s also crucial to detect failures quickly. Modern systems employ monitoring tools and rely on distributed coordination systems such as Zookeeper or etcd to identify faults in real-time: once detected, recovery mechanisms are triggered to restore the service.

Service Discovery: Microservices need to discover and communicate with each other dynamically. Service discovery tools like etcd, Consul, or Kubernetes built-in service discovery mechanisms help locate and connect to microservices running on different nodes within the infrastructure.

APISIX uses etcd to store and synchronize configurations.

etcd is an excellent key-value distributed database used internally by Kubernetes and managed by the CNCF. It's a great option, and that's the reason why Apache APISIX uses it too. Yet, it's not devoid of issues.

Someone on HN (https://news.ycombinator.com/item?id=36682595) suggested etcd (https://etcd.io)

In traditional mode, APISIX stores its configuration in etcd. APISIX offers a rich API to access and update the configuration, the Admin API. In standalone mode, the configuration is just plain YAML. It's the approach for GitOps practitioners: you'd store your configuration in a Git repo, watch it via your favorite tool (e.g., Argo CD or Tekton), and the latter would propagate the changes to APISIX nodes upon changes. APISIX reloads its configuration every second or so.

I am not sure neither. But this might overcome the etcd's soft storage limit of 8GB? [1]

[1] https://github.com/etcd-io/etcd/issues/9771