3 ms·

I am not worried about xz-style intentional backdoors. I am worried about unintentional bugs which end up being remotely exploitable. So while making sure the

by theamk 2y ago

I am not worried about xz-style intentional backdoors. I am worried about unintentional bugs which end up being remotely exploitable. So while making sure the image library is bug-free is practically impossible, it is pretty easy to check for compile-time feature flags. Build it once, then ldd to make sure the http library is not linked. Or check debug messages. Or objdump and make sure method is missing. Tons of very simple methods. From this standpoint, disabling favicon fetching is a 100% effective mitigation for all remote attacks. I've never bothered uploading favicons by hand, and I've never needed any images in my notes. No security theater, just a pragmatic view.

redserk 2y ago
Yet how many people are checking what libraries are being linked on every compilation? CMakefiles are susceptible to bugs too. KeepassXC could also very well remove these build flags and people would be none the wiser. As I said, concerned users should look at other ways to isolate the application’s behavior here instead of relying on the build process. Run it in an isolated network namespace if network connectivity is the prevailing concern.