Error getting tags :
error 404Error getting tags :
error 404 encrypt | revDocs | RunRev
Welcome Guest (Log in)
Product Edition
Expander triangle

encrypt source using cipher with [password|key] passorkey[and salt saltvalue] [and IV IVvalue] [at bit ]

Desktop, Web and Server
Platform Support
MacOS,Mac OS X,Windows,Linux

Additional Comments
Expander triangle

The encrypt and decrypt commands accept the source data that will be encrypted or decrypted. The cipher is the name of the cipher obtained using the ciphernames function. The passorkey specifies the password or key that will be use for encryption or decryption as determined by the keyword before it. If you specify key then the key needs to be the same size (in bits, eight per byte) as the specified cipher key length. The key may optionally be accompanied by the IVvalue used by some ciphers. If you specify password or don't specify a key mode, then a password, tyically text, will be used. The password may optionally be accompanied by a saltvalue. The bits specifies the key length in bits (for example, 64, 128, 192 or 256) and may be zero or empty for the default length (that listed with the cipherNames function). Some ciphers have fixed key lengths and using an unsupported value will result in an error.

The key and IV value are the fundamental determiner in block ciphers. The IV value is typically the width (in bits) of the block associated with the cipher. The default value is zero. Its use is beyond the scope of this documentation.

The password and salt value are combined and scrambled to form the key and IV which are used as described above. The key derivation process is the same as that used in the openSSL utility. A 16-byte salt prefix is prepended to the encrypted data, based on the salt value. This is used in decryption. If no salt value is specified for a password, one is randomly generated. The use of a randomized salt value is a protection against dictionary attacks.

Some modes of block ciphers will pad data to be a multiple of block size. The padding method is that used by the openSSL utility and is a minimum of one byte.

On failure encrypt/decrypt set the result to the appropriate ssl error message. On success the variable it will contain the encrypted or decrypted data.

To use OpenSSL functionality with Revolution, make sure that the openssl shared library is installed, and in a place where Revolution can find it. It is pre-installed with OSX. You can download and build OpenSSL at and sitribute with your apps. Revolution includes a prebuilt openssl dll which is required to use OpenSSL for windows (libeay32.dll) which needs to be in the application, current, or system directory. If Revolution cannot load SSL, it will return the error in the result "ssl library not found".

Important! The encryptcommand is part of the SSL & Encryption library. To ensure that the command works in a standalone application, you must include this custom library when you create your standalone. In the Inclusions section on the General screen of the Standalone Application Settings window, make sure "SSL & Encryption" is selected in the list of script libraries.

User Comments
Expander triangle
User thumbnail
Oliver Kenyon
Mar 20, 2009
The encrypt command (and all other SSL & Encryption library functions) requires libssl to work on Linux. This should be fine for most systems, but some may either not have the library installed at all, or have it in a non-standard location. An easy way to verify this is to get the value of the cipherNames function, as this should not normally be empty unless the library was not found.
If its not working, you may need to install the library on the system and possibly also create a symbolic link to it to help Revolution find it. For example on SUSE Enterprise 10, I had to issue the following shell command in order to get it working:
ln -s /usr/lib/ /usr/lib/