spesmilo / electrum

Electrum Bitcoin Wallet
https://electrum.org
MIT License
7.33k stars 3.05k forks source link

Clients older than 3.3.0 can no longer connect/synchronize. Users must upgrade. #5195

Open nooneknows1 opened 5 years ago

nooneknows1 commented 5 years ago

using version 3.1.3 in TAILS ...upon opening the wallet it states there has been an error...and it won't let me report it automatically. The manual error is:

Traceback
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/electrum/util.py", line 794, in run_with_except_hook
    run_original(*args2, **kwargs2)
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 985, in run
    self.wait_on_sockets()
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 967, in wait_on_sockets
    self.process_responses(interface)
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 626, in process_responses
    self.process_response(interface, response, callbacks)
  File "/usr/lib/python3/dist-packages/electrum/network.py", line 559, in process_response
    if error is None and result > 0:
TypeError: unorderable types: NoneType() > int()

Additional information
Electrum version: 3.1.3
Operating system: Linux-4.19.0-1-amd64-x86_64-with-debian-9.7
Wallet type: standard
Locale: en_US 

The wallet simply will not synch or won't connect at all.

ecdsa commented 5 years ago

Please upgrade.This is fixed in 3.3

SomberNight commented 5 years ago

Clients older than 3.3 can no longer connect to the network. Users should go to electrum.org and download the latest version of Electrum.


We have found a DOS vulnerability in them where a server can send them certain invalid data that they cannot parse and this kills the client's network thread (all networking functionality). Old clients are vulnerable to phishing messages from servers via which users kept getting tricked and losing money. To put an end to this, we've deliberately started exploiting the DOS vulnerability to make old clients unusable, hence force users to update.

It is unfortunate that this also affects Tails users, where it's not exactly easy to update. Sorry about this.

I suggest that you download the AppImage and run that. This can also be done on Tails, and is easy.

For Linux in general, see FAQ

kunsake commented 5 years ago

https://github.com/spesmilo/electrum/issues/5197

NiExTy commented 5 years ago

Can't upgrade because latest Electrum requires newer python version. It is really unfortunate that old versions were intentionally disabled.

SomberNight commented 5 years ago

@NiExTy see https://github.com/spesmilo/electrum-docs/blob/master/faq.rst#electrum-requires-recent-python-my-linux-distribution-does-not-yet-have-it-what-now

In particular, can you try using the AppImage?

NiExTy commented 5 years ago

Appimage requires 64-bit OS, so no. I will try to do 5. for now.

qctester commented 5 years ago

Clients older than 3.3 can no longer connect to the network. Users should go to electrum.org and download the latest version of Electrum.

We have found a DOS vulnerability in them where a server can send them certain invalid data that they cannot parse and this kills the client's network thread (all networking functionality). Old clients are vulnerable to phishing messages from servers via which users kept getting tricked and losing money. To put an end to this, we've deliberately started exploiting the DOS vulnerability to make old clients unusable, hence force users to update.

It is unfortunate that this also affects Tails users, where it's not exactly easy to update. Sorry about this.

I suggest that you download the AppImage and run that. This can also be done on Tails, and is easy. See FAQ

----------------------BIG BUG----------The behavior affects many users------------------------- HELP ME! Electrum 3.13 Collection, preloaded with tails-amd64-3.12.1.img, has not yet been billed. The newly requested wallet, due to the inability to connect to the server, uses the first three addresses in the client's 20 addresses. Is this a bug?Where's bitcoin? receive address(Mixed Bitcoin address):1ACPnD4mrijnEWr4Rxnr7JUPLDN4EsSsVR receive address: 1Ebx6T9r2fiv3GbXHq87QgAQy84QcnLwZz 1BTHKbnMugWZHq2rUpGL5nsPhhFnAXKDXF 1PSKUsroAjkSuG1phYAtwZFWNYuSRro4FV Send client:https://localbitcoins.com Sending time: 04/06/2019 08:05 blockstream: https://blockstream.info/tx/5dd99f63cd87abb5e0e56dda20a51914a2deb84e6d76c3360b 2bfa3f6c1fcca5?expand --------------------------------------Additional information--------------------------------------- The kind of wallet:Standard wallet The type of address:Segwit

shesek commented 5 years ago

Applying this diff (which simply wraps the vulnerable code with a try..except block) to network.py (typically at /usr/local/lib/python3.5/dist-packages/electrum/network.py or a similar location) should fix the remote networking thread crash vulnerability in Electrum v3.1.3.

pontescm commented 5 years ago

i've downloaded the latest release of Electrum 3.3.6 at https://electrum.org/#download but when it doesnt connect anyway, neither selecting manual servers nor automatic option

SomberNight commented 5 years ago

@pontescm try a few different servers and also review debug logs. If you can't figure out the issue, or if there is something interesting in your debug logs, please open a new issue and include your logs.

SadLife1 commented 5 years ago

why my message is deleted

smoki-z commented 3 years ago

я не могу перечислит деньги в тенге и отправит на карту.