Messages are not received if len(message) >1048438 bytes about go-libp2p-pubsub HOT 4 CLOSED

Yes, there is a limit for message size everywhere we use delimited readers, and that's the default max message size in libp2p.

The limit is there to protect the peer from memory use DoS attacks; otherwise a peer could just send a multi-gigabyte message that slowly consumes all memory and crashes.

from go-libp2p-pubsub.

Ok, but the host object should take care of that by marking the peer as a flood peer and closing its connection. Pubsub being an "application" over libp2p core should simply not care of this limitation.
This restriction will somehow add some complexity as the message composed shall not exceed 1MB in size. If, for some reason, I have to send more data than 1MB, the program must fragment the data in more than 1 message and then the peer should be able to recompose back the original data from more messages received.

from go-libp2p-pubsub.

This limit needs to be there otherwise the delimited reader will silently read the huge message and consume all the memory.

Yes, it adds complexity, but we can't not have a limit.

from go-libp2p-pubsub.

Closing this, as I think it has been resolved.

from go-libp2p-pubsub.