Pages:
Author

Topic: Encrypt the PSBT file - page 2. (Read 394 times)

legendary
Activity: 2268
Merit: 18586
October 02, 2021, 05:00:07 AM
#11
If they decide to ask email or SMS as verification, your only option is either perform the verification or upgrade to paid plan using Bitcoin.
Then I could buy a pre-paid SIM card for a dollar anonymously using cash for the sole purpose of receiving this SMS verification. Or try various disposable email address for verification. Or I could email them and directly request an invite, since the only reason they require verification is to prevent spammers, and it's highly unlikely a spammer is going to email them directly for the purpose of opening a single account. Or I just pay the $5 to open a Plus account for a month, not a big deal.

Although if you are going to encrypt the PSBT before uploading it, you don't even need to use ProtonMail - just host it somewhere you can access via Tor and it won't get deleted. Open a GitHub account and stick it on there. You could probably open a topic on the Archival board here and stick it there. Message it to yourself using an encrypted communication app like Signal. There are multiple possibilities.
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
October 01, 2021, 09:30:11 AM
#10
Slightly off-topic, but there are ways to create gmail accounts anonymously. It's a bit harder and well, gmail is owned by Google. But it can be done and then forever accessed through Tor so gmail never has your ip address, except maybe the first time (so the first time, when it is created, you have to do it from some public wifi hotspot or coffee shop or mall.)

You can then use those gmail accounts to maybe sign up for protonmail, maybe? I've only had to make one protonmail account and I don't even use it.

I find it's much easier to hide as a normal looking sheep with the other 1 billion users of gmail.

Crossing international borders is always a risk. I find that the officers don't normally take too much interest in phones or cameras, and sometimes even laptops. As long as you keep all of those devices off and encrypted, they're usually not going to bother. You can also just tape a microsd card to your device without actually inserting it? That way you can "smuggle" up to 1 terabyte of data without anyone knowing.

But, like implied, that might be a hassle for the OP to do.
hero member
Activity: 882
Merit: 5818
not your keys, not your coins!
September 28, 2021, 05:05:35 PM
#9
In general you don't want governments or just anyone to know you are transacting in Bitcoin and PSBT shows you are in.

PSBT file is relative small, you could always hide it inside regular file (e.g. png or docx).
I really love this idea! It's quite easily possible to store whole papers in jpegs with minimal modification of the look of the image when opened in an image viewer.

Here's an online tool to try Steganography.

From https://en.wikipedia.org/wiki/Steganography, very impressive:


According to https://protonmail.com/support/knowledge-base/human-verification/, it's harder than you expected. If they decide to ask email or SMS as verification, your only option is either perform the verification or upgrade to paid plan using Bitcoin.
That's correct, I tried to create a Protonmail account via Tor Browser a few times already and compared to accessing the site over clearnet, it asks for verification using Email, SMS or payment.
legendary
Activity: 4298
Merit: 3209
September 27, 2021, 07:58:10 PM
#8
Is there something about the structure of a PSBT that would benefit more from including encryption in the protocol over encrypting the PSBT in a transmission layer?
legendary
Activity: 2268
Merit: 18586
September 27, 2021, 03:09:51 PM
#7
The problem is linking this data to you.
I agree, which is why I said to use an anonymous account to store it.

As far as cloud storage. All of these "anonymous email" services aren't really anonymous. And "anonymous cloud services" require that you dox yourself via paying a subscription usually. You would to find one that accepts BTC and mix the coins and hope it all goes well.
I could use Tor to sign up to a brand new ProtonMail account, and then upload an encrypted PSBT and save it as a draft. When I arrive at my destination, I use Tor to access the ProtonMail account, download and then decrypt the PSBT.

I haven't found any reasonable way to store stuff in the cloud and call it "safe".
Again, I completely agree, and would never advocate storing any sensitive data online in any manner. But the goal here is not "prevent all access to this data" (which is near impossible to achieve once you upload something to any cloud storage or similar), but rather "prevent this data from being linked to me", which is far more realistic.
sr. member
Activity: 297
Merit: 424
September 27, 2021, 02:11:34 PM
#6
Carrying the PSBT file throught a border and then getting the laptop checked in customs for instance.
Then don't carry it through customs. As achow has said, it is going to be publicly viewable to the entire world once you broadcast it, so you can store it on the cloud, email it to someone else or yourself, post it on a blog, any method of digital storage which you can access later once you arrive at your destination. If you do all this with a brand new and otherwise anonymous cloud/email/whatever account, then there is minimal additional risk to your privacy.

I've heard stories of people getting their laptops confiscated if they had full disk encryption and refuse to deliver a password.
If border agents are interested enough in you to force you to decrypt your entire disk, then they are going to be interested enough in individual encrypted files or containers to force you to decrypt them too. If you really want to hide something from border agents, then don't take it across the border with you. If you must, then a hidden volume with some "decoy" encrypted data is probably the way to do it, which is far outside the scope of Bitcoin Core.

