-
Notifications
You must be signed in to change notification settings - Fork 752
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
System / Settings / Logging - targets: add TLS transport option #4937
Comments
to test, |
AdSchellevis
added a commit
that referenced
this issue
Apr 30, 2021
…#4937 (use generic system ca file)
AdSchellevis
added a commit
to opnsense/docs
that referenced
this issue
Apr 30, 2021
AdSchellevis
added a commit
that referenced
this issue
Aug 15, 2021
AdSchellevis
added a commit
that referenced
this issue
Aug 15, 2021
…#4937 (use generic system ca file)
oshogbo
pushed a commit
to DynFi/opnsense-core
that referenced
this issue
Mar 3, 2022
oshogbo
pushed a commit
to DynFi/opnsense-core
that referenced
this issue
Mar 3, 2022
…opnsense/core#4937 (use generic system ca file)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Currently we support syslog over udp and tcp, one feature requested from time to time is to allow sending encrypted messages as well.
Describe the solution you like
Add TLS as target option in syslog ng, using the certificate store available in OPNsense. (https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.17/administration-guide/55)
Describe alternatives you considered
pushing syslog traffic into a (vpn) tunnel, but this doesn't seem to be a workable solution for all use-cases.
Additional context
none
The text was updated successfully, but these errors were encountered: