Jul 2 07:59 [raw]
Seems the spam(-test?) is over. I'm wondering why the spamer sent all the messages with empty subject, so they were easy to delete. With different subjects I guess the chans would become unusable. Maybe in the next attac? Is there no strategy against that?
Jul 2 08:33 [raw]
Not really. You'd have to trawl through all the messages, and delete the spam.
Jul 2 08:47 [raw]
that said my bitmessage is still eating up bandwidth both directions like a hungry hippo
Jul 2 09:50 [raw]
the protocol should require a small proof of work for each of these actions: exchanging knownnodes (PoW for each one, instead of swapping lists) exchanging TLS keys and handshaking giving or receiving hashes of objects inventory (PoW for every single hash) exchaning every object (independent of sender PoW) exchanging pubkey objects (either requesting or receiving) the PoW should be recalculated for every node+node exchange based on current time and their ephemeral keys. the PoW should be tuned to the number of active streams, with target just high enough to take about a quarter second for each action. these measures would make spamming extremely expensive, would require an attacker to have thousands of IP addresses to even try, and lots of servers to attempt the PoW requirements, and as soon as one IP violates the PoW protocol the peers that witness it would ban the IP temporarily.
Jul 2 10:41 [raw]
What is the connection churning rate like?
Jul 2 11:59 [raw]
I'm not seeing this. After running it for four and a half hours, I have downloaded 7 MB and uploaded 3 MB.
Jul 2 12:18 [raw]
Of course you can't see my computer's activity.
Jul 2 12:26 [raw]
You know that's not what I meant. What I'm saying is that my BM is not seeing the same high level of network activity that you have. Mine has now been running for six hours, and in that time I have downloaded 8 MB and uploaded 3 MB of data.
Jul 2 12:41 [raw]
Good for you. Would you like a sticker?
Jul 3 07:18 [raw]
The relative inactivity of my BM networking proves that you are an attention seeking black liar, and there is no network flooding taking place.
Jul 3 07:40 [raw]
How about a cookie? Sticker not good enough for you?
Jul 3 07:40 [raw]
OP never said anything about network flooding. You are making assumptions. Go back and re-read the original post before you shoot your mouth off and make an ass out of yourself. OP said his bitmessage is constantly pulling data. Nothing was said about network flooding. If OP had a BSOD but you were running android, you would call him an attention seeking black liar because there's no BSOD on your screen.
Jul 3 07:42 [raw]
O'RLY? In my case: PyBitmessage 0.6.3.2-634a49c, running on Ubuntu 16.04.4 Upload speed limit: 36 kB/s, Download speed limit: 72 kB/s BM is running for 98 minutes, and has uploaded 157Mb, downloaded 158Mb (43 hosts connected to mine, mine connected to 5 hosts) /Suraquis
Jul 3 07:55 [raw]
300+ MB for a few text messages is ridiculous. If I raise my upload and download speed limits to 512kB, It sucks at max speed and quickly eats up hundreds of megabytes of bandwidth. There is non-stop data exchange without any letup.
Jul 3 11:38 [raw]
> PyBitmessage 0.6.3.2-634a49c There's your problem. You are still running a version that has the 50,000 inv bug which results in the traffic you are experiencing. You should update to 0.6.3-c7d3784 (June 27, 2018).
Jul 3 11:56 [raw]
Jul 3 13:14 [raw]
I pulled the latest commit and still have non-stop exchange of bandwidth that never ceases
Jul 3 13:49 [raw]
Updated it, thanks, now watching the bandwidth usage...
Jul 3 14:13 [raw]
Yes, upgraded to this exactly version. Pity the site is too out-of-date.
Jul 3 15:47 [raw]
Well, I have updated to 0.6.3.2-c7d3784, as I said, but bandwidth is still being gobbled: Stats after running the new version for 60 minutes: Uploaded: 102Mb, Downloaded: 211Mb Download limit: 96kB/s, upload limit: 48 kB/s Processed 211 person-to-person messages Processed 53 broadcast messages Processed 28 public keys Any more pieces of advice, please? Upgrading obviously didn't work. /Suraquis
Jul 3 20:24 [raw]
...and stats after running for 3 hours: Uploaded: 290Mb, downloaded 598 Mb Processed 1045 person-to-person messages Processed 63 broadcast messages Processed 34 public keys Definitely, the mentioned upgrade solved nothing, talking about bandwidth usage. /Suraquis
Jul 3 21:12 [raw]
If you're accepting incoming connections, it is expected to take a lot of bandwidth. Peter Surda Bitmessage core developer
Jul 4 11:43 [raw]
Is it possible to estimate that lot of bandwidth? I intend to keep at least one of my servers open, running BM 24/7 and unthrottled, but every device in this imperfect world has its limits. The overall network depends on how many hosts do accept incoming connections. As network and its requested transfer capacity grows, bandwidth consumption can as well become a bottleneck. Just curious whether there were estimations of such limits. Thanks. /Suraquis
Jul 4 13:12 [raw]
You only need to connect to a maximum of 8 peers.
Jul 4 14:59 [raw]
Yes, I didn't changed the default maxoutboundconnections = 8 But I see no obvious means to restrict the number of *incoming* connections (but I envision a grave problem if everyone could set the number of incoming connections)
Jul 4 15:23 [raw]
Is it's possible to restrict the number of incoming connections? Recently I started to observe maximum 2 outgoing connections in the same time having a dozen of peers connected to mine. maxoutboundconnections = 8 maxbootstrapconnections = 4 maxtotalconnections = 64 $ grep host .config/PyBitmessage/knownnodes.dat | sort -u | wc -l 17383 $ grep rating .config/PyBitmessage/knownnodes.dat | sort -u "rating": 0, "rating": 0.0, "rating": -0.09999999999999998, "rating": -0.1, "rating": 0.1, "rating": -0.2, "rating": 0.2, "rating": -0.20000000000000004, "rating": -0.3, "rating": -0.30000000000000004, "rating": 0.30000000000000004, "rating": -0.4, "rating": 0.4, "rating": 0.5, "rating": 1, "rating": 2.7755575615628914e-17,
Jul 5 00:27 [raw]
Default maxtotalconnections is 200 Default maxbootstrapconnections is 20 The real limit at which new incoming connections are refused is maxtotalconnections + maxbootstrapconnections + 10 (default 230).
Jul 15 01:58 [raw]
In this case, Suraquis has too many connections to other peers. Normally 8 peers is fine to obtain a sufficient network connection. (Running on Mac, 0.6.3.2)
Jul 17 21:52 [raw]
It is because you use a version of Bitmessage that does not ignore the original stream 1 where all the spam is. Any serious discussion is on stream 4 or higher.
Jul 17 23:50 [raw]
There are no streams higher than stream 1. Streams are not implemented in Bitmessage.
Jul 17 23:53 [raw]
There are no streams higher than stream 1. Streams are not implemented in Bitmessage.
Nov 15 11:56 [raw]
I made a break with the chans for a few weeks because of the spam-attack. Seems, that it's over? I hope so. Is it right, that this can always happen again? At least I have no idea, how to prevent this without loosing the freedom and anonymity of the Bitmessage chans. But I can imagine, that the person to person messages were affected, too, because the malicious traffic slows down the network. Maybe it was a test out from a government, how to stop unwanted communication, when they want it.
Nov 15 12:33 [raw]
we could drive up difficulty but that slows down stuff too
Nov 15 13:38 [raw]
No, it was just a snotgobbler who thought that blocking BM with spam was a funny joke.
Nov 15 17:02 [raw]
the takeaway seems to be that "difficulty" is not trivial to make use of to destroy spam setting up difficulty is complicated like setup of a PKI infrastructure
|Call to murder Angela Merkel, Emmanuel Macron, Petro Poroshenko, Jens Stoltenberg etc.||Jan 18 01:15||3|
|torIRC server now active||Jan 16 14:25||1|
|BM is too damned large . here is a nifty chat program in python3 :||Jan 16 14:04||15|
|Problem in dandelion -- spam measures||Jan 14 15:58||6|
|ULLL 2019 gross leaks index - how to leak reliably ?||Jan 14 09:54||1|
|archive BMs here : https://archive.fo/beamstat.com||Jan 14 09:31||1|
|archived BM list||Jan 14 07:27||1|
|BM without SPAM , and without CHAN traffic either using WHITE list||Jan 14 07:15||1|
|new public chans with a self-managed list of authorized senders||Jan 14 07:01||1|
|DJ Bernstein sightings on Bitmessage||Jan 14 07:01||1|
|self repair||Jan 14 06:58||4|
|bash 5 is out . what a blast!||Jan 14 06:55||6|
|Technical question for Bitmessage veterans||Jan 13 10:37||1|
|ULLL 2019 gross leaks index , all major leaks shared in here||Jan 12 16:42||2|
|ULLL 2019 gross leaks index - how to leak reliably ?||Jan 12 11:21||3|
|G0d @ _0rbit -- Doxxing-Adventskalender -- CDU SPD FDP LINKE -- Bundestag-Hackerangriff||Jan 12 03:31||1|
|** hot shit 2019 ** g0d _orbit 6 GB leak about German politicians||Jan 11 21:46||3|
|** hot shit ** the dark overlord ransom note 9/11 hyper LEAK||Jan 11 17:42||2|
|** hot shit 2019 ** g0d _orbit 6 GB leak about German politicians||Jan 11 16:32||2|
|BitMessage spammer.||Jan 11 11:19||5|
|Optimization technique law of semisymmetry||Jan 6 22:09||1|
|studdingsail parallel line||Jan 6 22:09||1|
|Air dose surprisingly||Jan 6 22:09||1|
|Concentration of authority orthogonal structure||Jan 6 22:09||1|
|Video preamplifier safety dog||Jan 6 22:09||1|
|Mechanized logging operations with sado||Jan 6 22:09||1|
|Compiled object program in air draft||Jan 6 22:09||1|
|Homesteader quarry stone||Jan 6 22:09||1|
|Convex end with scale resistance||Jan 6 22:09||1|
|Efforce grandual felling||Jan 6 22:05||1|
|Sigma homomorphism the intrinsic silicon||Jan 6 22:03||1|
|Pinpoint light shift fault||Jan 6 22:01||1|
|cutting edge package searching lighting||Jan 6 21:57||1|
|Law of conservation of momentum bow down||Jan 6 21:50||1|
|Eccentrics on skew corbel||Jan 6 21:47||1|
|Cable reinforcement early bird discount||Jan 6 21:44||1|
|vox, et praeterea nihil external cause||Jan 6 21:42||1|
|Microstatement with impelling||Jan 6 21:36||1|
|get the knock effective failure||Jan 6 21:36||1|
|Credulous defective condition||Jan 6 21:36||1|
|Splashdown them birdwoman||Jan 6 21:35||1|
|toughest the spinal cord||Jan 6 21:33||1|
|Immensely ingot car||Jan 6 21:30||1|
|moisture adsorption magnetically positioned perforator||Jan 6 21:24||1|
|Demyship jimjams||Jan 6 21:22||1|
|Calibration scale sour gasoline||Jan 6 21:22||1|
|Fluid filtration decantation recepticle||Jan 6 21:21||1|
|Hornist master control||Jan 6 21:16||1|
|Forelock visitatorial||Jan 6 21:16||1|
|Striking wedges specific weight||Jan 6 21:14||1|
|Painless the insomnia||Jan 6 21:13||1|
|Service simulating test hosiery industry||Jan 6 21:12||1|
|Neverland from there||Jan 6 21:12||1|
|Scuffled effectively||Jan 6 21:10||1|
|Systems integration into metalogical||Jan 6 21:10||1|
|Undefended auxiliary transformation||Jan 6 21:10||1|
|Path inspection diagram||Jan 6 21:09||1|
|Slumber away pressure loss in annulus||Jan 6 21:08||1|
|Swealing the invisible rays||Jan 6 21:07||1|
|Termination style packaged defect||Jan 6 21:07||1|
|Offset duplicator tape start||Jan 6 21:07||1|
|Soundingboard the synthetic diamond||Jan 6 21:06||1|
|enablement reluctance synchronizing||Jan 6 21:06||1|
|Autoignition temperature sparce||Jan 6 21:00||1|
|Blown glassware range gating||Jan 6 21:00||1|
|Moon crater into thin grating||Jan 6 21:00||1|
|Phasic development turbine setting||Jan 6 20:59||1|
|disabled interruption radiant superheater||Jan 6 20:57||1|
|Prelude hoisetrain||Jan 6 20:55||1|
|Principal stress yoke adjustment||Jan 6 20:51||1|
|Opposition method stored current||Jan 6 20:24||1|
|positive matrix acoustic cover||Jan 6 20:22||1|
|Gentiamarin the cane fiber||Jan 6 20:21||1|
|Nucleus of center flotation tank||Jan 6 20:18||1|
|harmonic generation with deoxidate||Jan 6 20:16||1|
|bolt strap force tentackled||Jan 6 20:15||1|
|Bank merger backshift||Jan 6 20:15||1|
|chillingly ugly duckling||Jan 6 20:15||1|
|Mortgage foreclosure capacitive window||Jan 6 20:15||1|
|Muscovado collective farm worker||Jan 6 20:15||1|
|integral conoid erasing rubber||Jan 6 20:15||1|
|Nonpacked format soleprint||Jan 6 20:14||1|
|Desegmentation rotorcraft ground resonance||Jan 6 20:11||1|
|Magnetic guidance reclaimed heat||Jan 6 20:10||1|
|clandestine meeting tapping interval||Jan 6 20:05||1|
|Variable quantizing level hostile environment logging tool||Jan 6 20:05||1|
|release brake epiguanine||Jan 6 20:05||1|
|Data interchange system for exploded custom||Jan 6 20:05||1|
|telecommunications system error breakpoint||Jan 6 20:05||1|
|atmospheric transmittance certainties||Jan 6 20:05||1|
|Relic coil conceded||Jan 6 20:05||1|
|Minima the panaramic||Jan 6 20:05||1|
|decolouration independent agencies||Jan 6 20:05||1|
|Snitch them slumbrously||Jan 6 19:56||1|
|Irreversible element ladder round||Jan 6 19:56||1|
|Capture a market correcting circuit||Jan 6 19:56||1|
|Observed number border incident||Jan 6 19:56||1|
|Dislocation martensite underquote||Jan 6 19:56||1|
|Team teaching closure of set||Jan 6 19:56||1|
|Lost arrivals the seek employment||Jan 6 19:56||1|