4 ms·
Most important any audit should state methodology and assumptions and report findings based on this. My big problem with KeepassXC is that the threat model is
by riedel 4y ago
Most important any audit should state methodology and assumptions and report findings based on this.
My big problem with KeepassXC is that the threat model is not well documented. It does a lot of fuzz around memory randomisation but it might be much easier to extract the secret key of the browser extension when unlocked. So I guess it mostly provides security for data at rest, but afaik this is not documented. A general security audit is IMHO difficult if nobody states any guarantees.
- moritzwarhier 4y agoIf the browser extension allowed leakage, I'd expect it to come from prepared pages and a JS exploit that can fake other origins, or from some stupid DOM information leak of the injected popups. From each other, WebExtensions are sandboxed pretty well as far as I know. I guess you're safe if you stick to always manually allow the password request and of course, practise the same amount of scrutiny regarding phishing as when entering passwords manually. Or are you talking about the IPC between the browser and the KPXC app?