Wrong length information in header? about pybitmessage HOT 6 CLOSED

If it were sending the wrong length information then we would see a lot more big red messages in the console output of PyBitmessage saying that the magic bytes are wrong or that the checksum is wrong. What you are seeing is compelling but I've had my PyBitmessage client running for almost 24 hours since the last restart, I have 41 connections currently, and I have no checksum invalid messages in my console output and the only times the magic bytes on messages were wrong is when non-bitmessage clients connected to my computer trying to do other things like use it as an HTTP proxy. Do you get different behavior when you request different msg objects?

from pybitmessage.

I get this behavior only for this one object. That is what makes this strange. I guess I have to look into that deeper.

from pybitmessage.

At least I have proof right now that it's not receiving wrong things ;)
I captured the communication between my client and PyBitmessage, and I found the broken message. I cut the messages before and the messages after, because it was really big. And also, I filtered it so that only traffic that I received was captured. Unforunately I could not safe the capture in binary, so I chose a hexdump. Here's a download link: https://www.dropbox.com/s/igq41relamoechs/hexdump.bm.zip
In the first line, the fifth last byte is the start of the message, I think you can work your way from there. Note that the dump isn't even 801987 bytes long, but you can find two other messages at the end. There are probably more messages before that, as I can't really search in the hexdump.

from pybitmessage.

I've seen your commit where you used the socket.sendall method instead of socket.send. After reading the documentation, I think that could have fixed this issue. I'll update if it persists.

from pybitmessage.

Excellent. I had a feeling last night that this would also fix your issue. You will still get this issue if you are connected to Ubuntu users who are using version Bitmessage 0.2.7 and earlier though.

from pybitmessage.

I've updated the PyBitmessage client and repeated my tests, it seems to be working.

from pybitmessage.