You have to set up enigma plugin :
cp /……../roundcubemail/plugins/enigma/config.inc.php.dist /……../roundcubemail/plugins/enigma/config.inc.php
<?php // Enigma Plugin options // -------------------- // A driver to use for PGP. Default: "gnupg". $config['enigma_pgp_driver'] = 'gnupg'; // A driver to use for S/MIME. Default: "phpssl". $config['enigma_smime_driver'] = 'phpssl'; // Enables logging of enigma operations (including Crypt_GPG debug info) $config['enigma_debug'] = true; // Keys directory for all users. Default 'enigma/home'. // Must be writeable by PHP process $config['enigma_pgp_homedir'] = enigma/home; // Location of gpg binary. By default it will be auto-detected. // This is also a way to force gpg2 use if there are both 1.x and 2.x on the system. $config['enigma_pgp_binary'] = '/usr/bin/gpg'; // Location of gpg-agent binary. By default it will be auto-detected. // It's used with GnuPG 2.x. $config['enigma_pgp_agent'] = ''; // Location of gpgconf binary. By default it will be auto-detected. // It's used with GnuPG >= 2.1. $config['enigma_pgp_gpgconf'] = ''; // Enables signatures verification feature. $config['enigma_signatures'] = true; // Enables messages decryption feature. $config['enigma_decryption'] = true; // Enables messages encryption and signing feature. $config['enigma_encryption'] = true; // Enable signing all messages by default $config['enigma_sign_all'] = false; // Enable encrypting all messages by default $config['enigma_encrypt_all'] = false; // Enable attaching a public key to all messages by default $config['enigma_attach_pubkey'] = false; // Default for how long to store private key passwords (in minutes). // When set to 0 passwords will be stored for the whole session. $config['enigma_password_time'] = 0; // With this option you can lock composing options // of the plugin forcing the user to use configured settings. // The array accepts: 'sign', 'encrypt', 'pubkey'. // // For example, to force your users to sign every email, // you should set: // - enigma_sign_all = true // - enigma_options_lock = array('sign') // - dont_override = array('enigma_sign_all') $config['enigma_options_lock'] = array();
In this article I described how we implemented client-side encryption in Roundcube using Mailvelope. There’s another approach for encryption, it is the Enigma plugin. It implements all the functionality using server-side GNUPG software. So, the big difference in these is that: Mailvelope keeps your keys in the browser, Enigma stores them on the server. In the current state Enigma however, has a lot more features.
Installation and settings
To use Enigma just enable it as any other plugin. Then in Preferences > Settings > Encryption you’ll see a set of options that will give you possibility to enable/disable encryption-related features.
NOTE: As keys are stored on the server, make sure the directory used as a storage has proper permissions, and it’s good to move it somewhere out of the location accessible from the web (even if secured by .htaccess rules).
To manage your keys goto Settings > PGP Keys. There you can generate a new key pair or import keys. See the following screenshots for more details.
In message compose screen a new toolbar button is added with popup where you can decide if the message have to be signed and/or encrypted. The behaviour and the icon is slightly different than the one used for Mailvelope functionality. Also, note that we did not change the compose screen in any way, so all standard features like responses and spellchecking actually work.
You can find the Enigma plugin code in Roundcube 1.0 and 1.1, but only the version in Roundcube 1.2 (current git-master) is usable. I put a lot of work into this plugin and I hope there will be users that will use it. It depends on you if that solution will be extended with S/MIME or other features in future versions. Current state is described in the plugin README file .