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

On Windows use SChannel, not OpenSSL, for TLS connections #9955

Open
4 tasks
Al2Klimov opened this issue Jan 3, 2024 · 0 comments · May be fixed by #9956
Open
4 tasks

On Windows use SChannel, not OpenSSL, for TLS connections #9955

Al2Klimov opened this issue Jan 3, 2024 · 0 comments · May be fixed by #9956
Assignees
Labels
area/api REST API area/distributed Distributed monitoring (master, satellites, clients) area/windows Windows agent and plugins

Comments

@Al2Klimov
Copy link
Member

Is your feature request related to a problem? Please describe.

As we ship OpenSSL on Windows, we have to update Icinga along with OpenSSL.
Every OpenSSL update is a security update by definition.

Describe the solution you'd like

  • typedef boost::asio::ssl::stream SslStream; or similar
  • use SslStream everywhere, not boost::asio::ssl::stream
  • on Windows make SslStream a custom class using SChannel, not OpenSSL
  • same with boost::asio::ssl::context => SCHANNEL_CRED

Describe alternatives you've considered

@Al2Klimov Al2Klimov added area/distributed Distributed monitoring (master, satellites, clients) area/api REST API area/windows Windows agent and plugins labels Jan 3, 2024
@Al2Klimov Al2Klimov self-assigned this Jan 3, 2024
@Al2Klimov Al2Klimov linked a pull request Jan 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api REST API area/distributed Distributed monitoring (master, satellites, clients) area/windows Windows agent and plugins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant