5195 Open nooneknows1 opened this issue on 12 comments nooneknows1 commented on edited by SomberNight mentioned this issue mentioned this issue accumulator on Sign up for free to join this conversation on GitHub. # License: public domain, credits go to philsmd and hashcat, props also to jtr for their electrum_fmt_plug. New issue Clients older than 3.3.0 can no longer connect/synchronize. Please still mention it here if you are looking into implementing it s.t. Update: I see quite little interest in this and my "discoveries", so it's currently quite low in my priorities to look into this. Maybe there are more obstacles that I didn't consider yet, but besides including that specific elliptic curve and adding the new kernels with a hook function, I do not see much more trouble for adding this new hash type (I think we can do both $electrum$4 and $electrum$5 with just one new hash type. deps/secp256k1) folder, we have both the zlib and elliptic curve cryptography (ecc) code for the hook needed for $electrum$4 and $electrum$5, that's my educated guess right now. Therefore, if we add these secp256k1 source code into the deps/ (e.g. I've done some little reseach again and it seems that many projects use this MIT licensed (very good for us !!!) elliptic curve with parameters Secp256k1 ( ) used by bitcoin: We could also try to ping which seem to have helped with other/older ethereum salt-types see #1805. As a starter, you could first get started with an (hopefully) easier hash mode: $electrum$3 and after you are accustomed with the hashcat code and especially the module feature, you can start experiencing with hooks (see -m 11600 = 7-Zip for an example of hook and decompression). Definitely too old to connect to electrum server and not. Ready or not remix dance 2016, Texas 10 series facebook, Tv mobile w902 manual. So how do we proceed, I would suggest that you start implementing the hook code and look for elliptic curve code that we could use (compatible license etc). I believe electrum 3.1.3 is shipped with the latest tails (not completely sure about that). but $electrum$4 and $electrum$5 need almost the same code (except decompression for $electrum$5 which we already support with deps/zlib/ ). Blocked by Tails - Bug 16421: Electrum Phishing Attack - Upstream Fix Committed Resolved: : History 1 Updated by. There are privacy and security benefits to choosing a trusted server. Users should have the option to select a server manually. in theory (for the purpose of getting $electrum$5 hashes working soon) you could skip the $electrum$3, because it's more closer to $electrum$2. Regarding the current configuration file, auto connect should not be enabled by default. Perfect privacy is impossible to guarantee. If I'm not totally mistaken we would need the hook and elliptic curve cryptography for both the $electrum$4 and $electrum$5 hashes. And the greater the privacy you want, the more tradeoffs you will need to make. The newly requested wallet, due to the inability to connect to the server, uses the first three addresses in the client's 20 addresses.The natural order would be to first implement $electrum$3*, then $electrum$4* and finally $electrum$5*. BIG BUG-The behavior affects many users-Įlectrum 3.13 Collection, preloaded with tails-amd64-3.12.1.img, has not yet been billed. This can also be done on Tails, and is easy. I suggest that you download the AppImage and run that. It is unfortunate that this also affects Tails users, where it's not exactly easy to update. To put an end to this, we've deliberately started exploiting the DOS vulnerability to make old clients unusable, hence force users to update. Old clients are vulnerable to phishing messages from servers via which users kept getting tricked and losing money. 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). Users should go to and download the latest version of Electrum. Clients older than 3.3 can no longer connect to the network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |