Support listening for syslog over TLS #1

New Issue

Closed

opened 2020-04-06 16:18:34 +00:00 by rtyler · 0 comments

rtyler commented

2020-04-06 16:18:34 +00:00

Owner

No need for client authentication at the moment, just a TLS encrypted channel

No need for client authentication at the moment, just a TLS encrypted channel

rtyler self-assigned this 2020-04-06 16:18:34 +00:00

rtyler referenced this issue from a commit

2020-04-18 22:37:20 +00:00

Add a test TLS certificate and private key and corresponding settings change This is the first part of implementing TLS support mentioned in #1. The expected options in `hotdog.yml` are as follows. syslog over plaintext TCP: ``` global: listen: tls: ``` syslog over a TLS encrypted socket ``` global: listen: tls: cert: 'path/to/cert.pem' key: 'path/to/key.pem' ```

rtyler referenced this issue from a commit

2020-04-18 22:37:20 +00:00

Implement basic support for listening for syslog over TLS This implementation is still fairly basic. There's more error-handling and refactoring that I need to do in order to clean this code up, but on its face it does the basic job of accepting TLS connections without certificate-based authentication for accepting syslog traffic. Fixes #1

rtyler closed this issue

2020-04-18 22:37:20 +00:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: rtyler/hotdog#1

No description provided.