s2n VS rke2

It seems to support multiple options but requires you pick at least one of them. https://github.com/aws/s2n-tls/blob/main/docs/BUILD.md#build...

I think GnuTLS is probably the second most popular TLS library, after openssl.

I'll also mentions s2n and rustls-ffi for completeness as C libraries, though the former isn't widely used, and the latter is very experimental still. https://github.com/aws/s2n-tls and https://github.com/rustls/rustls-ffi respectively.

I've seen operating on unauthenticated plaintext enough times to list it as my own pet peeve with AES-GCM. But it's a problem for chunked messages too. A few years ago we released a SCRAM mode that makes very minimal changes to AES-GCM so that it mathematically can't operate on unauthenticated plaintext. https://github.com/aws/s2n-tls/tree/main/scram

> The documentation is kind of vague, but apparently you have to re-enable it regularly.[3]

This is correct. And in the end it means more or less that setting the socket option is more of a way of sending an explicit ACK from userspace than a real setting.

It's not great for common use-cases, because making userspace care about ACKs will obviously degrade efficiency (more syscalls).

However it can make sense for some use-cases. E.g. I saw the s2n TLS library using QUICKACK to avoid the TLS handshake being stuck [1]. Maybe also worthwhile to be set in some specific RPC scenarios where the server might not immediately send a response on receiving the request, and where the client could send additional frames (e.g. gRPC client side streaming, or in pipelined HTTP requests if the server would really process those in parallel and not just let them sit in socket buffers).

[1] https://github.com/aws/s2n-tls/blob/46c47a71e637cabc312ce843...

It looks like by default s2n-quic uses this TLS implementation, which is not based on the ring crate (though it is written in C)

https://github.com/aws/s2n-tls

I would be interested in the other SSL implementations:

- https://github.com/awslabs/s2n

- https://boringssl.googlesource.com/boringssl

- https://bearssl.org/

Are these subpar implementations or there are other reasons not to use these?

In this essay, we showed how to use Rancher rke2 to deploy a Kubernetes cluster with 6 Debian nodes with firewall enabled. We've also covered deploying Cilium as a CNI for our cluster and have it completely replace kube-proxy so as to increase speed and gain more observability via Cilium tools. This article also showed how to deploy Metallb to manage IP pools and load balance traffic for those IP pools. Throughout this guide, we assumed that we have an external load balancer that will distribute traffic to our workload and control plane nodes. For further information please visit rke2 official documents: "https://docs.rke2.io/".

In this blog post, we will demonstrate how easy and fast it is to deploy Sveltos on an RKE2 cluster with the help of ArgoCD, register two RKE2 Cluster API (CAPI) clusters and create a ClusterProfile to deploy Prometheus and Grafana Helm charts down the managed CAPI clusters.

Did something happen to the Apache 2 rancher? https://github.com/rancher/rancher/blob/v2.7.5/LICENSE RKE2 is similarly Apache 2: https://github.com/rancher/rke2/blob/v1.26.7%2Brke2r1/LICENS...

To provision all of my clusters, I use Rancher with RKE2. The primary Rancher server is hosted on a bootstrapped RKE2 cluster running on a VPS.

Golang has burned me more than once with bizarre design decisions that break things in a user hostile way.

The last one we ran into was a change in Go 1.15 where servers that presented a TLS certificate with the hostname encoded into the CN field instead of the more appropriate SAN field always fail validation.

The behavior could be disabled however that functionality was removed in 1.18 with no way to opt back into the old behavior. I understand why SAN is the right way to do it but in this case I didn’t control the server.

Developers at Google probably never have to deal with 3rd parties with shitty infrastructure but a lot of us do.

Here’s a bug in rke that’s related https://github.com/rancher/rke2/issues/775

just looking at this myself. I think k3s has more support for arm, but looking through the github repo there are a lot of bugs indicating its a mess. RKE2 seems to be their big push, they also have a github issue open that has been open for the last 2 releases that they are going to add a update path from k3s to rke2. https://github.com/rancher/rke2/issues/881

RKE (https://rancher.com/docs/rke) and RKE2 (https://docs.rke2.io/) from Rancher folks