-
Notifications
You must be signed in to change notification settings - Fork 621
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
Fix: TLS support #1617
Fix: TLS support #1617
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.
Not sure about this fix, as the root cause why there are no client certs is not stated, even if it is clear, that either no path is configured, the given path is empty or the given path does not exist. Also not giving a client certs path could be wanted, when just TLS is sufficient
Fix: Improved the warnings and clarify why is running in TLS mode if client certs are not found. |
7cbb19f
to
bfac28e
Compare
272d687
to
324f2a5
Compare
The server didn't start if the client certs were missing. With this fix, it is possible to start the server in TLS or mTLS modes
What:
Fix: TLS support
Why:
The server didn't start if the client certs were missing. With this fix, it is possible to start the server in TLS or mTLS modes
How:
Start openvasd without client cert options, without a valid directory or an empty directory.
Checklist: