spooky integration: suggest AppImage isolation

[llamabyte]

Hi, great great idea !

I really like this but i don't like how it integrates with tails.

Would it be possible to have it as an appimage, that way i can isolate it and still have it download the dependencies it needs (bitcoind) and run whaterver daemons it needs.

It's kind of spooky to give all these persmission and have itpop up as an integrated app alongside other native apps, including my unlocked drive. I am aware i could intall it on a fresh tails and avoid that risk, but

[BenWestgate]

Thank you for your feedback, glad to hear that you like the idea.

Regarding your concerns about the integration with Tails:
I'd like to assure you Bails does not use elevated permissions, that was a major design change from the old project. While it limited options, I felt it was the right way to go to make the software require less trust to test and be more secure to use. Your idea may be a further step in that direction.

I think users should have a dedicated Bails USB for Bitcoin stuff so installing to an existing Persistent Storage is not a priority use case, but I will try to support it on a best effort basis.

Providing Bails as an AppImage, would allow you to run it in an isolated environment and manage its dependencies. This would provide you with more control over the application's access and interactions with other parts of your system. It's only dependency besides Tails itself is Bitcoin core.

As for the application menu shortcuts and autostart, they serve important functional purposes. Bails aims to provide an easy integrated experience for new users. The application menu allows for convenient access to Bails' features, including creating and restoring codex32 seed backups, creating backup USBs, updating bitcoin core and cloning Bails for a friend.

I have another repository named bitcoin-core-on-tails that we could put a stripped down version of the bitcoin core installation script into.

Such that it doesn't do anything else and can be be distributed as a single file. Then that file can become a dependency for this project Bails, which includes the codex32-enabled wallet and guide for setting up a Persistent Storage and help for remembering the passphrase.

It seems more experienced users are having more issues with the design or scope of Bails than beginners are who are finding it quite easy to use.

[BenWestgate]

Towards closing this issue, the bails-wallet code is being refactored into a Python package, as is the codex32 backend.

After this bails should really be 1-2 executables that just do a normal application installation.

I may be able to ship bails as a flatpack package. I'm more on the system administration side than software developer so packaging software is newer to me but I'm learning.

[github-actions]

Stale issue message

[BenWestgate]

@epiccurious: Should this issue be closed?

[epiccurious]

I am aware i could intall it on a fresh tails and avoid that risk, but

The workaround is using a fresh install of Tails.

@llamabyte can you provide more context for why you want to run this in an existing Tails setup?

[github-actions]

Stale issue message

[BenWestgate]

Here's what can be identified:

He doesn't want shortcuts, autostart, he only wants bitcoin to download and write what it needs to function.

He also seems to have set an administration password to mount his internal storage.

The current master would be more convenient for him as the choose datadir dialog from Bitcoin is shown where he could have selected his internal storage. Although that would unfortunately write the wallet folders to the internal storage too. That will get fixed with #81.

This can be moved to the Bitcoin Core on Tails repository if I commit to making that project do nothing other than install bitcoin core to Tails. That will close this issue.

[BenWestgate]

@llamabyte: a work around is to install bails then disable dotfiles afterwards. This will remove the shortcuts and autostarts.

You can find the executable to run bitcoin-qt in /live/persistence/TailsData_unlocked/dotfiles/.local/bin you will have to specify the datadir every start up use: ~/Persistent/.bitcoin.