User's Guide
Reference Manual
Release Notes
PDF
Top

crypto
Reference Manual
Version 1.6.4

Expand All
Contract All

Table of Contents

# crypto

### APPLICATION

crypto

### APPLICATION SUMMARY

The Crypto Application

### DESCRIPTION

The purpose of the Crypto application is to provide message digest and DES encryption for SMNPv3. It provides computation of message digests MD5 and SHA, and CBC-DES encryption and decryption.

### Configuration

The following environment configuration parameters are defined for the Crypto application. Refer to application(3) for more information about configuration parameters.

debug = true | false <optional>

  Causes debug information to be written to standard error or standard output. Default is false.

### OpenSSL libraries

The current implementation of the Erlang Crypto application is based on the OpenSSL package version 0.9.7 or higher. There are source and binary releases on the web.

Source releases of OpenSSL can be downloaded from the OpenSSL project home page, or mirror sites listed there.

The same URL also contains links to some compiled binaries and libraries of OpenSSL (see the Related/Binaries menu) of which the Shining Light Productions Win32 and OpenSSL pages are of interest for the Win32 user.

For some Unix flavours there are binary packages available on the net.

If you cannot find a suitable binary OpenSSL package, you have to fetch an OpenSSL source release and compile it.

You then have to compile and install the library libcrypto.so (Unix), or the library libeay32.dll (Win32).

For Unix The crypto_drv dynamic driver is delivered linked to OpenSSL libraries in /usr/local/lib, but the default dynamic linking will also accept libraries in /lib and /usr/lib.

If that is not applicable to the particular Unix operating system used, the example Makefile in the Crypto priv/obj directory, should be used as a basis for relinking the final version of the port program.

For Win32 it is only required that the library can be found from the PATH environment variable, or that they reside in the appropriate SYSTEM32 directory; hence no particular relinking is need. Hence no example Makefile for Win32 is provided.

### SEE ALSO

application(3)