Ubuntu
quassel package

  1. Bug #1868698
  2. Comment #2

Comment 2 for bug 1868698

Revision history for this message
Oliver Gerlich (ogerlich) wrote :

So for the quasselclient issue I've now compared the wireshark traces of 0.12.2-0ubuntu1 and 0.12.2-0ubuntu1.16.04.2. At startup both send a payload of 12 bytes.

0.12.2-0ubuntu1:
    42 b3 3f 03 00 00 00 02 80 00 00 01
0.12.2-0ubuntu1.16.04.2
    42 b3 3f 02 00 00 00 02 80 00 00 01

They only differ in the 4th byte (working client sends 0x03, broken client sends 0x02).
According to https://quasseldroid.info/docs/protocol/layers/framing/ that byte contains the handshake feature flags. 0x02 means "Compression"; 0x03 means "TLS" and "Compression".

So it looks like quasselclient 0.12.2-0ubuntu1.16.04.2 does not use TLS for the core connection any more.