On Jun 8, 2014, at 10:29 PM, Vignesh Viswanathan -X (vignevis - EMBED UR
SYSTEMS at Cisco) <[email protected]> wrote:
> Thank you fixing this issue with PEEKREMOTE dissector.
>
> When could we possibly expect the next build with this fix included, so that
> we can give it a try with our setup and resolve our bug for the same.
If by "the next build" you mean "the next official release", then the
Development/Roadmap page on the Wireshark Wiki, at
http://wiki.wireshark.org/Development/Roadmap
says that the 1.10.8 and 1.8.15 releases should come out on June 11, 2014; the
fix was backported to the 1.10 and 1.8 branches, so the fix will be in those
releases.
If you don't build from source or, on OS X or Windows, use one of
wireshark.org's binary releases, you're at the mercy of whoever builds binary
releases for your platform (various Linux distributions, various *BSDs, various
organizations that package Wireshark for commercial UN*Xes).
If by "the next build" you mean "the next automated build", then the fixes
should be in all the automated builds; see
http://www.wireshark.org/download/automated/
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