I can't agree with this logic of "the entire world will know". The entire world will know X transaction happened but not that it's tied to you. The problem is linking this data to you. It's the basic pseudonymous principle of making transactions in Bitcoin. So if for instance you save a .psbt file in an usb pendrive and you forget to delete it, and someone gets access to the USB physically and manages to tie this USB pendrive to you, then they would know you are an owner of bitcoins. So you have now become a target.
But assuming this will remain as it is then you'll just have to guarantee that the file is put inside a Veracrypt container or something before it leaves your airgapped laptop.
As far as cloud storage. All of these "anonymous email" services aren't really anonymous. And "anonymous cloud services" require that you dox yourself via paying a subscription usually. You would to find one that accepts BTC and mix the coins and hope it all goes well. There's also the problem that you never know what happens with this data if you don't control the servers physically. I haven't found any reasonable way to store stuff in the cloud and call it "safe".


Carrying the PSBT file throught a border and then getting the laptop checked in customs for instance.
Wallet software is way more obvious than a PSBT. And wallet software will contain far more private information than a PSBT.

PSBTs are just base64 strings, you wouldn't know that it is Bitcoin related unless you are looking for it specifically.

And again, you can just encrypt the PSBT with a third party tool. Then it will look like an encrypted file, instead of specifically an encrypted PSBT as adding an encryption standard would make.

I have always wondered why the wallet.dat is not fully encrypted, but in any case you wouldn't move the wallet.dat file around to sign between computers as you would with the PSBT ones. Of course it's the same thing: never move the wallet.dat file around if it's not fully encrypted with a third party software.
staff
Activity: 3374
Merit: 6530
Just writing some code
September 27, 2021, 02:00:35 PM
#5
Carrying the PSBT file throught a border and then getting the laptop checked in customs for instance.
Wallet software is way more obvious than a PSBT. And wallet software will contain far more private information than a PSBT.

PSBTs are just base64 strings, you wouldn't know that it is Bitcoin related unless you are looking for it specifically.

And again, you can just encrypt the PSBT with a third party tool. Then it will look like an encrypted file, instead of specifically an encrypted PSBT as adding an encryption standard would make.
legendary
Activity: 2268
Merit: 18586
September 27, 2021, 01:01:58 PM
#4
Carrying the PSBT file throught a border and then getting the laptop checked in customs for instance.
Then don't carry it through customs. As achow has said, it is going to be publicly viewable to the entire world once you broadcast it, so you can store it on the cloud, email it to someone else or yourself, post it on a blog, any method of digital storage which you can access later once you arrive at your destination. If you do all this with a brand new and otherwise anonymous cloud/email/whatever account, then there is minimal additional risk to your privacy.

I've heard stories of people getting their laptops confiscated if they had full disk encryption and refuse to deliver a password.
If border agents are interested enough in you to force you to decrypt your entire disk, then they are going to be interested enough in individual encrypted files or containers to force you to decrypt them too. If you really want to hide something from border agents, then don't take it across the border with you. If you must, then a hidden volume with some "decoy" encrypted data is probably the way to do it, which is far outside the scope of Bitcoin Core.
sr. member
Activity: 297
Merit: 424
September 27, 2021, 12:14:36 PM
#3
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.
staff
Activity: 3374
Merit: 6530
Just writing some code
September 27, 2021, 12:06:08 PM
#2
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.
sr. member
Activity: 297
Merit: 424
September 27, 2021, 11:57:44 AM
#1
I was testing offline transactions via PSBT and realized that the PSBT file can be decoded using this program:

https://github.com/achow101/psbt-decoder

Then it's plaintext that contains personal information about the transaction.

Code:
% psbt_dump data/worked-7.psbt

976 bytes in PSBT: data/worked-7.psbt
-- HEADER --

psbt 0xff

-- GLOBALS --

  key: 00  (GLOBAL_UNSIGNED_TX)
value:

