You can now use KeePass to manage and provide your wallet passphrase. You set up the association and stored the wallet passphrase in KeePass2.

A new entry should appear in KeePass with the name you specified in the keepassname configuration variable:Īt this point the configuration is complete.

Type: keepass setpassphrase (replace with your actual wallet passphrase):.

Step 2: Setup wallet passphrase entry in the KeePass database Keepasskey=MSb+JLygqz7ZH40SyJ1QR62iOOIXoa3tmT8SMGGI2K0= This will be used to name the entry for the wallet passphrase in KeePass. You may freely choose a value for keepassname.

Edit your nf file with the information provided.

Choose a relevant name, e.g.: testwalletassociation

KeePass will ask for a 'Key name' for the association.

Open console: Help -> Debug Window -> Console:.

Open existing database or create a new one:.

current wallet passphrase: 1BWi2OXyk76uWumxJQy4.

Keepass option is not necessary during configuration, but is necessary to retrieve the password from keepass. keepassname= Name to construct url for KeePass entry that stores the wallet passphrase

keepassid= KeePassHttp id for the established association keepasskey= KeePassHttp key for AES encrypted communication with KeePass keepassport= Connect to KeePassHttp on port (default: 19455) keepass Use KeePass 2 integration using KeePassHttp plugin (default: 0) The following new options are available for darkcoind and darkcoin-qt: Please note that the standard RPC commands walletpassphrasechange and the wallet encrption from the QT GUI already send the updates to KeePassHttp, so this is only necessary for manual manipulation of the password. This should match the passphrase you intend to use for the wallet.

keepass setpassphrase : Updates the passphrase in KeePassHttp to a new value.

Returns the association and the base64 encoded string for the AES key. This will trigger KeePass to ask for an Id for the association.

keepass init: Sets up the association between Darkcoin and KeePass by generating an AES key and sending an association message to KeePassHttp.

This is only necessary for manual configuration.

keepass genkey: Generates a base64 encoded 256 bit AES key that can be used for the communication with KeePassHttp.

The following keepass RPC commands are available in the Darkcoin client console or server:

Keepass manual