Are these types of errors normal?

[chan] bitmessage
Jun 10 01:00

sock.recv error. Closing receiveData thread (Peer(host='77.247.181.163', port=443), Thread ID: 140545401539856).104/[Errno 104] Connection reset by peer Could it be indicative of messages being lost in transit? Peter Surda Bitcoin Core Developer

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Jun 10 07:48

Why are you using my name? Peter Surda Bitmessage core developer

[chan] bitmessage
Jun 10 14:26

It's a poor joke, I am much appreciative of your efforts. We need to take this thing mobile.

BM-2cWt5S2rhpNqdnZnhAHPhSXxeMc58A7FVn
Jun 10 14:44

Do you have suggestions about the mobile version ? UI-wise (e.g. it should look like the version from XYZ, ...), features, ... Have also a look at: Android * 2015 https://github.com/JonathanCoe/bitseal https://www.reddit.com/r/bitmessage/comments/3zb2fz/how_can_i_implement_bitmessage_into_my_android_app/ android and ios version https://github.com/mailchuck/PyBitmessage/issues/45 https://bitmessage.org/wiki/Mobile_Protocol_specification (from 2014)

[chan] bitmessage
Jun 11 06:15

Wow, Peter, I didn't know you were the bitcoin dev.

[chan] bitmessage
Jun 11 07:40

Shared C++ base code, hooks via... something

[chan] bitmessage
Jun 12 08:45

I too am receiving regular errors like this: sock.recv error. Closing receiveData thread (Peer(host='93.115.95.204', port=443), Thread ID: 139966220036048).104/[Errno 104] Connection reset by peer While I understand that peers might drop off the network, this seems to be happening all too often.

[chan] bitmessage
Jun 13 03:10

"Connection reset by peer" is the TCP/IP equivalent of slamming the phone back on the hook. It's more polite than merely not replying, leaving one hanging. But it's not the FIN-ACK expected of the truly polite TCP/IP converseur. Notice that the port is 443 which is typically HTTPS or HTTP over SSL/TLS. Someone is possibly trying to utilize the bitmessage network as a botnet to carry out a DDoS by injecting web servers into known nodes.

[chan] bitmessage
Jun 13 05:55

Yes so it could be the case that messages are being lost in transit in a targeted attack

[chan] bitmessage
Jun 13 08:59

Perhaps do a little research first before letting your paranoia get the best of you. As I said before 443 is usually HTTPS so a simple visit with a web browser reveals a web server is indeed running at those IP address and serving requests on port 80 and 443. Additionally reading the web page served reveals both IP address are Tor exit nodes which is confirmed by their existence in https://check.torproject.org/exit-addresses

[chan] bitmessage
Jun 14 09:14

Just today they continue with fervour. ERROR - sock.recv error. Closing receiveData thread (Peer(host='85.248.227.164', port=9002), Thread ID: 139786545940496).104/[Errno 104] Connection reset by peer ERROR - sock.recv error. Closing receiveData thread (Peer(host='83.180.73.126', port=8444), Thread ID: 139786545940176).104/[Errno 104] Connection reset by peer ERROR - sock.recv error. Closing receiveData thread (Peer(host='66.87.153.48', port=8444), Thread ID: 139786541104848).104/[Errno 104] Connection reset by peer Why would HTTP/HTTPS servers running on ports 80/443 have anything to do with BitMessage running on 8444?

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
Chips without backdoors Aug 18 05:16 3
New warnings in log Aug 17 21:00 20
Yellow peers and green peers Aug 16 20:59 4
cannot import name bmpow Aug 15 12:36 2
Brute forcing BM addr's Aug 15 07:58 6
Bitmessage crashes when posting Aug 14 05:51 10
plz assist. are you a netcat or SSH tunnel guru? Aug 14 05:01 4
shorter bitmessage addresses Aug 14 04:56 14
Why Python? Aug 13 10:45 16
Nerd Bully Aug 13 05:17 1
Bitmessage not connecting Aug 12 04:16 64
Feature idea Aug 10 03:30 10
Local nodes won't connect properly Aug 9 15:51 28
I do any thing in iran for BTC Aug 7 15:36 3
Bitmessage feature request Aug 7 12:50 4
query about short addresses Aug 7 06:54 4
Curious Aug 5 22:39 8
Full time nodes Aug 5 13:50 9
changes to the dodobit server Aug 5 11:05 2
Received Date Aug 5 06:04 13
apinotifypath Aug 4 06:04 9
BM <-> TOR Aug 3 13:19 12
BM Bandwidth Aug 2 14:11 11
When I try to register BM, collided with your key Aug 2 13:51 12
Received Date Aug 1 21:34 4
Bitmessage reminds me of ... Aug 1 14:36 3
I need help Aug 1 13:08 3
Response from Bitmessage Dodo Server Aug 1 02:25 1
Streams and bloom filter Jul 31 21:25 3
Questions about bitmessage streams Jul 31 21:25 1
TTL question Jul 31 08:03 3
API JSON index error Jul 31 07:22 3
API question Jul 30 11:22 7
MiNode Jul 30 07:19 3
Yes it's obvious my BM private keys have been stolen.... Jul 29 19:50 2
Keys.dat options Jul 29 04:56 3
Bitmessage and I2P no longer working Jul 28 22:39 10
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
Network Size Jul 22 14:47 6