As mentioned in #3854, Let's Encrypt now provides two different chains when acquiring a certificate: one with a cross-signed root certificate (default) and one with a self-signed root certificate.

I'd like to use the alternative chain, which seems to be possible using the preferred_chains option in Caddy. From what I'v

Just for RSA. Do encrypt and decrypt. Include a bold comment that this should not be used for bulk encryption.

It should be the current best practice (fetch), have proper error handling and resource allocation/deallocation and be in the style of a known answer test.

Right now in different places in the SE codebase there are references to /opt and then as well to /usr.

All SE code should reference one place only. Could someone please create a PR that fixes this.

This PR should also take PR #454 into consideration (no conflicts)

Is your feature request related to a problem? Please describe.

In order to address issue #3796, PR #3815 runs the e2e tests in series one after the other. It would be nice to run the tests in parallel again as that would lead to all the tests completing earlier.

Describe the solution you'd like

There's little information about what keys and values are in the output, what it means and how they are related to the screen output. In general that needs to be added. (special topics see #1675, #1674)

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.

What would you like to be added

Add support for a DynamoDB storage backend. Although MySQL is available, it would require to run a RDS Instance for it. Extra costs, backup considerations, etc. Even with Aurora Serverless.

DynamoDB is just there, scales as needed with OnDemand pricing and has fine backup capabilities.

Why this is needed

We plan to run step-ca in AWS ECS on Farga

mbedtls_debug_print_ecp is prints a point by printing its X and Y coordinates. This is a little weird with Montgomery curves since the internal representation does not use the Y coordinate so it's printing 0.

A minor issue revealed by @lhuang04 in #4578. It triggered the more serious bug ARMmbed/mbedtls#4608.