020000000258e87a21b56daf0c23be8e7070456c336f7cbaa5c8757924f545887bb2abdd750000000000ffffffff838d0427d0ec650a68aa46bb0b098aea4422c071b2ca78352a077959d07cea1d0100000000ffffffff0270aaf00800000000160014d85c2b71d0060b09c9886aeb815e50991dda124d00e1f5050000000016001400aea9a2e5f0f876a588df5546e8742d1d87008f00000000  (154 bytes)

 Transaction: (2 inputs, 2 outputs, 0 witness)
            : txid 82efd652d7ab1197f01a5f4d9a30cb4c68bb79ab6fec58dfa1bf112291d1617b
   [in #0 ] (not signed)
            from 75ddabb27b8845f5247975c8a5ba7c6f336c4570708ebe230caf6db5217ae858 : 0
   [in #1 ] (not signed)
            from 1dea7cd05979072a3578cab271c02244ea8a090bbb46aa680a65ecd027048d83 : 1
  [out #0 ] tb1qmpwzkuwsqc9snjvgdt4czhjsnywa5yjdzglap9
  [out #1 ] tb1qqzh2ngh97ru8dfvgma25d6r595wcwqy06sqc03


-- INPUT #0 --

  key: 00  (IN_NON_WITNESS_UTXO)
value:

0200000001aad73931018bd25f84ae400b68848be09db706eac2ac18298babee71ab656f8b0000000048473044022058f6fc7c6a33e1b31548d481c826c015bd30135aad42cd67790dab66d2ad243b02204a1ced2604c6735b6393e5b41691dd78b00f0c5942fb9f751856faa938157dba01feffffff0280f0fa020000000017a9140fb9463421696b82c833af241c78c17ddbde493487d0f20a270100000017a91429ca74f8a08f81999428185c97b5d852e4063f618765000000  (187 bytes)

 Transaction: (1 inputs, 2 outputs, 0 witness)
            : txid 75ddabb27b8845f5247975c8a5ba7c6f336c4570708ebe230caf6db5217ae858
   [in #0 ] (unknown)
  [out #0 ] 2MtgN5EvHUm2kNVvqKgqsZ9v2fGH3jCpXVF
  [out #1 ] 2Mw4CE6tUQ7Ak9Zf9TKujgzbVjDZqgRbUVP



  key: 07  (IN_FINAL_SCRIPTSIG)
value:

00473044022074018ad4180097b873323c0015720b3684cc8123891048e7dbcd9b55ad679c99022073d369b740e3eb53dcefa33823c8070514ca55a7dd9544f157c167913261118c01483045022100f61038b308dc1da865a34852746f015772934208c6d24454393cd99bdf2217770220056e675a675a6d0a02b85b14e5e29074d8a25a9b5760bea2816f661910a006ea01475221029583bf39ae0a609747ad199addd634fa6108559d6c5cd39b4c2183f1ab96e07f2102dab61ff49a14db6a7d02b0cd1fbb78fc4b18312b5b4e54dae4dba2fbfef536d752ae  (218 bytes)

-- INPUT #1 --

  key: 01  (IN_WITNESS_UTXO)
value:

00c2eb0b0000000017a914b7f5faf40e3d40a5a459b1db3535f2b72fa921e887  (32 bytes)


  key: 07  (IN_FINAL_SCRIPTSIG)
value:

2200208c2353173743b595dfb4a07b72ba8e42e3797da74e87fe7d9d7497e3b2028903  (35 bytes)


  key: 08  (IN_FINAL_SCRIPTWITNESS)
value:

0400473044022062eb7a556107a7c73f45ac4ab5a1dddf6f7075fb1275969a7f383efff784bcb202200c05dbb7470dbf2f08557dd356c7325c1ed30913e996cd3840945db12228da5f01473044022065f45ba5998b59a27ffe1a7bed016af1f1f90d54b3aa8f7450aa5f56a25103bd02207f724703ad1edb96680b284b56d4ffcb88f7fb759eabbe08aa30f29b851383d20147522103089dc10c7ac6db54f91329af617333db388cead0c231f723379d1b99030b02dc21023add904f3d6dcf59ddb906b0dee23529b7ffb9ed50e5e86151926860221f0e7352ae  (218 bytes)

-- OUTPUT #0 --

  key: 02 03a9a4c37f5996d3aa25dbac6b570af0650394492942460b354753ed9eeca58771 (OUT_BIP32_DERIVATION, 34 bytes)
value:

d90c6a4f000000800000008004000080  (16 bytes)

    Address: 03a9a4c37f5996d3aa25dbac6b570af0650394492942460b354753ed9eeca58771 (33 bytes)
             = n1ExfZ1rECtYdzfBHoeYtAWzTURXsdSVkb
    HD Path: (m=0x4f6a0cd9)/0'/0'/4'


-- OUTPUT #1 --

  key: 02 027f6399757d2eff55a136ad02c684b1838b6556e5f1b6b34282a94b6b50051096 (OUT_BIP32_DERIVATION, 34 bytes)
value:

d90c6a4f000000800000008005000080  (16 bytes)

    Address: 027f6399757d2eff55a136ad02c684b1838b6556e5f1b6b34282a94b6b50051096 (33 bytes)
             = mfaZXpvjGrisYP1rW2wL2YBHJt22sCoX53
    HD Path: (m=0x4f6a0cd9)/0'/0'/5'


-- EXPECT EOF --
-- ACTUAL EOF --


If an attacker gets this, it wouldn't be nice. In order to maintain privacy, I suggest that the PSBT files can optionally be encrypted. It would prompt for a password, once entered the PSBT file is saved encrypted. As you load it on the other computer, it asks for the password. This way you wouldn't be paranoid that a man in the middle attack can be performed to steal the contents of the PSBT.
Pages:
Jump to: