Encryption: Mobilink 12 syncing to Mobilink 16

[Former Member]

I have a situation where we are trying to upgrade to SQL Anywhere 16 to get the benefits of the TLS 1.1 encryption protocol.

The man calling the shots doesn't want to upgrade all of the client databases to SQLA 16, though.  Just the Consolidated database, where the MobiLink server is.

So what would happen if someone using MobiLink 12 syncs to a MobiLink 16 service connected to a SQLA 16 database?  Is this even possible?  And if so, would the synchronization use TLS 1.0 or TLS 1.1?

Thanks in advance!

Guy

[former_member188493]

Historically, it is very common for both SQL Remote and MobiLink shops to have vast numbers of client sites using different versions of the client software, where "vast" means "thousands" :-)... big bang upgrades can be literally impossible (say, across ships on the ocean).

Getting specific... the V16 Help says "The version 16 MobiLink server can be used with clients that are version 11 or later."

TLS versions supported by V16 are discussed separately: "TLS versions 1.0 and 1.1 are supported."

That, plus an application of The Watcom Rule, gets us to 99% confidence that TLS 1.0 and 1.1 can be mixed across different clients.

You're going to have to test anyway ( riigggghht?  ) so you might as well try it now and see 🙂

[Former Member]

Hi, Breck!  Good to speak to you again!  Hope all is well.

The end goal here is to ensure that all synchronizations are using TLS 1.1.

So that brings me to a few more questions -- mostly due to not knowing exactly how a TLS encryption protocol works behind the scenes...

Lets say a SQLA12 client initiates a sync to the ML16 server (as per my scenario).  Which of the following are more likely to happen?

• The ML16 will create the entire encrypted connection between the two sockets, which will be encrypted with TLS 1.1?... OR...
• The ML16 server will upload its data using TLS 1.1, and the SQLA12 client will upload its data using TLS 1.0?... OR...
• The SQLA12 client creates the connection, using TLS 1.0?

We are trying to get a little more information before deciding to upgrade to SQLA16, and then we'd be able to test from there.

When starting to test, how can we determine which encryption protocol is actually being used?

Thanks!

[former_member188493]

According to point (2) The Watcom Implication, "If you want to know how Watcom does something, simply determine how it should be done."

Using that rule as a basis for this WAG: A MobiLink V12 client only understands TLS 1.0, and therefore can only send and receive TLS 1.0 traffic to and from the MobiLink V16 server. The MobiLink V12 client initiates the synchronization using TLS 1.0 and the MobiLink V16 server takes its cue from that.

So... Door Number Three... "The SQLA12 client creates the connection, using TLS 1.0".

For a real answer, plus any answer to "how can we determine which encryption protocol is actually being used?", try posting a new question... because people who know the answers might not read this question, because [deep breath] they think the mere existence of my responses means everything's been dealt with 🙂

[former_member188493]

There's another reason to upgrade: Version 17 has shipped so V12's days are numbered as far as bug fixes are concerned.