![]() ![]() There’s a lot of things you have to type so you might want to copy and paste this into a text file and load it on a USB, so you can copy and paste certain commands back into the commandline.Ĭurrently, the running version of Electrum on Tails is insecure because it allows nodes to broadcast messages that can potentially be phishing attacks and trick users into downloading malware. So I thought I would create a blog post showing people how to do it. I see a lot of requests on reddit asking how to install the new version of Electrum on Tails. If this is a controversial move, then we can at least delay shipping the updated config until Electrum is updated via stretch-backports.Upgrading electrum on tails to 3.3.4 Februat 7:52 am | Posted in Uncategorized | 139 Comments I wasn’t trying to add cutting edge features, but rather I was trying to clean up the config file which requires Electrum 3.1.1. Again, I don’t see “missing cutting edge features” = “bug”. ![]() > When there’s a bug or regression that makes the version shipped in Tails useless, the new Electrum version that fixes is will be in stable-backports so we should never get there. I could be wrong, but I have found backported software to significantly lag behind testing/unstable. This is more closer and in concordance to Tails ~6 weeks estimated release life. Also, every Electrum update in unstable will make it to stable-backports after the required time passes. Installing from stable-backports however ensures it is properly install-able. Installing from unstable might not be the best move. ![]() When there’s a bug or regression that makes the version shipped in Tails useless, the new Electrum version that fixes is will be in stable-backports so we should never get there. If we take this approach, we might never catch up. These will obviously be supported as they come to stable-backports, but until then users that want cutting edge features should take some time to install themselves the preferred version that support them. It is not mandatory to support all cutting edge features of this wallet and support each and every hardware wallet, to its last version. should not have security bugs, or other severe bugs which could affect user’s funds or security should be fully usuable (send, receive, sync with the network) We go for the idea that Electrum is to be shipped with Tails and: ![]() Then users who want to use Electrum will need to add it to their list of ASP and they’ll have the same UX as currently, except they’ll always be running the latest version (from the Debian dist our APT pinning prefers, which one is best can be discussed from a different perspective once it’s not about a version that’s frozen in an ISO) as you say they should be.
0 Comments
Leave a Reply. |