In order to get clients to send a certificate when connecting, certauth sets SSL_VERIFY_PEER on all ports. This makes sense for the default case, but it would be nice to be able to configure this on a per-listener basis. Sample usecase: setting SSL_VERIFY_PEER on port 6697 would allow you to use certauth for IRC connections, while having it unset on port 443 would let you access the web console without getting prompted for a client certificate.
In order to get clients to send a certificate when connecting, certauth [sets `SSL_VERIFY_PEER` on all ports][all ports]. This makes sense for the default case, but it would be nice to be able to configure this on a per-listener basis. Sample usecase: setting `SSL_VERIFY_PEER` on port 6697 would allow you to use certauth for IRC connections, while having it unset on port 443 would let you access the web console without getting prompted for a client certificate.
[all ports]: https://github.com/znc/znc/blob/znc-1.7.0/modules/certauth.cpp#L46-L52
<!-- github-sync-id:336342750 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In order to get clients to send a certificate when connecting, certauth sets
SSL_VERIFY_PEERon all ports. This makes sense for the default case, but it would be nice to be able to configure this on a per-listener basis. Sample usecase: settingSSL_VERIFY_PEERon port 6697 would allow you to use certauth for IRC connections, while having it unset on port 443 would let you access the web console without getting prompted for a client certificate.