"anon" does not permit to authenticate the remote peer. As such, this mode is vulnerable to man in the middle attacks as well as unauthorized access. It is recommended NOT to use this mode. A certificate/key does not need to be configured in this authmode.
In the first link above, please consider changing anon to x509/name.
This documentation says:
We assume it accepts messages only via TLS protected plain tcp based syslog from those peers that are explicitly permitted to send to it.Despite the security goal being to allow only permitted peers, it actually allows other peers such as "man in the middle" peers as stated below:
The gtls page says:
"anon" does not permit to authenticate the remote peer. As such, this mode is vulnerable to man in the middle attacks as well as unauthorized access. It is recommended NOT to use this mode. A certificate/key does not need to be configured in this authmode.In the first link above, please consider changing anon to x509/name.