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

TLS key system v1 #1185

Merged
merged 8 commits into from
Aug 18, 2024
Merged

TLS key system v1 #1185

merged 8 commits into from
Aug 18, 2024

Conversation

TinCanTech
Copy link
Collaborator

@TinCanTech TinCanTech commented Jul 6, 2024

#1121

Note: There is no unit test for gen-tls-*-key because OpenVPN may not be installed on GHA. Also, the command is simple enough that a unit test is not required. However, unit testing the inlining of a TLS key will be advantageous (OpenVPN/easyrsa-unit-tests#62).

@TinCanTech TinCanTech self-assigned this Jul 6, 2024
@TinCanTech TinCanTech added the development Possible changes label Jul 6, 2024
@TinCanTech TinCanTech added this to the v3.2.1 milestone Jul 6, 2024
@TinCanTech TinCanTech removed this from the v3.2.1 milestone Jul 7, 2024
@TinCanTech TinCanTech force-pushed the tls-key-system-v1 branch 2 times, most recently from a3eb4b2 to 05dfccb Compare July 8, 2024 01:33
@TinCanTech
Copy link
Collaborator Author

Inlining files is only suitable for OpenVPN, therefore, inlining should only be done for recognized certificate types server and client.

Add OpenVPN --key-direction for TLS-AUTH keys.

Signed-off-by: Richard T Bonhomme <[email protected]>
Only inline TLS Keys for certificate type 'server' and 'client'.

Signed-off-by: Richard T Bonhomme <[email protected]>
@TinCanTech TinCanTech merged commit 07f8c0d into OpenVPN:master Aug 18, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant