Precedence of work / Priority of work

BM-NBACvhWaK4JpFY4hMcWDqt7JtVx78c1z
Jun 30 23:08

Does bitmessage place priority of sending messages before receiving and decoding messages? If send is not top priority an attacker could DDoS an individual address by constantly flooding it with incoming objects from a botnet. If address can be hanged or slowed due to incoming objects DDoS is serious threat. I guess that the protocol should prioritize sending of a locally composed message before all other operations. Nothing incoming to a node should have any effect of slowing down PoW and sending of outgoing original messages. If this is not the case then a permanent DDoS of an individual bm-address is trivial to implement. I didn't see anything about precedence of work or priority of work in the protocol paper. Please advise me if this concern is unfounded or already mitigated in the bitmessage protocol. ~ cl!Q

[chan] bitmessage
Jul 1 00:22

You are right, it seems to be an oversight of the protocol design. However I have not yet come across an implementation that does not use multithreading which effectively mitigates your concern.

[chan] bitmessage
Jul 1 00:50

If one dedicate thread were kept running strictly and only for sending original objects with high priority and the remaining threads multitask that might be perfect enough.

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Jul 1 05:38

> Does bitmessage place priority of sending messages before receiving > and decoding messages? Those happen in separate threads. > I didn't see anything about precedence of work or priority of work > in the protocol paper. Please advise me if this concern is unfounded > or already mitigated in the bitmessage protocol. Some parts were synchronous in the past, but now they happen in separate threads. > ~ cl!Q Peter Surda Bitmessage core developer

[chan] bitmessage
Jul 16 20:43

My understanding is that sending requires proof-of-work (is computationally expensive) while receiving/decoding does not. So a DDoS should be significantly more expensive for the attacker than for the target. Abraham Lincoln Bitmessage core developer

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
Bitmessage and I2P no longer working Jul 28 14:24 9
Connect Bitmessage only to .onion nodes Jul 27 13:22 3
peers Jul 26 11:36 4
© 2013-2016 The Bitmessage Developers Jul 26 07:12 6
0.6.3 Jul 24 20:52 3
Bug with chan creation Jul 24 10:15 12
Brute forcing BM addr's Jul 23 04:22 26
Network Size Jul 22 14:47 10
memory leak? Jul 21 06:19 3
BM bot sourcecode sample Jul 20 15:56 7
RE: BM bot sourcecode sample Jul 20 04:01 1
BitMessage need new improvements Jul 19 23:35 3
2 bugs while quitting Jul 19 19:03 1
[Feature Request/Question] Blacklist counters Jul 19 12:01 1
raspberry pi Jul 18 17:13 3
Feature request (2) Jul 17 00:44 13
Bug report (UI shows deleted messages) Jul 17 00:20 3
ECC Curves: secp256k1 versus secp521r1 -> BitMessage Secure Station Jul 16 22:18 1
PyBitmessage message save folder Jul 16 21:00 5
HELP(!) - Impossible PoW recipient address msg Jul 16 20:53 6
ECC Curves: secp256k1 versus secp521r1 Jul 16 20:44 28
Precedence of work / Priority of work Jul 16 20:43 5
I need help Jul 16 16:42 1
Pre-commitment and "open source canary" Jul 16 16:41 2
Killing impossible PoW sent items (daemon) Jul 16 16:40 1
Feature request (1) Jul 13 13:45 6
Bitmessage statistics Jul 13 09:42 13
addr command problems and plans Jul 13 06:19 7
BM client 0.6.2 (OS X) does not show images Jul 12 04:16 24
bug in latest commits Jul 11 08:46 11
Bitmessage bug in latest v0.6 branch Jul 11 06:09 1
bmwrapper broadcasts Jul 10 14:27 5
Beamstat chanlist bug? Jul 10 06:10 3
FPGA Hardware backdoors risk and counter-measures, regarding « TOR/VPN fingerprinting family anonymity breach fix » with a custom FPGA based « Single Socket » Ethernet Controller. Jul 9 11:36 1
tor socks access issues continue (0.6dEV pYbm code @ 20170706) Jul 8 23:10 3
FPGA Hardware backdoors, regarding « TOR/VPN fingerprinting family anonymity breach fix » with a custom FPGA based « Single Socket » Ethernet Controller. Jul 8 14:10 3
BM-2NB prefix ? Jul 8 13:30 3
Jabit and Abit update Jul 8 07:45 1
Peer "Ratings" Jul 7 12:54 9
How to.. Jul 6 18:01 30
Is there a quick way to export a thread, or all threads of a chan in a readable manner. Jul 6 04:00 6
Dev-talk PML status / instructions pls Jul 5 21:04 5
BM db blob questions Jul 5 07:40 11
How to connect to more nodes Jul 5 07:34 4
P.P.S. Re: BM db blob questions Jul 5 03:21 2
bitmessage API TTL Jul 5 01:08 2
Re: Re: Re: Re: Religious garbage at this point Jul 4 22:28 7
Yes it's obvious my BM private keys have been stolen.... Jul 4 22:20 15
MiNode I2P support testing Jul 2 07:04 25
To the person running /wire:0.1.0/bmd:0.0.1/ on 158.69.119.35:8444 Jul 1 12:55 5
So you think God is a myth ... Jul 1 12:14 1
How to.. (Node Conns Encrypted) Jul 1 10:17 1