MobiLink Synchronization User's Guide
Transport-Layer Security
You can use transport-layer security when using the TCP/IP, HTTP, or HTTPS communication protocols. For TCP/IP and HTTP, you can use either RSA or elliptic-curve encryption. For HTTPS, you must use RSA encryption.
To invoke transport-layer security, you must first set it up for the client, storing the settings in the publication, subscription, or MobiLink user. You invoke server authentication on the dbmlsrv9 command line.
For information about how to invoke transport-layer security on Adaptive Server Anywhere clients, see CREATE SYNCHRONIZATION USER statement [MobiLink].
For information about how to invoke server authentication for UltraLite clients, see Synchronization for UltraLite Applications.
For information about how to invoke server authentication for Adaptive Server Anywhere, see -x option.
The Certicom security software built into MobiLink uses certificates for the purpose of server identification. Two sample certificates are provided with Adaptive Server Anywhere, for elliptic-curve and for RSA encryption. The sample elliptic-curve certificate is called sample.crt and the password is tJ1#m6+W. The sample RSA certificate is called rsaserver.crt and the password is test.
| Caution The sample certificates should be used for testing purposes only. The sample certificates provide no security in deployed situations because they and their corresponding passwords are widely distributed with Sybase software. To protect your system, you must create your own certificate. |
The MobiLink synchronization server screen displays informational messages on startup. These messages are also sent to the log file if you start the server with the -o option. You can use the -v+ option to provide more detailed messages.
If Certicom security starts properly, the informational messages confirm this fact. The absence of such messages indicates that Certicom security has not started properly.