andy at warmcat.com
Fri Apr 1 03:53:16 CEST 2016
Thanks to the guys who found / helped fix them.
Just several minor fixes with no obvious security dimension. These all
also went into master.
NB: No API change since v1.7.0
1) MINOR: fix build with musl C library
2) MINOR: libuv handle signals only if requested
3) MINOR: Fix compile warning if HTTP2 + RELEASE + ALPN-capable SSL
4) MINOR: produce and package
5) MAJOR: make permessage-deflate enforce protocol rx buffer size
lucasterra at github spotted a problem thismorning related to
permessage-deflate and small rx_buf_size set in the protocol. I pushed
a fix which disables permessage-deflate on connections using a protocol
whose rx_buf_size is < 128, which seems required by zlib, and made
permessage-deflate adjust the size of his output buffer down if
necessary if the protocol buffer size was > 128, permessage-deflate
defaults to 1024.
If you're using permessage-deflate with its default rx buffer size of
1024, and you set a protocol rx buffer size in the protocols struct to
be nonzero and less than 1024, you should upgrade to v1.7.5 immediately.
If you don't support permessage-deflate extension, or your protocol
rx_buf_size is 0 (==4096) or >= 1024, there's no necessity to upgrade.
Use "v1.7.5" tag or just follow "v1.7-stable" branch to get the latest fixes
More information about the Libwebsockets