User:Minshy99/sandbox

KDE Wallet manager (KWallet) is free and open source password management software written in C++ for UNIX-style operating systems. KDE Wallet Manager runs on Linux-based OS and It's main feature is storing encrypted passwords in KDE Wallets.

Installation
KDE Wallet Manager (KWallet) requires Linux-based OS and the KDE Software Compilation desktop environment such as Kubuntu.

Browser extensions
KDE Wallet manager (KWallet) can be integrated with various web browsers inluding Chrome, Firefox, Opera, and Edge.

Standalone addon is also available in Firefox. This addon allows user to store passwords internally through KDE Wallet manager (KWallet) instead of default Firefox password manager.

Konqueror, the official web browser of the K Desktop Environment (KDE) features KDE Wallet manager (KWallet) to store sensitive passwords encrypted.

API
KDE Wallet Manager’s APIs trigger authentication events when the application makes a request through Desktop Communications protocol (DCOP), which is KDE’s primary interprocess communication (IPC) mechanism, which causes a password dialog box to be displayed for the application. This causes the password dialog box to be launched by the KDE daemon process. User can choose either to cancel the dialog box which will terminate the application or to fill the password box in. If password box is filled, the Wallet will automatically open. KDE Wallet Manager’s Desktop communications protocol (DCOP) can only be accessed locally because it is an interpocess communication (IPC) protocol that is processed over UNIX local sockets.

GUI
On KDE Wallet Manager’s GUI, user can manage every Wallets and passwords assigned to them.

KDE Wallet Manager allows user to save or delete Wallets and user can identify which wallet applications should look in when attempting to access a stored password.

Wallets
The Wallet is a term of password storage used in KDE Wallet Manager software. Wallets can be created manually by user or It is offered by dialogue when user enters in password on any KDE desktop environment or websites. Once created, Wallet can store various passwords and It is controlled by one master password. This way users do not have to remember various passwords, instead they can just manage them by memorizing one master password for the wallet. The default Wallet is named “kdewallet” and users can create more of their own if needed.

Encryption of the password
The data stored by KDE Wallet manager can be encrypted in two major ways. The GNU Privacy Guard (GnuPG or GPG) algorithm is used if GnuPC Made Easy library is installed on the user’s Linux-based OS. If not, Blowfish symmetric block cipher algorithm is used.

Blowfish symmetric block cipher algorithm
KDE Wallet manager encrypts the data stored in wallet using the Blowfish symmetric block cipher algorithm in CBC mode. To protect the user’s information, blowfish encrypted data is authenticated with SHA-1 hashing algorithm.

KDE Wallet manager’s blowfish encryption provides faster encryption compared to Khufu, RC5, DES, IDEA, Trip-DES. Blowfish encrypts at a rate of 18 clock cycles per byte in 32-bit microprocesses.

KDE Wallet manager’s Blowfish algorithm can be executed in memory within 5k, and a simple structure is easy to implement and easy to determine the strength of the algorithm. The algorithm is variable in key length, which can be long as 448 bites and it allows basic word addition and bit XOR operations.

GNU Privacy Guard encryption
User can create a GNU Privacy Guard (GnuPG or GPG) based wallet to store extra sensitive passwords. This requires users to install GnuPG Made Easy library. If the library is installed and once the software found GNU Privacy Guard (GnuPG or GPG), users will be asked to choose a key to use for a new wallet.

Vulnerabilities

 * SHA-1 hash function that is used in KDE Wallet manager (KWallet) is cryptographically broken. Google and CWI Amsterdam have proved that two identical SHA-1 digest displays two different PDF content. Various Companies including Microsoft has discontinued SHA-1 supports however KDE Wallet manager (KWallet) uses SHA512 in versions higher than 4.13 or with Pluggable authentication module or it uses SHA-1 hash function.
 * "kwallet-pam in KDE KWallet before 5.12.6 allows local users to obtain ownership of arbitrary files via a symlink attack."
 * "fishProtocol::establishConnection in fish/fish.cpp in KDE kio-extras through 20.04.0 makes a cacheAuthentication call even if the user had not set the keepPassword option. This may lead to unintended KWallet storage of a password."
 * "kwalletd in KWallet before KDE Applications 14.12.0 uses Blowfish with ECB mode instead of CBC mode when encrypting the password store, which makes it easier for attackers to guess passwords via a codebook attack."