Today we are announcing the release of our first Audit Report conducted by an independent security consultant: https://keepassxc.org/blog/2023-04-15-audit-report/
Today we are announcing the release of our first Audit Report conducted by an independent security consultant: https://keepassxc.org/blog/2023-04-15-audit-report/ 17 comments
@keepassxc the audit report links seems to be linked to localhost, implying the site was probably generated in development mode @keepassxc the download link for the audit report links to 127.0.0.1 - could you please update the blog post? @keepassxc great to see this! I'll keep recommendeding KeepassXC to people (after i read the report ofc) @keepassxc When will there be a mobile app on F-Droid? @jfmblinux while waiting for that, the pendent I currently use is KeepassDX: https://f-droid.org/packages/com.kunzisoft.keepass.libre/ @keepassxc @IzzyOnDroid was genau ist denn der Unterschied zwischen der erwähnten App von dir und Keepass2Android? Oder gibt's da keinen nennenswerten Unterschied? @kranzkrone Musst Du Dir anschauen; da ich die von Dir genannte nicht selbst nutze oder genutzt habe, kann ich das nicht sagen (müsste also genau so die Beschreibungen vergleichen). @jfmblinux @keepassxc > select at least 2048 MiB The memory recommendation is a bit too high, imo. I've tried previously with 2048 MiB (threads ~2, transform round was higher) on my laptop with 8 gigs of ram/dual core. It takes a significant amount of time to open and the application freezes. On mobile (4gb/octa core) it just times out. These aren't very old or low spec-ed devices. @keepassxc As these numbers are going to be different for everyone according to their specs, I think it is better to mention the formula that keepass recommends min(M/2, 1 GiB). The thread count will also vary, similarly. Too high parameters can lead to an issue where the application freezes while unlocking but you need to unlock the database to reduce them. |
@keepassxc Congrats!