I am using openSSL 1.1.1g.

In order to be compatible with Web Crypto API (and its wrapper openCrypto) regarding encryption RSA keys, The pKCS8 (and PBKDF2) is needed. The documentation is lacking info on PKCS5_pbe2_set_iv. Is it possible to create it? Thanks.

Feature request

Feature description

We have global options to enable Dockerfile and docker-compose.yaml -- we should provide correct syntax highlighting for these files when present.

We should make the syntax highlighting for these async so that the Prism data is generated in a separate bundle file and is present in the main bundle, being loaded only when needed.

How the fea

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.

This line describing the return value PSA_ERROR_INVALID_SIZE for psa_its_get should be deleted:

https://github.com/ARMmbed/mbedtls/blob/development/library/psa_crypto_its.h#L102

• There is no error code PSA_ERROR_INVALID_SIZE.
• There is no argument data_size.
• It is not an error to ask for just part of the data.

(Also, the description of PSA_ERROR_INVALID_ARGUMENT does not

Expected Behavior

If cookie-expire is setted to long period (1 week) and cookie-refresh to 1 hour (because Google's JWT is valid 1 hour), oauth2-proxy should refresh session cookie earliest after first hour and if successfully recieve access token (JWT) oauth2-proxy should do next cookie refresh earliest after one hour (a