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
Wondering Jun 23 07:44 6
Privacy? I don't have anything to hide. Jun 23 07:12 2
Any predictions? Jun 23 05:11 7
Curious Jun 22 11:03 3
Bitmessage over OnionCat hidden services layer Jun 21 02:41 2
Question about PoW Jun 21 02:16 2
Free software makes millions for Richard Stallman's cult Jun 20 07:40 11
Streams? Jun 20 03:16 3
Support (connections are "stuck" when using TOR+iptables) Jun 20 03:01 6
test 14.06.2017 19:44 london time Jun 17 15:27 17
regular stats about the BitMessage network (in TZAG) Jun 17 07:17 2
DEMONSAW Believe in the Right to Share Jun 17 06:43 3
Are these types of errors normal? Jun 14 09:14 11
tor hidden service DoS vuln Fixes 20170608+ codebases Jun 13 03:16 8
MiNode experimental I2P support. Jun 11 07:35 2
Abit problems Jun 7 03:41 1
easy way to deactivate msgpack Jun 7 01:33 6
active nodes in BM Jun 6 13:36 11
Default known nodes Jun 6 08:49 3
BM good practices Jun 6 01:54 7
Bitmessage peer discovery status Jun 5 17:43 12
PyBitmessage laggy Jun 5 16:39 4
error: uncaptured python exception Jun 5 16:08 7
The Stallman Tax Jun 4 16:55 3
ransomware "crisis" Jun 4 12:57 1
RE: Hi, there is a problem Jun 2 04:09 7
[chan] memory-hard proof of work BM-2cVnsDNQJeDYoqvrSuQKEn3B6yLuMC24n3 Jun 1 10:41 1
Sorting the inbox May 31 14:59 2
Bitmessage snapshots for testing May 30 22:32 3
RE: Hi Chris! May 30 06:02 1
Broken May 29 17:03 6
HOWTO Enable asyncore in PyBitmessage 0.6 May 29 04:28 3
HOWTO Enable asyncore in PyBitmessage 0.6 May 29 01:00 2
[Feature Request] Send Later at time of day May 28 19:15 1
Fixed width font in bitmessage May 28 19:08 2
for your feature request bucket May 28 19:08 6
vanity generator May 28 15:51 12
Asyncore and Peer discovery work :-) May 28 11:38 2
What is a cyberguerilla? May 28 11:36 1
How to cancel a message? May 27 14:09 1
API TTL May 27 05:56 8