Fabian Keil

3.0.34 segfaults Editing actions

Thanks for the report. Does this happen for all action files or only one specific one? Did you modify the action file(s) that trigger the segfault?

I can reproduce the issue that the comments don't load on https://www.kommersant.ru/ but on my systems the problem seems to be that connections to i.kommersant.ru already fail before the TLS handshake: fk@elektrobier ~ $curl -v --head https://i.kommersant.ru/ * Host i.kommersant.ru:443 was resolved. * IPv6: (none) * IPv4: 185.147.37.72 * Trying 185.147.37.72:443... * connect to 185.147.37.72 port 443 from 95.211.138.7 port 63777 failed: Operation timed out * Failed to connect to i.kommersant.ru port...

i.kommersant.ru remains unreachable for me but I can reproduce the problem with https://traxxas.com/ with both Privoxy and curl linked against wolfSSL 5.7. I consider this a wolfSSL bug worth reporting upstream. Do you want to do it or should I?

Which WolfSSL version do you use? When I try i.kommersant.ru it doesn't seem to respond to requests to port 443 so it doesn't work with either OpenSSL or WolfSSL for me.

Fix build on macOS

Thanks a lot for the patch. Pushed to git master.

ipleak.net site does not work