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

Allow to use KeyManagerFactory / TrustmanagerFactory #141

Merged
merged 1 commit into from
Jan 25, 2021
Merged

Conversation

normanmaurer
Copy link
Member

Motivation:

People often want to use their own custom keymaterial selection / certificate validation. This was not possible as all of this was handled internally by quiche.

Modification:

  • Allow to implement custom key material selection
  • Allow to implement custom certificate validation
  • Port over some code from netty-tcnative / netty
  • Use our own vendored boringssl libraries when compiling

Result:

Fixes #97

@normanmaurer
Copy link
Member Author

We can simplify some of this when netty/netty#10953 is merged

normanmaurer added a commit to netty/netty that referenced this pull request Jan 21, 2021
Motivation:

Creating certificates from a byte[] while lazy parse it is general useful and is also needed by netty/netty-incubator-codec-quic#141

Modifications:

Move classes, rename these and make them public

Result:

Be able to reuse code
normanmaurer added a commit to netty/netty that referenced this pull request Jan 21, 2021
Motivation:

Creating certificates from a byte[] while lazy parse it is general useful and is also needed by netty/netty-incubator-codec-quic#141

Modifications:

Move classes, rename these and make them public

Result:

Be able to reuse code
@normanmaurer
Copy link
Member Author

/cc @thomdev @kachayev

Motivation:

People often want to use their own custom keymaterial selection / certificate validation. This was not possible as all of this was handled internally by quiche.

Modification:

- Allow to implement custom key material selection
- Allow to implement custom certificate validation
- Port over some code from netty-tcnative / netty
- Use our own vendored boringssl libraries when compiling

Result:

Fixes #97
@normanmaurer normanmaurer merged commit 697d64c into main Jan 25, 2021
@normanmaurer normanmaurer deleted the inject_ssl branch January 26, 2021 18:19
ZzxyNn pushed a commit to ZzxyNn/netty that referenced this pull request Jan 29, 2021
Motivation:

Creating certificates from a byte[] while lazy parse it is general useful and is also needed by netty/netty-incubator-codec-quic#141

Modifications:

Move classes, rename these and make them public

Result:

Be able to reuse code
normanmaurer added a commit to netty/netty that referenced this pull request Mar 7, 2021
Motivation:

Creating certificates from a byte[] while lazy parse it is general useful and is also needed by netty/netty-incubator-codec-quic#141

Modifications:

Move classes, rename these and make them public

Result:

Be able to reuse code
raidyue pushed a commit to raidyue/netty that referenced this pull request Jul 8, 2022
Motivation:

Creating certificates from a byte[] while lazy parse it is general useful and is also needed by netty/netty-incubator-codec-quic#141

Modifications:

Move classes, rename these and make them public

Result:

Be able to reuse code
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.

Investigate if we can use quiche_conn_new_with_tls to interface with our SslContext implementation
1 participant