KDE Wallet Manager: Difference between revisions

Latest revision as of 15:23, 6 August 2018

Other languages:

KWalletManager manages some of your passwords in an encrypted file - but Kgpg does not use Kwallet, neither does firefox.

KWalletManager is an optional tool which can greatly assist your work-flow while maintaining security.

Wallets are encrypted against your chosen passphrase
Wallets are, by default, closed. Your passphrase is required to open a wallet
Wallets can be configured to close when unused
You control which applications may use the wallet - everything else will have to ask you for a password.

A right-click, context menu on the wallet in kwalletmanager offers maintenance options:

To create a new wallet
To open and examine the selected wallet
To change the passphrase for that wallet
To disconnect an application currently using that wallet
To close or delete the wallet

Clicking (or in some versions, double-clicking) on a wallet allows you to examine the contents of a wallet. From here you can remove any entries that you do not wish to be further controlled by the wallet. A further advantage is that it is possible to examine the passwords for individual entries - particularly useful if you have mis-typed a password and stored it. These activities remain secure, since they are only available after you have given the passphrase.

Tip

For greater security configure KWalletManager to use one wallet for local passwords and a separate one for network passwords and form data.

Some apps, e.g. octopi, offer multiple options for password entry, e.g. gksu besides kdesu. gksu then offers to store a password, say the root password, in the gnome-keyring to save you the bother of repeated entering of the password in short intervals of time. That gnome keyring is a "wallet" separate from the KDE-wallet. Another separate "wallet" is the file /etc/passwd for login passwords into Gnu/Linux.

Hints and Tips

How to make an application start using KDE Wallet Manager

Open KDE Wallet Manager, and go to Settings -> Configure Wallet... -> Access Control, and there adjust application settings. Useful if you mistakenly told an application not to use KDE Wallet Manager.

Use KDE-wallet with Python in a CLI: CLI.

@@ Line 2: / Line 2: @@
 <translate>
+<!--T:1-->
 {|class="tablecenter vertical-centered"
-|[[Image:Kwalletmgr.png|250px]]||&nbsp;||'''KWalletManager manages all your passwords in an encrypted file'''
+|[[Image:Kwalletmgr.png|250px]]||&nbsp;||'''KWalletManager manages some of your passwords in an encrypted file - but Kgpg does not use Kwallet, neither does firefox.'''
 |}
+<!--T:2-->
 '''KWalletManager''' is an optional tool which can greatly assist your work-flow while maintaining security.
 * ''Wallets'' are encrypted against your chosen passphrase
@@ Line 12: / Line 14: @@
 * You control which applications may use the wallet - everything else will have to ask you for a password.
+<!--T:3-->
 A right-click, context menu on the wallet in '''kwalletmanager''' offers maintenance options:
 * To create a new wallet
@@ Line 19: / Line 22: @@
 * To close or delete the wallet
+<!--T:4-->
 Clicking (or in some versions, double-clicking) on a wallet allows you to examine the contents of a wallet.  From here you can remove any entries that you do not wish to be further controlled by the wallet.  A further advantage is that it is possible to examine the passwords for individual entries - particularly useful if you have mis-typed a password and stored it.  These activities remain secure, since they are only available after you have given the passphrase.
+<!--T:5-->
+{{Tip|1=''For greater security'' configure '''KWalletManager''' to use one wallet for local passwords and a separate one for network passwords and form data.
+----
+Some apps, e.g. ''octopi'', offer multiple options for password entry, e.g. ''gksu'' besides kdesu. gksu then offers to store a password, say the root password, in the gnome-keyring to save you the bother of repeated entering of the password in short intervals of time. That gnome keyring is a "wallet" separate from the KDE-wallet. Another separate "wallet" is the file /etc/passwd for login passwords into Gnu/Linux.
+}}
+== Hints and Tips == <!--T:7-->
-==FAQs, Hints and Tips==
+=== How to make an application start using KDE Wallet Manager === <!--T:8-->
-{{Tip|1=''For greater security'' configure '''KWalletManager''' to use one wallet for local passwords and a separate one for network passwords and form data.}}
+<!--T:9-->
+Open '''KDE Wallet Manager''', and go to <menuchoice>Settings -> Configure Wallet... -> Access Control</menuchoice>, and there adjust application settings. Useful if you mistakenly told an application not to use '''KDE Wallet Manager'''.
+<!--T:10-->
+Use KDE-wallet with Python in a CLI: [http://www.mirbsd.org/kwalletcli.htm#b_pyex CLI].
+<!--T:6-->
 [[Category:Utilities]]
 [[Category:Security]]
 </translate>