Yes, that feature to restrict host data collection has value. But that, clearing and Incognito would defeat the purpose of Usage for the obsessive compulsive user (me) who needs to know what everything is doing, and when. I often use Month and Custom.
Personally, I’d have no problem submitting my glasswire.db file under warrant. It just hit me that a plaintext history store within a security app just didn’t jive.
My curiosity about that plaintext nature of glasswire.db stemmed from the SSL badge and “Server list is encrypted” detail in the Server List settings pane. And the option to enable an admin account, the credentials surely not stored in a plaintext file. My assumption is the same routines can be used for the glasswire.db file; I could stand to be corrected.
What you say about a key is true, but vulnerability is a risk when the key is poorly implemented and/or locked with a dumb password.
At this point, I make the suggestion to encrypt the glasswire.db file. A setting during install would present an option to do so with the usual “may affect performance, you can change this later” caveat and a Settings option to disable it with the other usual “if you experience performance issues” note. The Qt5 core is quite an efficient platform, so you’d probably not see too many customers opting out. Of course, that’s not to dismiss users locked into legacy hardware due to social or political factors. Encryption would mandate the creation of an admin account.
It could be GeoLite2 is up to date for the purpose of flag and region data. Very little has changed geopolitically in that respect over the last two years. I’m familiar with MaxMind databases, among others, having used them in enterprise security apps to allert accessing within nations specific regions known for nefarious deeds. (I use the free GeoLiteCity.dat database in Nirsoft’s CurrPorts network monitor.) Forgive my OC disposition wherein a two year old file unnecessarily tweaks sirens and flashing lights…
No reply needed or expected. Cheers!