pull down to refresh
Thank you!
After that fiasco as you said, I think old school still solid as rock for many things.
By default persistent partition is not enabled/configured. To store config and wallets you have to configure the partition manually and enable dotfiles.
You can also have another storage device which you can mount as /home/amensia and have all your configuration even in a LUKS or Veracrypt/Truecrypt partition or file.
Do you think persistence for e.g. wallets would be a good default to have?
Is there any security or operational issue with having the seed / wallets stored in persistent that you can think of? What about even having passphrase etc on there too (textfile?)?
My understanding is passphrase is designed for a cold card or evil maid scenario where the seed is compromised, but if the tailsOS is behind a long encrypted partition password already, can it be stored in plaintext or a password manager on the device do you think? Or is my security thinking wrong here?
All depends people's needs. Security level is not the same for all. What I mean with that is that to me, LUKS2 (Tail's persistent partition) is safe to me with strong password for example. Normally tools like Sparrow save the data in a encrypted file, so never plaintext.
If you want to store something important, you can go and use another device for that, but if you still need to use same storage device and persistent partition, I would go for KeepassXC/Secrets software that Tails includes.
You are right with your security thinking. You can store in plaintext (I would avoid that) or password manager (Best option) feeling safe with a strong password in the encrypted partition.
But as I said; Security level is not the same for all, and I do not want to recommend a setup to store seeds/secrets... But better always offline and in a non-electronic device.
Regards
Cool, I did know know there was a secrets app in tails, will check it out.
Well done! I look forward to exploring more closely and verifying what you have made here.
With the whole Coldcard fiasco, I am reevaluating cold storage options and have been exploring TailsOS as a potential solution among many.
Tails gives a few benefits: Being able to enter a passphrase and manage wallets and files in a full desktop environment is much easier with a full keyboard etc.
For Tails I really wanted to be able to use Sparrow. Electrum is iconic, but it is just not the right tool for me in this case for a few reasons (Not really designed for BIP39 seedphrases etc).
I worked out how to get Sparrow working in Tails persistently by setting up a sparrow.desktop launcher file in the dotfiles directory and pointing it to the extracted tarball, but the issue was how to get the config and wallets to persist between reboots.
I ended up using the -d flag in the launcher to point to its own folder in amnesia/Persistent that makes it clean and simple.
@DesobedienteTec If this project is not using persistent storage, how does it handle storing the config and wallets for Sparrow? Where do they live? Or do you need to keep them on a seperate storage device etc?