We have a newer web site! Visit axcrypt.net instead!

Advanced usage

AxCrypt may be used in more advanced scenarios, such as integration into other softwares, server scripting, use from batch files etc.

Navigate the menu on the left for details.

Some notes on server side use

AxCrypt is often used as a server-side component in for example web applications, and there are some things to consider. AxCrypt is essentially a user program, with some adaptation to server side use. One of the challenges when run on a server as a service or called by a service such as IIS, is unwanted interaction between interactive use and non-interactive use. AxCrypt depends on having a resident process running which does all the real work and specifically serves as the cache for encryption and decryption keys.

The design of AxCrypt does not allow several resident processes in one session, but it does support and is aware of terminal server scenarios, so these issues do not apply then. The basic problem is that whoever uses AxCrypt first, be it a service or an interactive user on the server, will cause the resident process to be loaded and run with that users permissions and identity. If a subsequent use of AxCrypt is made in the same session from a different user, this will not work.

So, the simple rule is that if you're using AxCrypt in a server called from a service, you can't also use it interactively. The easiest way to achieve this is to not install the Windows Explorer right-click integration during setup. You can also remove this component later by using the 'Change' option in the Programs and Features applet.

There is a registry entry that is of use here, and it's called ServerMode. This is useful, but you must define it in the appropriate subkey of HKEY_CURRENT_USER of the service account if it's to be applied to the use of AxCrypt by the service. For example, if AxCrypt is run via IIS 6 under the 'NETWORK SERVICE' account, you need to change the registry for SID S-1-5-20. To have it apply to an interactive Administrator, you'll have to do the same for that Admininstrators HKEY_CURRENT_USER hive.

If you still need to use AxCrypt interactively during testing, I suggest primarly to use the AxCrypt2Go program which is found in the installation directory of AxCrypt. As an alternative, if you're careful, you can use Task Manager to kill the resident AxCrypt.exe process whenever you need a clean start.