> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Wednesday, June 01, 2011 2:54 PM > To: [email protected] > Subject: [rsyslog] version 4.4.2 and TLS > > Dear all, > > as far as I know, RHEL currently still comes with version 4.4.2 of rsyslog, which > is a rather elderly version, even within the 4.x branch.
To the best of my knowledge, they ship some 3.x version, but I would be delighted to hear it has been updated. > We encounter a few > problems related to this version and TLS, currently, and also it seems to me > like this version was one of the first 4.x ones to support TLS. > > That is why I would like to ask, if it is possible to build a secure (in terms of > system stability and in terms of encryption via TLS) syslog architecture based > on this version? I strongly recommend against this. The reason is that a very serious bug [1] is present in this code base. It can lead to clients looking up and doing nothing but loop (until restart). Looking at the ChangeLog, there are also a number of other bugs which have been fixed since 4.4.2 was current (roughly 18 month ago, what is a very large time for rsyslog...). If you insist on using that version, probably the best thing to do is use plain tcp syslog together with stunnel. But this has its own operational drawbacks. The proper thing to do is to use a recent and supported version, so that we can look and fix at any issues you may experience. HTH Rainer [1] http://bugzilla.adiscon.com/show_bug.cgi?id=194 > > Best regards > Ole > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
