Project

General

Profile

Feature #16565

Mention Electrum updates on the doc/known issues page

Added by emmapeel 5 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
03/16/2019
Due date:
% Done:

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:
Electrum

Description

Users are sending many emails to frontdesk about electrum not being updated or unoperative, and we have also some reports here in the bugtracker

But there is no mention of this situation on our Electrum page, or our docs. In fact many users mail to support saying "they didn't find anything on the documentation'.

Maybe we could post something related to this, specially if we take a decision regarding #16564

I assign to sajolida for triaging and deciding what to do


Related issues

Related to Tails - Bug #16564: Consider shipping Electrum as an AppImage Resolved 03/15/2019
Related to Tails - Bug #16421: Electrum Phishing Attack - Upstream Fix Committed Confirmed 02/05/2019

Associated revisions

Revision 33223686
Added by CyrilBrulebois 5 months ago

Merge branch 'web/release-3.13' (Fix-committed: #16470, #16565).

History

#1 Updated by emmapeel 5 months ago

  • Related to Bug #16564: Consider shipping Electrum as an AppImage added

#2 Updated by s7r 5 months ago

agreed.

we should merge this into our doc:
https://blog.thestever.net/2019/02/26/upgrading-electrum-on-tails-to-3-3-4/

I sincerely hope so we can use the AppImage model for this tool, because it's so much better for this kind of tool given what happened lately in the wild that pushed us to drastic decisions like cut off from the network pre 3.3 clients, etc.

#3 Updated by sajolida 5 months ago

  • Related to Bug #16421: Electrum Phishing Attack - Upstream Fix Committed added

#4 Updated by sajolida 5 months ago

  • Assignee changed from sajolida to emmapeel
  • QA Check set to Info Needed

Can you please help me understand what we should write about that?

I had a quick look at #16421 and understood that there was no real security issue to fix on Tails.

Maybe you can start by pasting here what you usual tell people contacting you about that.

#5 Updated by emmapeel 5 months ago

Up until now, I was telling them this, but it does not seem to be practical anymore according to #16564:

The problem is that the Debian package of electrum is not maintained. Actually Tails will have to drop Electrum support unless bugs https://bugs.debian.org/912042 & https://bugs.debian.org/912042 are fixed and Electrum enters back on Buster (the next Debian release). Tails plans to drop support of Electrum if this is not possible.

More information at https://redmine.tails.boum.org/code/issues/16204 and https://redmine.tails.boum.org/code/issues/15484

Because of sustainability of the project, Tails relays on the Debian community to get the last version of software. And the version of electrum included in Debian is not the last version.

There are two things you can do:

    Contact the developers on the Debian side. You can find the contacts on https://tracker.debian.org/ under the "maintainers" section.

    Contact the electrum team and ask them to dedicate resources to help Debian maintainers, which are all volunteers, and often out of time..

#6 Updated by emmapeel 5 months ago

  • Assignee changed from emmapeel to sajolida
  • QA Check changed from Info Needed to Dev Needed

#7 Updated by sajolida 5 months ago

  • Related to Bug #16421: Electrum Phishing Attack - Upstream Fix Committed added

#8 Updated by sajolida 5 months ago

  • Related to deleted (Bug #16421: Electrum Phishing Attack - Upstream Fix Committed)

#9 Updated by sajolida 5 months ago

  • Tracker changed from Bug to Feature
  • Status changed from New to Fix committed
  • Assignee deleted (sajolida)
  • Target version set to Tails_3.13
  • QA Check deleted (Dev Needed)

Done in 364003d9f7 and reviewed on tails-dev.

We can update this based on the output of http://lists.autistici.org/message/20190319.170700.b3b5bf1f.en.html.

#10 Updated by CyrilBrulebois 5 months ago

  • % Done changed from 0 to 100

#11 Updated by CyrilBrulebois 5 months ago

  • Status changed from Fix committed to Resolved

#12 Updated by intrigeri 5 months ago

There are two things you can do:

Contact the developers on the Debian side. You can find the contacts on https://tracker.debian.org/ under the "maintainers" section.

FYI, in general, this has more chances to do harm than good.

Also available in: Atom PDF