Configure libtcl.cfg

Drivers are libraries that provide an interface to an external service provider. Use the libtcl.cfg configuration file on a 32-bit machine or libtcl64.cfg configuration file on a 64-bit machine as a template into which you enter all the configuration information about the security drivers installed on a machine.

The libtcl.cfg file is located in the $SYBASE/$SYBASE_OCS/config/ directory in UNIX, or the %SYBASE%\%SYBASE_OCS%\ini directory in Windows. Refer to the Open Client and Open Server Configuration Guide for more information about Sybase drivers.

The syntax for a security driver entry is:

provider=driver init-string

where

provider is the local name for the security mechanism, for example, “dce.” The mapping of the local name to a global object identifier is defined in objectid.dat.
- The default local name for the DCE security mechanism is “dce.”
- The default local name for the Kerberos security mechanism is “csfkrb5.”
If you use a local mechanism name other than the default, you must change the local name in the objectid.dat file.
driver is the name of the security driver, for example, libsdce.so.
init-string is the initialization string for the driver.
- For the DCE driver, use this syntax for init-string, where cell_name is the name of your DCE cell:
```
secbase=/.:/cell_name
```
- For the Kerberos driver, use this syntax for init-string, where domaine_name is the name of your Kerberos domaine:
```
secbase=@domaine_name
```

Use a text editor to customize libtcl.cfg for your site. Make sure that lines you do not want are preceded with the “;” character. Change one parameter at a time and reboot Replication Server to effect the changes you make.

An example of an entry for a DCE driver is:

[SECURITY]
dce=libsdce.so secbase=/.:/cell_name

An example of an entry for a Kerberos driver is:

[SECURITY]
csfkrb5=libsybskrb.so
secbase=@ASE libgss=/krb5/lib/libgss.so