Quote from: achow101 on Today at 04:06:08 PM

Almost all of the information contained in the PSBT is (or will be) public information. UTXOs are public, signatures are public, txids and vouts are public. The only thing that is not public are the BIP 32 derivation paths, and those aren't particularly useful to an attacker.

What "personal information" are you concerned about? What is the attack you are concerned about? If you are transmitting PSBTs over the internet, then you can employ third party tools for encryption, such as PGP. If you are concerned about a man in the middle between local machines, then you are concerned about an attacker who has gained remote access to your machines, in which case you have much bigger problems.

Carrying the PSBT file throught a border and then getting the laptop checked in customs for instance. I've heard stories of people getting their laptops confiscated if they had full disk encryption and refuse to deliver a password. In general you don't want governments or just anyone to know you are transacting in Bitcoin and PSBT shows you are in.

I guess you can always put the file inside an encrypted container. I just would like a minimalistic setup where the entire process is done with Bitcoin Core and you don't need to install anything else to store encrypted data.