SMTP mail relays exposed to the internet typically use a combination of SSL and authenticated SMTP to avoid abuse by malicious actors.
This is an excellent choice from a security perspective, but makes smoke testing a bit more complex than just opening telnet.
Continue reading “Ubuntu: Testing authenticated SMTP over TLS/SSL”
There are numerous articles I’ve written where a self-signed certificate is a prerequisite for deploying a piece of infrastructure.
Here are the quick steps for installing a self-signed certificate on an Ubuntu server.
Some of you will want a full explanation of the steps required, others will only want to run the script I’m putting on github.
Continue reading “Ubuntu: Creating a self-signed certificate using OpenSSL on Ubuntu”
The PingFederate server provides best-in-class Identity Management and SSO. However, due to US laws governing export of cryptography, the default SSL protocols and cipher suites need to be configured to harden the solution.
Below are the steps involved with making these post-installation changes.
Continue reading “PingIdentity: Disabling SSLv3 and weak ciphers for PingFederate”
While enabling HTTPS is a important step in securing your web application, it is critical that you also take steps to disable legacy protocols and low strength ciphers that can circumvent the very security you are attempting to implement.
As long as you have the latest version of openssl then you should be able to use a bash script like below (credit for this script goes here) to enumerate every matching protocol and cipher that a server is exposing:
Continue reading “OpenSSL: Using OpenSSL to enumerate protocols and ciphers in use by web applications”