Josh Aas

We (ISRG / Let's Encrypt) do not allow clients to use our service's name in their client name. We recommend you use the term "ACME" instead, in reference to the...

When a path has a quote, like "Josh's favorite image.png", we get unclosed quotes errors from python.

I think our Getting Started page could be much better than it is. We drive new visitors towards this from our main page, so improving it probably has a lot...

include more basic information about what we do

2

I have heard a few complaints recently that our website doesn't give people enough of a basic summary about what we actually do/offer. In other words, we presume too much...

create a page explaining why we believe every website should use HTTPS

2

This information is central to our mission and a page laying out our argument will be a helpful resource in multiple communications contexts.

consider providing binary releases

42

I was hoping to avoid doing this to keep project overhead low (having to make formal builds on a bunch of platforms every time we release), but based on feedback...

create system for evaluating compression improvements

2

As we work on this project we'll need a reliable way to measure the progress of compression improvements. Ideally this can be an automated set of tests using various metrics...

optimize receiving data with TLS 1.2 and aes-128-gcm

2

We ran the Rustls benchmarking tool with the Rustls v0.23 release and Rustls appears to be a bit slower than OpenSSL 3.2.0 when receiving data with TLS 1.2 and aes-128-gcm....

optimize server-side full handshakes for TLS 1.2 and 1.3

2

We ran the Rustls benchmarking tool with the Rustls v0.23 release and Rustls appears to be a bit slower than OpenSSL 3.2.0 on server-side full handshakes for TLS 1.2 and...

We ran the Rustls benchmarking tool with the Rustls v0.23 release and Rustls appears to be a bit slower than OpenSSL 3.2.0 when receiving data with TLS 1.3 and aes-256-gcm....