Andrei

The other remedy is to block the offending advertisers. This would be a right thing to do, but it would cost you (fewer erroneous ad clicks → fewer ad clicks → lower ad revenue). Google is no saint, but the choice "users vs money" is still very much yours. That's why I expected to see "we'll include that ad to our block list" instead of "you need to read carefully".

Official KeePass website: shows misleading ads with fake "Download" buttons User: clicks "Download" in one of these ads, installs malware Official KeePass support: We will filter the ads better to protect our users You need to read carefully, it was just one of those misleading ads Is it me or there is something fundamentally wrong here?

Unless the password contains a colon symbol (:), in which case iOS will mess up capitalization of pasted text.

The company behind seems like a legit French startup founded in 2017, some article mentions there 15 employees. The name choice was surely not accidental and is definitely a sleazy, unethical tactic. But legally they are in the clear: nobody has exclusive rights to the name. Dominik could push them back by registering "keepass" as a trademark early on. But today this would be a slow and expensive process.

Unfortunately, it's not that easy. Yes, the icon is similar, but KeePass' icon is covered by the project's GPL license which explicitly allows derived works. Yes, KPass violates the license by not crediting the original and not publishing the source of their icon — but this is not a clear-cut copyright violation, so Google won't intervene without legal paperwork. Which is just not worth the trouble. An easy(-ier) solution would be if the logo and/or name were registered trademarks. Both Google and...

It is compatible, so indeed related in a way. But the icon is only a tip of the iceberg, it gets much uglier.

KeePass is a Windows application. Which phone app you use?

most powerful computer imaginable Let's not forget about GPUs and ASICs. Consider we take AES-KDF and Argon2 with iteration count that makes them run 1 second on an average desktop. Calculating AES-KDF requires about 2*320 = 640 bytes of RAM. Argon2's memory is configurable, let's assume a mobile-friendly value of 32 MB. A GPU like Nvidia H100 has 80 GB of RAM. So it can simultaneously brute-force 125M keys with AES-KDF and only 2.5K with Argon2 (that's 80e9/640 vs 80e9/32e6). That is, Argon2 is...