RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 867016 - rsyslog gssapi functionality gets broken with InputGSSServerPermitPlainTCP
Summary: rsyslog gssapi functionality gets broken with InputGSSServerPermitPlainTCP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rsyslog
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Tomas Heinrich
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1070830 1075802 1159820 1172231
TreeView+ depends on / blocked
 
Reported: 2012-10-16 14:45 UTC by Karel Srot
Modified: 2018-12-09 16:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1085379 1289184 (view as bug list)
Environment:
Last Closed: 2016-06-02 19:37:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
A little bit more detailed log from the testing (17.48 KB, application/octet-stream)
2012-10-16 14:54 UTC, Karel Srot 		no flags Details
View All

Description Karel Srot 2012-10-16 14:45:27 UTC 
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.


Version-Release number of selected component (if applicable):
rsyslog-5.8.10-2.el6

How reproducible:
always

Steps to Reproduce:
It is pretty complicated. I started with http://www.rsyslog.com/doc/gssapi.html
but I would recommend to contact me.
Comment 1 Karel Srot 2012-10-16 14:51:39 UTC 
I have also tested it with rsyslog built with patch from bug 862517. 

1) server accepts gssapi only && client sends gssapi only:
messages delivered but I got a netstream session error at the end (could be related to something else)

2) server accepts gssapi only && client sends tcp/plain only:
rsyslog client-server connection got stucked

3) server accepts gssapi only && clients sends both gssapi and tcp/plain:
again, rsyslog client-server connection got stucked

4) server accepts both gssapi and tcp/plain, client sends gssapi messages:
gssapi message wasn't delivered, several netstream session errors

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.
Several netstream session errors.
Comment 2 Karel Srot 2012-10-16 14:54:13 UTC 
Created attachment 628201 [details]
A little bit more detailed log from the testing
Comment 5 RHEL Program Management 2012-12-16 06:47:13 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 12 Tomas Heinrich 2013-08-20 16:26:58 UTC 
This isn't going to make it this devel-cycle. Postponing to 6.6.
Note You need to log in before you can comment on or make changes to this bug.