haarp
haarp
I finally managed to to reach the bugged state during a log verbosity = 4 run and collected some logs. I don't have an exact timestamp for when it started...
Thanks for having a look! > 1. I don't see 10x received queries in Unbound each second, even during times of Unbound "idleness" (not logging anything else) > 2. The...
> and there's a huge list of local-data entries to block ad domains. This only started happening after I added the ad domains blocklist. Be sure to give unbound time...
Interesting. Does it react to unbound-control in this state? Does SIGTERM work or do you need to SIGKILL it?
Interesting. Call it a hunch, but I suspect TLS forwarding might be the culprit.
> `unbound-control` does reply in this state. Hmm, seems like your case is different from this bug then.
And if anyone is worried about compromised hardware instructions, Tor already took precautions: https://gitlab.torproject.org/tpo/core/tor/-/issues/10402
It gets weirder. Not even changing the `settings.swipe.*` `value_or()` parameters in config/config.cpp and commenting them in the config instead seems to have any influence on swipe behavior whatsoever. This is...
> are you sure your config file is in correct location and being read by the deamon? Yes, it is using the correct commands for the swipes, which can only...
I think something else is going on that none of the swipe settings have an effect.