The normal GT.M installation script (invoked by sh ./configure executed as root or with sudo sh ./configure in the directory in which you have unpacked the GT.M distribution) will automatically install GT.M with the reference implementation plug-in.

If the encryption libraries are not part of the automatic search path on your system, you will need to take action specific to your operating system and directory structure to make them accessible. For example, you may need to set one of the environment variables $LD_LIBRARY_PATH or $LIBPATH, for example: export LIBPATH="/lib:/usr/lib:/usr/local/lib" and/or run the ldconfig command.

You must also implement appropriate key management, including ensuring that users have appropriate values for $gtm_dbkeys.

The $gtm_dist/plugin directory is configured such that you can copy it to a location of your choice to customize your own encryption plug-in. After testing, simply replace the directory as distributed with your customized directory.

The structure of the $gtm_dist/plugin directory on Linux x86 is as follows:

plugin/
|-- gpgagent.tab
|-- gtmcrypt
|   |-- add_db_key.sh
|   |-- encrypt_sign_db_key.sh
|   |-- gen_keypair.sh
|   |-- gen_sym_hash.sh
|   |-- gen_sym_key.sh
|   |-- gtmcrypt.tab
|   |-- import_and_sign_key.sh
|   |-- maskpass
|   |-- pinentry-gtm.sh
|   |-- pinentry.m
|   |-- show_install_config.sh
|   `-- source.tar
|-- libgtmcrypt_gcrypt_AES256CFB.so
|-- libgtmcrypt_openssl_AES256CFB.so
|-- libgtmcrypt_openssl_BLOWFISHCFB.so
|-- libgtmcrypt.so -> ./libgtmcrypt_gcrypt_AES256CFB.so
|-- o
`-- r