Hello, I was wondering how to setup a rsyslog server to accept both TLS and non-TLS connection over TCP. On the client side it is possible as all the relevant options are placed in the omfwd action itself. However, on the server side the options a located in the module, not in the input. So all the related inputs "inherit" the TLS setting from the module. It there a way to split it?
The usecase: I have system producing logs. Some of the systems are not capable of TLS. I want to collect logs from all the clients so I need to open one port for incoming TLS connections and one for non-TLS at the same time. I can imagine running separate rsyslog instance for TLS connections forwarding the traffing locally to instance with non-TLS or vice versa. But that's not really efficient solution. Thanks, Dalibor _______________________________________________ rsyslog mailing list https://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.
