jks

Debugging aids for me. Push "dump" and see what you get in the log. "Clear histogram" followed by "dump" is a little more subtle.

So there has been significant port scanning of kiwisdr.com recently. For example, over the last 24 hours 173 thousand scan requests were made by a single ip address from China. Also from a Digital Ocean server farm in the USA.

Some of these scans occur on the proxy ports. If the URL or packet data is particularly pathological it might trigger bugs in the proxy server code (e.g. buffer overruns). This could explain the looping and crash/restart behavior we've seen in the last several days.

Rather than try and debug the proxy code (which we didn't write), and cause significant additional proxy downtime, it was easier to strengthen our existing firewall filtering rules. Port scanning is now more reliably detected and the associated ip addresses banned.

We will closely monitor the situation and see how effective the new rules are.

The proxy service is having serious problems. There is some evidence that it is under attack, but this is not yet confirmed.

No. If the configuration files are ever missing in kiwi.config they are copied from the defaults in the distro. They are never touched after that (unless removed). This is because you can't tell from that point if they have been modified by the admin/owner. So for the vast majority of Kiwis the files in kiwi.config are those copied during the very first startup of v1.2 in the factory. There was a slight format change to the files in a later version but that's a different story.

Thanks. Will fix Makefile in next release to ignore a failed "systemctl {stop,disable} lightdm.service".