{"id":23829,"date":"2013-06-20T06:47:58","date_gmt":"2013-06-20T06:47:58","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/encrypted-contact\/"},"modified":"2015-02-10T15:03:48","modified_gmt":"2015-02-10T15:03:48","slug":"encrypted-contact","status":"closed","type":"plugin","link":"https:\/\/en-za.wordpress.org\/plugins\/encrypted-contact\/","author":12143310,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.3.0","stable_tag":"1.3.1","tested":"4.0.38","requires":"2.9.2","requires_php":"","requires_plugins":"","header_name":"Encrypted Contact","header_author":"Ralf Senderek","header_description":"","assets_banners_color":"","last_updated":"2015-02-10 15:03:48","external_support_url":"","external_repository_url":"","donate_link":"https:\/\/senderek.ie\/donate","header_plugin_uri":"https:\/\/snderek.ie\/wordpress\/encrypted-contact","header_author_uri":"https:\/\/senderek.ie","rating":0,"author_block_rating":0,"active_installs":0,"downloads":1161,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":[],"upgrade_notice":{"1.0":"

Security upgrade necessary.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.3.0","1.3.1"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[27171,21048,27170,12167,27169],"plugin_category":[],"plugin_contributors":[],"plugin_business_model":[],"class_list":["post-23829","plugin","type-plugin","status-closed","hentry","plugin_tags-confidential","plugin_tags-decryption","plugin_tags-encrypted-message","plugin_tags-encryption","plugin_tags-secure-contact","plugin_committers-kerrylinux"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/encrypted-contact.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n

As an online professional or business owner you need to offer your website visitors a\nsecure way to contact you. Unprotected email is not enough, even if someone tries\nto contact you for the first time.<\/p>\n\n

The Encrypted Contact plugin is the most secure way to enable secure messages for your website\nvisitors and it even allows the website owner to read (i.e. to decrypt) protected messages\nonline by using the admin panel of WordPress.<\/p>\n\n

This plugin uses the well-established Web Encryption Extension, an open source extension\nfor web applications that has been released under GPL-3 in 2011. All encryption is done\non the server with the tested standard tool GnuPG, so sending protected messages is \nboth secure and easy to use. Using Encrypted Contact on the website makes sure that \nthe website owner can stay in touch with visitors, even if he is on the road, because\neverything he needs is stored on the server. Total device independence is assured. Neither\nthe website user nor the owner has to install anything on his computer, smartphone or\ntablet, except a browser, to use the plugin securely.<\/p>\n\n

Arbitrary section<\/h3>\n\n

The plugin uses the Web Encryption Extension in its current version. You can download the\nlatest version of WEE from the \n[download page] (https:\/\/senderek.ie\/downloads) .\nIt is possible to replace the scripts for encryption, decryption and key management in your\nplugin directory with the original files from this download, without breaking anything. \nJust make sure you preserve the content of the configuration file gpgconfig.php, where\nyour recipient address is being stored.<\/p>\n\n

In order to comply with the conditions of the Detailed Plugin Guidelines<\/em> we have\nremoved the powered by Senderek Web Security link from all these scripts as a default.\nIf you wish to display this link on your website, you can replace the default files with\nthe original files you'll find in the directory websecurity<\/code>.<\/p>\n\n

All files from the Web Encryption Extension are code-signed by Senderek Web Security, so the \nsignature verification will fail on the installed files because of the missing link, but it will\nvalidate correctly on the files in the directory websecurity<\/code>. Check the difference, you'll\nfind only one line of code.<\/p>\n\n\n

    \n

  1. Have your website https-ready, make sure your visitors can reach your site via \nhttps:\/\/your-site.com.<\/p><\/li>\n

  2. Create a safe place for your encryption key by making the directory \/home\/gpg<\/code>. \nChange the ownership to the web server user and remove all permissions except for the \nowner.<\/p>\n\n

    as root run the following commands:<\/p>\n\n

    mkdir \/home\/gpg\nchown apache \/home\/gpg (you may replace apache with your web server user)\nchmod 700 \/home\/gpg<\/p><\/li>\n

  3. Upload the plugin zip-file encrypted-contact.tgz<\/code> to your \/wp-content\/plugins\/<\/code> \ndirectory and extract the plugin files. The files will be stored in a separate directory\n encrypted-contact.<\/p><\/li>\n

  4. Log into your admin panel and activate the new plugin through the plugins<\/code> menu.<\/p><\/li>\n

  5. Place the contact form in some place like the sidebar through the widgets<\/code> menu, where \nthe new widget Encrypted Contact<\/code> will show up.<\/p><\/li>\n

  6. Log into your admin panel and create a new key pair for you via the Key Management<\/code> \nbutton. Alternatively you can upload an existing private key via the Key Management tool.<\/p><\/li>\n

  7. Decide whether or not you will store the messages (encrypted or not) on the server. \nSet the Archive Messages select box to yes<\/code>. A subdirectory messages<\/code> will be created \nautomatically inside the safe place for your encryption keys and copies of all messages \nwill be archived here before the are sent out via email.\nYou can read these messages and even decrypt them online using the admin panel.<\/p><\/li>\n<\/ol>\n\n\n

    \n
    Do I need a Linux server for Encrypted Contact?<\/dt>\n

    Yes, because the software relies on the operation system capabilities of Linux to work \nsecurely. It also requires an installation of GnuPG on the server, which is usually \npresent already.<\/p><\/dd>\n

    Do I need full control over my server to install Encrypted Contact?<\/dt>\n

    Not necessarily. But you have to trust the system administrators, because the encryption is\ndone on the server and can be intercepted there. In order to perform the installation\nyou need a safe place for the encryption key(s), which is located outside the web server \ntree.\nThe default installation assumes that you use the directory \"\/home\/gpg\" for this purpose.\nYou need to ask your system administrator to create this directory for you and to make it\nwriteable for the web server process only. That means, if you cannot use a safe place for \nyour encryption keys with restrictive access permissions, your encryption will refuse to \nwork. This is not a bug but a desired performance of Encrypted Contact.<\/p>\n\n

    Once your server's sysadmin has created such a directory for you, and its name matches the\nsetting for $GPGDIR in the file \"gpgconfig.php\", then all key management can be done via\nthe admin panel without any further help from the sysadmin.<\/p>\n\n

    If you like to read more about the desirable server environment for encryption, have a\nlook at [this article] (https:\/\/senderek.ie\/articles\/what-is-a-secure-server.php).<\/p><\/dd>\n

    Why do I need to enable HTTPS on my server before I can use Encrypted Contact?<\/dt>\n

    Because, if you don't you trick your website visitors into entering confidential messages\ninto a form that transfers these messages insecurely, i.e. unencrypted to your server.\nAnd your website visitors will not even be sure their messages will arrive a the server\nyou call yours. Under these circumstances it is pointless to encrypt something on the server\nthat has arrived insecurely. Encrypted Contact will check, if the message has arrived\nvia https, and it will refuse to work, if not.<\/p>\n\n

    HTTPS is a basic requirement, if you are serious about the security of your website.<\/p><\/dd>\n\n<\/dl>\n\n\n

    1.0<\/h4>\n\n

    This is the first stable version of Encrypted Contact, released Monday, 10th June 2013.<\/p>\n\n

    1.3.1<\/h4>\n\n

    Latest version includes security upgrade.<\/p>","raw_excerpt":"Encrypted Contact offers your website visitors a tool to protect their messages before they are sent \nto the website's owner via email.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/23829","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=23829"}],"author":[{"embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/kerrylinux"}],"wp:attachment":[{"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=23829"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=23829"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=23829"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=23829"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=23829"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/en-za.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=23829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}