[zeromq-dev] ZMQ_STREAM does not receive 16KB but only 8KB, possible information disclosure

Pieter Hintjens ph at imatix.com
Wed Jun 25 10:12:22 CEST 2014


The only way to deliver 'all' is to send a length field or other metadata
and then you are using framing... and not raw TCP. There really is no magic
here, and it's the same for any TCP socket.
 On Jun 25, 2014 9:01 AM, "Mathias Hablützel" <mathias.habluetzel at gmail.com>
wrote:

> Hi,
>
> On Tue, Jun 24, 2014 at 4:20 PM, Pieter Hintjens <ph at imatix.com> wrote:
>
>> It's not truncated, rather it's split up. This is inherent to TCP.
>> There's no framing, and sent data is repacked into MTUs arbitrarily.
>> You have to read until you've gotten everything you expect. If you
>> need framing, use a standard socket and ZeroMQ message.
>
>
> Ok, I was wrong with the truncated and split up, but as I would expect
> zeromq to handle this for me (I mean it delivers all parts or nothing) I
> would suggest to add a big fat red warning in the docs. Other people might
> run into it and do the same mistake as I did.
>
> Happy hacking
> mhk
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20140625/1069aef5/attachment.htm>


More information about the zeromq-dev mailing list