Hi all, just discovered the documentation of TLS encrypted setup [1] should be extended to mention the clientAuth extended attribute is needed only for rsyslog client and serverAuth for rsyslog target server. At least for simple imtcp/omtcp it's true; could somebody test the RELP part? Don't see any reason why it should be different.
The only limitation I see here is that rsyslog doesn't support to have different certificates for receiving and sending syslog messages and the same used for all TLS communication channels. In that case the sending/receiving is needed the rsyslog instance need the certificate with both attributes serverAuth and clientAuth. [1] http://www.rsyslog.com/doc/rsyslog_tls.html -- Peter Viskup _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
