Red Hat Bugzilla – Bug 1289184
rsyslog gssapi functionality gets broken with InputGSSServerPermitPlainTCP
Last modified: 2016-07-27 05:44:34 EDT
+++ This bug was initially created as a clone of Bug #867016 +++
Description of problem:
rsyslogd crashes or hangs or looses log messages in various configurations.
This is a bit complex problem.
rsyslogd can be configured using InputGSSServerPermitPlainTCP on to accept both gssapi and tcp/plain messages. I have tested following 6 scenarios:
1) server accepts gssapi only && client sends gssapi only:
works fine except AVC denials reported as bug 867001
2) server accepts gssapi only && client sends tcp/plain only:
rsyslog crashes, this is reported as bug 862517.
3) server accepts gssapi only && clients sends both gssapi and tcp/plain:
again, rsyslog crashes
4) server accepts both gssapi and tcp/plain, client sends gssapi messages:
gssapi messages are not delivered
5) server accepts both gssapi and tcp/plain, client sends plain messages only:
plaintext only messages can be delivered with $InputGSSServerPermitPlainTCP on, but the log is flooded with netstream session errors
6) server accepts both gssapi and tcp/plain, client sends both gssapi and plain messages
nor tcp nor gssapi messages are delivered because of issues in client-server
communication. But tcp/plain messages sent by netcat were delivered.
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.