<p>Clearly your receiving addresses, your sending addresses and their associated aliases are readily available without the passphrase to your wallet as they are visible upon opening the Bitcoin client without entering the passphrase. </p>

<p>It's perhaps also worth noting that even if your wallet is encrypted, a successful attacker who has a copy of your wallet could install a keystroke logger to obtain your passphrase. </p>

<p>This would seem more likely to happen when your computer is compromised through installing a trojan etc than if someone physically found say a lost notebook PC (for which the attacker would need to install the keystroke-logging software &amp; remote access software, and then give you your computer back so you would type in the passphrase next time you wanted to send coins!)</p>

<p>Sorry, I don't know where the sending and receiving address descriptions are stored, so I don't know how to protect them - hopefully someone else can answer that.</p>

CC BY-SA 3.0
2011-12-06T02:13:58.753Z
Updated the question to show that people can find wallet.dat without getting to the computer itself. +1 for pointing that out.
Thilo
CC BY-SA 3.0
2011-12-06T06:04:03.730Z
They are stored in wallet.dat, so putting that file in a Truecrypt volume could be a step towards securing them.
Meni Rosenfeld
CC BY-SA 3.0
2011-12-06T01:48:40.887Z
2011-12-06T01:48:40.887Z
Highly Irregular
<p>Bitcoin wallet encryption makes sure (by encrypting the private keys with a passphrase) that someone who finds your computer or your Dropbox or your backup drive (including wallet.dat) cannot spend your coins.</p>

<p>Does this also protect my receiving addresses (which I may not want to be associated with to protect my pseudonymity, and finding them in my wallet would remove plausible deniability)? And how about the aliases I have associated to sending addresses, which might breach confidentiality with my business partners?</p>

<p>If not, what additional steps do I need to take?</p>

CC BY-SA 3.0
2011-12-06T05:04:53.753Z
Probably related: http://bitcoin.stackexchange.com/questions/2150/where-are-the-receiving-and-sending-address-descriptions-stored
Thilo
<wallet><privacy><encryption>
Does Bitcoin wallet encryption also protect my sending and receiving addresses?
Thilo
# Does Bitcoin wallet encryption also protect my sending and receiving addresses?

(Asked by: username_0 on 2011-12-06)

Bitcoin wallet encryption makes sure (by encrypting the private keys with a passphrase) that someone who finds your computer or your Dropbox or your backup drive (including wallet.dat) cannot spend your coins.

Does this also protect my receiving addresses (which I may not want to be associated with to protect my pseudonymity, and finding them in my wallet would remove plausible deniability)? And how about the aliases I have associated to sending addresses, which might breach confidentiality with my business partners?

If not, what additional steps do I need to take?

**Tags:** wallet, privacy, encryption

> **Comments:**
> **username_0**: Probably related: http://bitcoin.stackexchange.com/questions/2150/where-are-the-receiving-and-sending-address-descriptions-stored  

---

## 1 answers

### Answer by username_1 on 2011-12-06. Score: 2

Clearly your receiving addresses, your sending addresses and their associated aliases are readily available without the passphrase to your wallet as they are visible upon opening the Bitcoin client without entering the passphrase.

It's perhaps also worth noting that even if your wallet is encrypted, a successful attacker who has a copy of your wallet could install a keystroke logger to obtain your passphrase.

This would seem more likely to happen when your computer is compromised through installing a trojan etc than if someone physically found say a lost notebook PC (for which the attacker would need to install the keystroke-logging software & remote access software, and then give you your computer back so you would type in the passphrase next time you wanted to send coins!)

Sorry, I don't know where the sending and receiving address descriptions are stored, so I don't know how to protect them - hopefully someone else can answer that.

> **Comments:**
> **username_0**: Updated the question to show that people can find wallet.dat without getting to the computer itself. +1 for pointing that out.  
> **username_2**: They are stored in wallet.dat, so putting that file in a Truecrypt volume could be a step towards securing them.  

---

