Project

General

Profile

Actions
Copy link

Regression #12160

closed

An invalid configuration is generated when choosing TLS as the default protocol

Added by Markus * over 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Jim Pingle
Category:
syslog-ng
Target version:
-
Start date:
07/23/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

This regression was introduced by this commit.

Actions
Copy link
 #1

Updated by Markus * over 3 years ago

A solution has been proposed here and awaits confirmation by the reporter.

Actions
Copy link
 #2

Updated by Markus * over 3 years ago

A pull request has been created.

Actions
Copy link
 #3

Updated by Jim Pingle over 3 years ago

  • Status changed from New to Pull Request Review
  • Assignee set to Jim Pingle
Actions
Copy link
 #4

Updated by Jim Pingle over 3 years ago

  • Status changed from Pull Request Review to Feedback

PR merged.

Actions
Copy link
 #5

Updated by Azamat Khakimyanov over 2 years ago

  • Status changed from Feedback to Resolved

Tested on 22.05 and on 22.09-DEV

There was no problem using TLS as a default protocol for syslog-ng. I was able successfully create Syslog Server and Client with Protocol: TLS and send logs from Client to Server.

I marked this Regression report as resolved.

Actions
Copy link

Also available in: Atom PDF