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

Allow version '0' for structured syslog messages #3503

Merged
merged 1 commit into from Feb 16, 2017
Merged

Conversation

@joschi
Copy link
Contributor

@joschi joschi commented Feb 15, 2017

Although RFC 5424 clearly states that '1' is the only valid version for structured syslog
messages, some syslog daemons are using '0' as a version identifier.

https://tools.ietf.org/html/rfc5424#section-9.1

Fixes #3502

Althought RFC 5424 clearly states that '1' is the only valid version for structured syslog
messages, some syslog daemons are using '0' as a version identifier.

https://tools.ietf.org/html/rfc5424#section-9.1

Fixes #3502
@joschi joschi added this to the 2.2.1 milestone Feb 15, 2017
@joschi
Copy link
Contributor Author

@joschi joschi commented Feb 16, 2017

This also has to be back-ported into 2.2.

@dennisoelkers dennisoelkers merged commit af1a258 into master Feb 16, 2017
4 checks passed
4 checks passed
@garybot2
ci-web-linter Jenkins build graylog-pr-linter-check 1357 has succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
licence/cla Contributor License Agreement is signed.
Details
dennisoelkers added a commit that referenced this pull request Feb 16, 2017
Althought RFC 5424 clearly states that '1' is the only valid version for structured syslog
messages, some syslog daemons are using '0' as a version identifier.

https://tools.ietf.org/html/rfc5424#section-9.1

Fixes #3502
(cherry picked from commit af1a258)
@joschi joschi deleted the issue-3502 branch Feb 16, 2017
@jalogisch jalogisch mentioned this pull request Feb 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants