SSL/TLS


This article describes how to configure Postfix and Dovecot to use SSL/TLS to encrypt communication. Before you begin, generate an SSL certificate.

(more…)
 

To use SSL or TLS to encrypt SMTP, POP3, IMAP or HTTP connections requires an SSL certificate. This article describes how to generate your own self signed SSL certificate. A self signed certificate will not cost you any money, but the certificate will not be automatically accepted as trusted by the email client or web browser.

(more…)
 

An SSL connection to Active Directory is required in order to update a user’s password using LDAP. This article describes how to configure and test 389 Directory Server to synchronize with an Active Directory Server via an SSL LDAP connection.

(more…)
 

This article describes how to install an SSL certificate in 389 Directory Server to be able to use encypted SSL connection during synchronization. If you will be synchronizing with an Active Directory server, make sure SSL is enabled. You’ll also need a base-64 encoded SSL certificate from your Active Directory server.

(more…)
 

Secure Sockets Layer (SSL) enables the HTTP protocol to be secured. This page will show you how to configure SSL in Apache and SquirrelMail.

(more…)
 

If you are using Active Directory, you can use the Microsoft Certificate Services to generate an SSL certificate suitable for use in an office environment. This page will show you how to request a certificate from the Microsoft Certificate Services for use in a web server.

(more…)
 

To communicate with the Active Directory server over the Secure Sockets Layer (SSL), you need an SSL enabled server and an SSL certificate for the client. SSL communication is required to programmatically change the Active Directory password.

(more…)
 

Enabling SSL in Active Directory allows clients to communicate securely with AD servers. This is also required to allow a user’s Active Directory password to be changed programmatically using LDAP.

(more…)