See the discussion here: https://caddy.community/t/v2-http-handlers-templates-functions-in-file-server-browse-template/9214

The file_server directive has a browse option which enables a directory index to be served when a directory is requested. By default, this index is rendered using a template which can be [found in the cod

In the manual of master and v1.1.1. (also may in the more older versions)
At detail of the BN_mask_bits.
(https://www.openssl.org/docs/manmaster/man3/BN_mask_bits.html)
(https://www.openssl.org/docs/man1.1.1/man3/BN_mask_bits.html)

Hi, all.

Pseudo code of the detail "a&=~((~0)>>n)", it means following computation, I think,
~0 : 11...(m-bits 1)...11 (left bit is higher, m is bit length

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)

Describe the solution you'd like
helm-docs Is a nice little utility for auto-generating the Parameters table from comments in the values.yaml file. It would make PRs into the chart much easier, because you don't need to document in multiple places, and you don't need to edit a huge markdown table.

If you're open to this, I could probably work a PR f

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:

As mentioned in the comment New cipher suites MUST be added here, IN ORDER, or they will not be properly initialized.

https://github.com/awslabs/s2n/blob/64297d8ce45a38394094f1c31b2ecf5735472edb/tls/s2n_cipher_suites.c#L768-L772

Solution:

Unit test to validate the array order.

• **Does

tests/include/test/psa_crypto_helpers.h contains function definitions. That's a remnant from when we didn't have tests/src/*.c and unit tests had to be compiled as a monolithic C file. It's a problem because merely including the header causes an unused-function warning. The header should contain only function declarations (or static inline function definitions, but the functions in that head

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