I got disconnected from one network which doesn't have valid certificate at 3:47:23+0200 and now it's 07:33+0200 and I am at computer and can accept the certificate.
This network has 4 servers specified and scrollback looks like ZNC has been cycling between these 4 servers for hours.
I got disconnected from one network which doesn't have valid certificate at 3:47:23+0200 and now it's 07:33+0200 and I am at computer and can accept the certificate.
This network has 4 servers specified and scrollback looks like ZNC has been cycling between these 4 servers for hours.
<!-- github-sync-id:51389719 -->
In case of MitM, it could be a temporary problem. When attacker stopped attacking, the same server would connect fine. Do you want every one-second attack to make ZNC just stop attempts to connect to the right server?
Check that ServerThrottle setting is > 0. That way it won't hammer server with failed connects.
1. In case of MitM, it could be a temporary problem. When attacker stopped attacking, the same server would connect fine. Do you want every one-second attack to make ZNC just stop attempts to connect to the right server?
2. Check that ServerThrottle setting is > 0. That way it won't hammer server with failed connects.
<!-- github-comment-id:66247938 -->
In case of MitM, it could be a temporary problem. When attacker stopped attacking, the same server would connect fine. Do you want every one-second attack to make ZNC just stop attempts to connect to the right server?
I said that there are four servers specified and ZNC cycled between them all for hours until I attached to it and noticed the issue. Of course one-second attack might not make sense, but if it continues for longer period of time like some hours stopping connection attempts would make sense.
Check that ServerThrottle setting is > 0. That way it won't hammer server with failed connects.
10
> 1. In case of MitM, it could be a temporary problem. When attacker stopped attacking, the same server would connect fine. Do you want every one-second attack to make ZNC just stop attempts to connect to the right server?
I said that there are four servers specified and ZNC cycled between them all for hours until I attached to it and noticed the issue. Of course one-second attack might not make sense, but if it continues for longer period of time like some hours stopping connection attempts would make sense.
> 1. Check that ServerThrottle setting is > 0. That way it won't hammer server with failed connects.
10
<!-- github-comment-id:66249736 -->
If attack stopped after 1 hour, 3 more hours it won't connect, until you come to computer?
Exponential backoff in case of connection errors would help.
If attack stopped after 1 hour, 3 more hours it won't connect, until you come to computer?
Exponential backoff in case of connection errors would help.
<!-- github-comment-id:66253865 -->
I think better solution for this which would work for everyone would be fixing https://github.com/znc/znc/issues/67.
<!-- github-comment-id:138898064 -->
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.
I got disconnected from one network which doesn't have valid certificate at 3:47:23+0200 and now it's 07:33+0200 and I am at computer and can accept the certificate.
This network has 4 servers specified and scrollback looks like ZNC has been cycling between these 4 servers for hours.
oh and I am on ZNC - 1.5.0-git-414-3201146 - http://znc.in
IPv6: yes, SSL: yes, DNS: threads, charset: no
I said that there are four servers specified and ZNC cycled between them all for hours until I attached to it and noticed the issue. Of course one-second attack might not make sense, but if it continues for longer period of time like some hours stopping connection attempts would make sense.
10
If attack stopped after 1 hour, 3 more hours it won't connect, until you come to computer?
Exponential backoff in case of connection errors would help.
I think better solution for this which would work for everyone would be fixing https://github.com/znc/znc/issues/67.