<div dir="ltr">Good question!<div><br></div><div>We have a (small) crypto-focused test suite that gets run from "make check" and as part of building the Debian/Ubuntu packages (and possibly Fedora/EPEL?), but it doesn't test protocol interoperability among versions of mosh that were compiled differently.<div><br></div><div>It would be great to do a rigorous test suite like this, but honestly I think this is not where we're going to get in trouble (that Google will introduce a breaking change into the protobuf wire format and we won't know about it). I'm a lot more worried about screwing up the terminal emulation (or the timeout semantics in SSP, which are a bit byzantine) than the possibility that Google will screw us over on protobuf.</div><div><br></div><div>Our intention is that that any mosh-client since 0.96 (February 2012) and any mosh-server since 1.0.9 (March 2012) can talk to each other and to the most recent release and the Git tip.</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 14, 2015 at 4:56 PM, James C. McPherson <span dir="ltr"><<a href="mailto:James.McPherson@oracle.com" target="_blank">James.McPherson@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi Alex,<br>
thankyou for the quick and reassuring response.<br>
<br>
btw, is there a test suite to help confirm the hypothesis?<br>
<span class="HOEnZb"><font color="#888888"><br>
James<br>
</font></span><div><div class="h5"><br>
On 15/05/15 09:50 AM, Alex Chernyakhovsky wrote:<br>
> Hi James,<br>
><br>
> From my reading of<br>
> <a href="https://github.com/google/protobuf/blob/master/CHANGES.txt#L187" target="_blank">https://github.com/google/protobuf/blob/master/CHANGES.txt#L187</a>, there<br>
> are no wire-level differences. As long as mosh builds, it should<br>
> stil=l be compatible across protobuf versions. I recently rebuilt<br>
> Fedora's mosh to work against libprotobuf.so.9, which IIRC is 2.6.1,<br>
> and I noticed no issues.<br>
><br>
> The protobuf generated output source should be different, since protoc<br>
> got new features.<br>
><br>
> Sincerely,<br>
> -Alex<br>
><br>
><br>
> On Thu, May 14, 2015 at 7:44 PM, James C. McPherson<br>
> <<a href="mailto:James.McPherson@oracle.com">James.McPherson@oracle.com</a>> wrote:<br>
>> Hi mosh-devel,<br>
>> I've observed that Google Protobuf has made some incompatible<br>
>> changes between v2.5 and 2.6.1.<br>
>><br>
>> When I built mosh for Solaris (internal testing / evaluation<br>
>> work), I used 2.5 and all seemed well. I built it again today<br>
>> using 2.6.1 - and again, all seems ok, but the protobuf generated<br>
>> output is different between the two versions.<br>
>><br>
>> Does mosh have a dependency on a specific version of Google<br>
>> protobuf?<br>
>><br>
>><br>
>> thanks in advance,<br>
>> James C. McPherson<br>
>> --<br>
>> Oracle<br>
>> Systems / Solaris / Core<br>
>> <a href="https://www.jmcpdotcom.com/blog" target="_blank">https://www.jmcpdotcom.com/blog</a><br>
>> _______________________________________________<br>
>> mosh-devel mailing list<br>
>> <a href="mailto:mosh-devel@mit.edu">mosh-devel@mit.edu</a><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/mosh-devel" target="_blank">http://mailman.mit.edu/mailman/listinfo/mosh-devel</a><br>
<br>
<br>
</div></div>--<br>
<div class="HOEnZb"><div class="h5">James C. McPherson<br>
--<br>
Oracle<br>
Systems / Solaris / Core<br>
<a href="https://www.jmcpdotcom.com/blog" target="_blank">https://www.jmcpdotcom.com/blog</a><br>
_______________________________________________<br>
mosh-devel mailing list<br>
<a href="mailto:mosh-devel@mit.edu">mosh-devel@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/mosh-devel" target="_blank">http://mailman.mit.edu/mailman/listinfo/mosh-devel</a><br>
</div></div></blockquote></div><br></div>