-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/tls #17
Feature/tls #17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! But I also don't understand how this will fit into the larger system so would recommend you wait on Dave's approval too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments, but nothing that should be too hard to address... but let me know if you want me to take another look at anything.
These checks make the code and the testing more complicated. Instead, we check that the internal fields are not nil after creation.
This PR adds the tools needed by the
nitriding
server
(future PR) to get certificates to create TLS connections.Notable changes:
type Builder[T any] interface
, which allows us to remove all the specific builder interfaces likeAttesterBuilder
etc. For not I only used this interface to get rid specific builder interfaces in this PR, but I plan on updating older code as well. Not doing it now because it would result in changes all over the place and make the review of the new TLS code harder.