I don't believe that this is currently supported. the main reason for
implementing this is almost always either to have the data encrypted when going
over the Internet or to prevent unknown/untrusted systems from delivering logs
to rsyslog. The mode where the server doesn't care who is sending it logs but
the client cares that it's sending to the right server is not a use case that
was considered as far as I know.
David Lang
On Mon, 2 Mar 2015, stephane martin wrote:
Date: Mon, 2 Mar 2015 00:17:15 +0100
From: stephane martin <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: [email protected]
Subject: [rsyslog] TLS with RELP or TCP syslog: certificate just for the
server
?
Hello,
i've been playing with rsyslog for a few months. The product is so great :)
Just a quick question : i'd like to have a rsyslog server, offering RELP
and TCP over TLS to clients. So far, the configuration examples I've found
need the client to show certificates to the server.
Is it possible to have a scheme so that only the server has a X509
certificate, and the client just connects to it, like in a typical HTTPS
use case?
Regards,
Stephane
_______________________________________________
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.
_______________________________________________
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.