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.

Context and Description

The READMEs and any example code in all projects should be updated to reflect the move from the IBM-Swift organization to the Kitura organization.

If anyone wants to take on all or part of this, please comment here so other's know what you're working on and submit PR's. :-)

Thanks!

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.

Currently Redis is our only supported persistent session store as an alternative to encrypted cookie sessions. Redis provides greater security, but has friction in initial setup which likely makes most users opt for cookie based sessions.

Let's aim to start supporting the table DBs of the big 3 cloud vendors, starting with DynamoDB.

Current Behavior

Only Redis is supported. It has a lo

This option is a trade-off between a feature a code size: it allows people who don't need that feature to avoid paying the cost in code size, by disabling it.

However:

• the code size savings are not that significant
• in the future we can design a mechanism for that an other ssl_config options that will save more code size and be more uniform, see #3535 "Hardcoding of SSL options"

Wor