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.

I'm in the process of writing my first (real) Kitura app and have been lost quite a lot. Kitura often sends Cannot GET /some/endpoint. responses without any error message in the log to help debug the issue. My log consists almost exclusively of [VERBOSE] [HTTPServerRequest.swift:215 parsingCompleted()] HTTP request from=127.0.0.1; proto=http; messages, even when there have been errors. I am us

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

An upcoming revision of the PSA Crypto specification will clarify that the export format of Curve25519 and Curve448 private keys must have the forced bits set as specificed in RFC 7748 §5 (output of decodeScalar25519 and decodeScalar448).

Goal of this task:

• Update the documentation of psa_export_key in crypto.h.
• Add tests to valid

Current Behavior

Currently you can set a custom userid claim using --user-id-claim ( ref 5.1.1)
m using the oauth2_proxy in conjunction with nginx.

i would like to be able to pass group from a custom claim to upstream services.

for example
--group-claim=cognito:groups

and have the results available in X-Auth-Request-User-Groups