[Pkg-bitcoin-devel] Please package Electrum 2.5.1 for Wheezy-Backports - the existing package now throws frequent errors due to incompatibility with newly-standardized BIP62

[s7r]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Thank you Tristan for taking care of this.

In latest Bitcoin release low-S ECDSA signatures are enforced. This is
one step forward to mitigate malleability (where anyone can change a
signature of a transaction or push some data on the stack and change
the txid [sha256 hash of the transaction] without invalidating it).

I agree, Electrum 1.9.8 is obsolete and should be removed because it's
pretty much useless and vulnerable. Even seeds are incompatible. It
makes sense in Debian that we include such software (like bitcoin
related software which needs often updates) packages only for unstable
and sid repos, so that when there's a new upstream release we can have
it in sid in max. 2 weeks, and people can install from there only this
package.

Tails is a different kind of operating system as you know. In this
case we will be installing this package from sid, we're ok with that.

If you are on Debian Wheezy you can either install it from sid (it
will require --force-depends because of the python version), either
install it with pip, and have the latest version:
 sudo apt-get install python-qt4 python-pip
 sudo pip install https://download.electrum.org/Electrum-2.5.1.tar.gz




On 10/24/2015 10:17 AM, Tristan Seligmann wrote:
> On Sat, 24 Oct 2015 at 08:05 <gofixit at ruggedinbox.com 
> <mailto:gofixit at ruggedinbox.com>> wrote:
> 
> Bringing Electrum 2.5.1 to Wheezy-Backports would be an enormous 
> asset to the privacy and Bitcoin communities, and help re-affirm 
> Debian's mission in making free and effective software available
> to all, especially to those who need it most.
> 
> 
> Electrum 2.5.1 is not eligible for wheezy-backports, so I guess you
> meant wheezy-backports-sloppy (which it would be eligible for, once
> it transitions to testing); I will take a look at doing such a 
> backport once it transitions. Based on the discussion on the Tails 
> Trac that you linked, it looks like there shouldn't be many 
> obstacles to this.
> 
> On a side note, I do have to question the wisdom of trying to keep 
> up with the Bitcoin network on an operating system released more 
> than 2 years ago; while I appreciate that it is difficult for a 
> project like Tails to update quickly, I don't think it really
> makes sense to rely on backports of fast-moving software in lieu
> of updating to newer Debian releases.
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBCAAGBQJWK0hSAAoJEIN/pSyBJlsReVcH/iNQZMfElXNhgwy24ckBYb2/
fYjlmxlaPyXB4P+zSp7gUSc1ZFP7tpH0Fh6ANkOdYcyLo0Tkck6UbgecDwu3wx5d
H3oJ+G8/g1o8cwKkr5I8FvCT7rDO0q1I7Q8h3Msw4COWaWOzqbPxN6TjUaGrPBSp
896NOMBn+d6Zap+93FH/a5HknTqIwLrGjv4puox9EjwmamRT+5Zf13zSnFTM+pSg
9D6f7VHuy0QVM7GOADxRR0VIYXjHUlzkevnGuDvD47XBhbYrXZVW2DY43erVGbXt
m96asxc+W+/IJuDlvb1yFSC/SxGCq9y+5GX8r0ZIx65UH3W1W+iQeBTa/7ck9Yw=
=jo8E
-----END PGP SIGNATURE-----