Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Contributions to OpenVPN #1

Open
wants to merge 3 commits into
base: upstream
Choose a base branch
from
Open

Contributions to OpenVPN #1

wants to merge 3 commits into from

Conversation

smittals2
Copy link
Owner

@smittals2 smittals2 commented Jan 15, 2025

This is a local PR to gather internal feedback before we contribute these changes to OpenVPN.

Thank you for your contribution

You are welcome to open PR, but they are used for discussion only. All
patches must eventually go to the openvpn-devel mailing list for review:

Please send your patch using git-send-email. For example to send your latest commit to the list:

$ git send-email [email protected] HEAD~1

For details, see these Wiki articles:

strategy:
fail-fast: false
matrix:
os: [ubuntu-22.04]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do they use specific versions or ubuntu-latest in other builds?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using ubuntu 22.04. Copied most of the boilerplate from other tests. Changed all the build steps tho

with:
path: aws-lc
repository: aws/aws-lc
ref: main

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For their other libcryptos do they use a specific release or follow main?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mbedtls and libressl use a tagged release, but I think we should be following main to have two way compatibility checks. I guess we're testing mainline LC in our CI with OpenVPN anyway so we don't need to. I don't have a preference, thoughts?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, if we're building their main and not running into any breaking changes then this is probably fine. I just don't want to create noise in their CI if something subtle changes.

.github/workflows/build.yaml Outdated Show resolved Hide resolved
README.aws-lc Outdated Show resolved Hide resolved
src/openvpn/ssl_openssl.c Show resolved Hide resolved

*************************************************************************
Due to limitations in AWS-LC, the following features are missing
* Windows CryptoAPI support

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this effect OpenVPN customers? Can you use OpenVPN through the Windows CryptoAPI? Or does OpenVPN use Windows CryptoAPI to do something that doesn't work with AWS-LC now?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like OpenVPN has some support for the Windows CryptoAPI. OpenSSL has some APIs that seem to work with CryptoAPI but we don't support these like wolfssl and mbedtls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants