0

Having an important security facility that is locally developed, tightly coupled, opaque and not optional seems like a bad idea, at least to those of us who worry about operational security.

I understand that, for many users, something is better than nothing, but forcing your KDE-grown solution on all Plasma users is NOT great security.

I have read many posts, both here on the KDE forum and on other sites across the Internet who are, at least, frustrated with Kwallet. Many try to improvise ways to disable it (null password?, etc.), but what they really seem to want is it gone. I do too.

I want to use a purpose-developed and widely used password manager with limited coupling to any particular system (OS, DE, browser, etc.). I currently use keepassxc, but I am always watching the solution space. Having another insufficient password manager installed is cluttering my system at best, and causing/allowing unsafe behavior at worst.

I recommend either eliminating Kwallet or making its installation optional.

Thank you.

You don't have to use KWallet, just ignore the request when it first starts. In other words: it already IS optional

Kwallet doesn't appear optional when I configure WiFi and my VPN.

Mamarok wrote:You don't have to use KWallet, just ignore the request when it first starts. In other words: it already IS optional

it asks you if you want to store your passwords, if you don't want to use KWallet, just answer no. Not really hard.

You can disable KWallet:
1. Go to Settings -> System Settings -> Account Details -> KDE Wallet
2. Uncheck "Enable the KDE wallet subsystem"