Description of problem:
This is kind of an interesting problem that crosses a couple of programs and is not specifically rsyslog related, though rsyslog probably shouldn't core dump on the error.
The issue is when using rsyslog with TLS enabled, if the private key is held in the PKCS#8 format, rsyslog will core dump with the following error:
unexpected GnuTLS error -207 in nsd_gtls.c:197: Base64 unexpected header error.
Now as I said the issue only occurs with PKCS#8 formatted keys, you can find more info on that format here:
It looks like this problem has been solved in gnutls > 2.12, as referenced here:
I doubt an upgrade to a different version of gnutls is feasible but perhaps a back port of said feature could help.
For rsyslog it probably shouldn't just core dump on the issue. A bug about this is open here:
If you are interested this issue all arose because certmaster switched to using PKCS#8 format in RHEL 6. I know certmaster is unsupported, and I have yet to find out if the switch was intentional or not, but there we are.
Version-Release number of selected component (if applicable):
Use a PKCS#8 formatted pricate key
Perhaps an error?
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
This is the gnutls commit for reference:
The core dump must be solved on the rsyslog side.
Also please use the regular support channels to request the bug to be fixed. It is necessary for proper prioritizing.
Case #00513502 has been open for two months before I finally gave up and opened this BZ. Hopefully this will allow you to prioritize etc.
The core dump fix is the bug 727380 for reference.
*** Bug 798054 has been marked as a duplicate of this bug. ***
Ha, forgot I filed this bug, so filed another one. Ah, how funny.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.