Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Electrum 0 balance bug/vulnerability #1575

Closed
treodu opened this issue Dec 9, 2015 · 2 comments
Closed

Electrum 0 balance bug/vulnerability #1575

treodu opened this issue Dec 9, 2015 · 2 comments

Comments

@treodu
Copy link

treodu commented Dec 9, 2015

Is electrum still a safe client to store/recieve/send bitcoins? I have discovered an electrum bug but i find it hard to believe im the only one - im technically savy but not a programmer who may try things that stress the code electrum is built on such as #1525 but none the less i seem to have uncovered this new/undiscovered weaknesses/bug in this 4yr old software - i have not found any identically similar problems anywhere on the web (onion network nor open web) - under persumption bug-reporting from scratch may be needed i furnish all relevant background, specs, and bug descriptions for review. .If any further information is needed to duplicate and resolve this bug please email me - i will promptlu provide.

Problem specs:
Linux kali 4.0.0-kali1-686-pae #1 SMP Debian 4.0.4-1+kali2 (2015-06-03) i686 GNU/Linux
Electrum 1.9.8 via tor localhost port (this setup works - i have sent, recieved, and verified transactions via tor port for anonymity)

The Electrum Bug:

Thank you electrum delvelopers in advance for you time and attention to keeping electrum a strong bitcoin client - bitcoin community needs and appreciates you.

@ecdsa
Copy link
Member

ecdsa commented Dec 9, 2015

please don't report bugs about 1.9.8.
upgrade to the latest version first, and check if the bug exists with it

@ecdsa ecdsa closed this as completed Dec 10, 2015
@treodu
Copy link
Author

treodu commented Dec 13, 2015

sure about that? Both versions seem to slow debian systems - very questionable as to coding
both versions have same bug
I will report this again and bring to the for front the VERY strange behavior of electrum and perhaps the code would benefit from independent review for safety and functionality. Other wallets do not seem to run so many "unidentified" processes in the background - this coupled with this balance bug that recurs in so many forms (as detailed in my initial question) any one concerned about there bitcoins will be concerned about what im uncovering

Toporin pushed a commit to Toporin/electrum-satochip that referenced this issue Sep 25, 2019
* Update Chaquopy pycryptodomex hashes

* Add Romanian plural formula

* Take default cashaddr format setting from back end

* Simplify main activity fragment tracking (closes spesmilo#1576)

* Add another null check for TextView.getLayout (closes spesmilo#1592)

* Fix intent handler so URIs are never processed multiple times

* Factor out base class for all dialogs which work on a background thread, and ensure multiple threads are never created (closes spesmilo#1575)

* Add uncapitalized string

* Migrate to AndroidX using IDE

* Tidy up after migration

* Move `py` variable from Daemon.kt to App.kt:

On startup, if ACRA attempts to resend a crash report which previously failed, it accesses `py` to get the Python version number. But this also initializes all the other global variables in the same file, which caused the following exception:

java.lang.IllegalStateException: Cannot invoke setValue on a background thread
        at androidx.lifecycle.LiveData.assertMainThread(LiveData.java:443)
        at androidx.lifecycle.LiveData.setValue(LiveData.java:286)
        at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:33)
        at org.electroncash.electroncash3.DaemonKt.<clinit>(Daemon.kt:23)
        at org.electroncash.electroncash3.DaemonKt.getPy(Unknown Source:0) 
        at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Crash.kt:102)
        at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Unknown Source:0)
        at org.electroncash.electroncash3.CrashKt.putJson(Crash.kt:116)
        at org.electroncash.electroncash3.CrashKt.reportToJson(Crash.kt:101)
        at org.electroncash.electroncash3.CrashhubSender.convertToString(Crash.kt:62)
        at org.acra.sender.HttpSender.send(HttpSender.java:127)
        at org.acra.sender.ReportDistributor.sendCrashReport(ReportDistributor.java:111)
        at org.acra.sender.ReportDistributor.distribute(ReportDistributor.java:76)
        at org.acra.sender.SenderService.onHandleWork(SenderService.java:84)
        at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:392)
        at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 
        at java.lang.Thread.run(Thread.java:764) 

* Fix Enter key repeating if ACTION_UP is lost during a rotation

* Update to androidx.fragment and androidx.appcompat version 1.1.0 (closes spesmilo#1091)

* Implement AlertDialogFragment.createView (spesmilo#1091)

* Access synthetic properties on fragment rather than dialog  /  Remove dialog parameter from onShowDialog and onFirstShowDialog

* Work around toast bug in Android 7.1 (closes spesmilo#1528)

* Fix warning
Toporin pushed a commit to Toporin/electrum-satochip that referenced this issue Feb 16, 2021
* Update Chaquopy pycryptodomex hashes

* Add Romanian plural formula

* Take default cashaddr format setting from back end

* Simplify main activity fragment tracking (closes spesmilo#1576)

* Add another null check for TextView.getLayout (closes spesmilo#1592)

* Fix intent handler so URIs are never processed multiple times

* Factor out base class for all dialogs which work on a background thread, and ensure multiple threads are never created (closes spesmilo#1575)

* Add uncapitalized string

* Migrate to AndroidX using IDE

* Tidy up after migration

* Move `py` variable from Daemon.kt to App.kt:

On startup, if ACRA attempts to resend a crash report which previously failed, it accesses `py` to get the Python version number. But this also initializes all the other global variables in the same file, which caused the following exception:

java.lang.IllegalStateException: Cannot invoke setValue on a background thread
        at androidx.lifecycle.LiveData.assertMainThread(LiveData.java:443)
        at androidx.lifecycle.LiveData.setValue(LiveData.java:286)
        at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:33)
        at org.electroncash.electroncash3.DaemonKt.<clinit>(Daemon.kt:23)
        at org.electroncash.electroncash3.DaemonKt.getPy(Unknown Source:0) 
        at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Crash.kt:102)
        at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Unknown Source:0)
        at org.electroncash.electroncash3.CrashKt.putJson(Crash.kt:116)
        at org.electroncash.electroncash3.CrashKt.reportToJson(Crash.kt:101)
        at org.electroncash.electroncash3.CrashhubSender.convertToString(Crash.kt:62)
        at org.acra.sender.HttpSender.send(HttpSender.java:127)
        at org.acra.sender.ReportDistributor.sendCrashReport(ReportDistributor.java:111)
        at org.acra.sender.ReportDistributor.distribute(ReportDistributor.java:76)
        at org.acra.sender.SenderService.onHandleWork(SenderService.java:84)
        at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:392)
        at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 
        at java.lang.Thread.run(Thread.java:764) 

* Fix Enter key repeating if ACTION_UP is lost during a rotation

* Update to androidx.fragment and androidx.appcompat version 1.1.0 (closes spesmilo#1091)

* Implement AlertDialogFragment.createView (spesmilo#1091)

* Access synthetic properties on fragment rather than dialog  /  Remove dialog parameter from onShowDialog and onFirstShowDialog

* Work around toast bug in Android 7.1 (closes spesmilo#1528)

* Fix warning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants