Sybase ASE SSL encryption for instance aliases

[william-paul_philibert]

Bonjour,

  I have setup SSL on my new Sybase ASE 15.7 development environment.

When I try to connect to my instance using the "real" servername, it works.

Example,  my servername is called sybdev.  When I connect to sybdev, unsing SSL encryption, it works.

But, for legacy reason, I have to use "aliases" in the interfaces file so that old applications can connect to the new ASE instance.  Replacing aliases with the real servername is the least wanted solution here.

So, in the interfaces file, I have created an entry but instead of using sybdev, I am using, sybd01, for example.  When I try to connect to sybd01 using SSL encryption, it fails.

Is there a workaround to enable the use of SSL communication using "aliases"

sybdev

        master tcp ether mysybaseserver 7775 ssl

        query tcp ether mysybaseserver 7775 ssl

sybd01

        master tcp ether mysybaseserver 7775 ssl

        query tcp ether mysybaseserver 7775 ssl

Many thanks for your time and knowledge!

William

[ryan_hansen · Accepted solution]

Hi William,

You can edit your interfaces file to show this:
sybdb01
     master tcp either mysybserver 7775 ssl="cn=sybdev"
     query tcp ether mysybserver 7775 ssl="cn=sybdev"

Basically somewhere you will have to mention the CN or CommonName which is the same as your server name.

Regards,

Ryan

[william-paul_philibert · Accepted solution]

Thanks Ryan, that did the trick!

Regards