Adding AWS-LC as a supported libcrypto

Open
#434 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp

Research direction

Start by comparing OpenVPN3's current libcrypto integration with the AWS-LC compatibility and build changes described in the issue, then review the linked OpenVPN support commits for precedent. Done means AWS-LC is available as an OpenVPN3 provider option with the required compatibility shims and build configuration changes.

Written by the indexing model from the issue text.

Description

Hi,

I'm a maintainer at AWS-LC, a libcrypto that is API compatible with OpenSSL. We'd like to add support for AWS-LC as a provider option in OpenVPN3. It would give users a FIPS-validated and post-quantum capable crypto option. The changes would be mostly small compatibility shims for the few API differences and build configuration modifications.

OpenVPN already officially supports AWS-LC and is part of the CI, so we'd be extending this precedent to OpenVPN3. Would you be open to a PR for this?

Dominant language
C++
Stars
1.2k
Forks
473
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenVPN/openvpn3

All issues in OpenVPN/openvpn3

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.