Good question. Without any certificate check schat is not actually secure. So the correct fingerprint would need to somehow be communicated first, perhaps via IRC, but that would be a protocol change. Another option is to provide that as command line option when accepting the chat and requiring user to somehow know the fingerprint
Either way, as is, the module is now useless. And since noone complained about this since 2014, noone is using it. So I think it can be safely removed
> How should znc handle this?
Good question. Without any certificate check schat is not actually secure. So the correct fingerprint would need to somehow be communicated first, perhaps via IRC, but that would be a protocol change. Another option is to provide that as command line option when accepting the chat and requiring user to somehow know the fingerprint
Either way, as is, the module is now useless. And since noone complained about this since 2014, noone is using it. So I think it can be safely removed
<!-- github-comment-id:5312967902 -->
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.
Git bisect shows commit
4442af724f- "Validate TLS certificate of IRC server." caused this regression.How should znc handle this?
znc -D log from commit
4442af724f:znc -D log from a commit before "Validate TLS certificate of IRC server." without the issue:
Good question. Without any certificate check schat is not actually secure. So the correct fingerprint would need to somehow be communicated first, perhaps via IRC, but that would be a protocol change. Another option is to provide that as command line option when accepting the chat and requiring user to somehow know the fingerprint
Either way, as is, the module is now useless. And since noone complained about this since 2014, noone is using it. So I think it can be safely removed
well, I suppose one could make a non-self-signed cert for their IP, and use that