Not an official requirement.
It cannot be brushed away with “yes backport”.
Dev/APT Pinning is an issue which can break APT for all users.
Not an official requirement.
It cannot be brushed away with “yes backport”.
Dev/APT Pinning is an issue which can break APT for all users.
I don’t think Electrum “goes through all the requirements of the Whonix project like a hot knife through butter”. From the discussions I’ve been part of, the decision about whether or not a particular application is suitable for inclusion in Whonix by default or not usually has a lot of thought put into it, with discussions like this one. Granted, most of the applications are already in Debian’s stable repositories, so the primary hurdle is already gone through in those instances.
Related:
| Feature | Feather Wallet | Monero GUI |
|---|---|---|
| Flatpak | Available | Available |
| Debian APT | In progress | Not available |
| AppImage | Whonix-compatible (pre-configured) | N/A |
| Whonix Support | OS detection disables built-in Tor daemon to avoid Tor-over-Tor | Not specified |
| Recommended Use | Lightweight use | Mainly for running a full node |
| Installation | Flatpak, Debian APT, or AppImage | Flatpak or AppImage |
Whonix OS detection & Tor handling & paths
feather/src/utils/os/whonix.cpp at master · feather-wallet/feather · GitHub
feather/src/utils/os/whonix.h at master · feather-wallet/feather · GitHub
feather/src/utils/TorManager.cpp at master · feather-wallet/feather · GitHub
feather/src/utils/TorManager.cpp at master · feather-wallet/feather · GitHub
Paths | Feather Wallet Documentation
Feature comparison between CLI and GUI wallets
Feature comparison | Feather Wallet Documentation
Feather seems like a clear winner to me. However I dont want discount those that use whonix to set up a full or remote node in condunction to those who do that same usage with Whonix in Qubes
Monero now finally verified on flathub.