SHA-1 based SSL Certificates are being Phased Out

Hello friends,

The following post is to advice some of you that run public facing websites which use SSL.  Google Chrome  will start giving users Warning messages when accessing sites that use SHA-1 based SSL Certificates.

By the way – This is scheduled to start happening in under a month form now. And if you are like me and test SSL on sites you manage and visit you would notice that many are now flagging SHA-1 is insecure and lowering your sites ratings on security.

What is SHA-1

The SHA-1 cryptographic hash algorithm has been known to be considerably weaker than it was designed to be since at least 2005 — 9 years ago.

Why change it now?

Well its not that its new news. SHA-1’s use on the Internet has been deprecated since 2011. However change across the world takes a bit more time.  And with the advancement of computing technology the ability to create  Collision Attacks. So companies such a Google and Projects such as Firefox, oh and Microsoft are all Sunsetting SHA-1.

What do this mean for me?

This means you need to have your certificates re-keyed through your SSL provider using a certificate signing request (CSR) with a SHA-256 signing hash if you don’t want people to get browser warnings.

But IIS doesn’t offer this?

You are correct it doesn’t.  If you are using  IIS,  regardless of what version of Windows OS (2003-2012) you only can generate SHA-1 certificates. So its time to embrace the power of Linux or simply OpenSSL to get the job done.

So my advice is that you start making the change, so that you don’t have to deal with the embarrassment of your customers and site visitors asking you why your SSL enabled site is reporting warnings.

Warning Example:  This site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it.

– Jermal

Ref Links:

Online Tool(s)

Check your SSL Sites –

Secure Apache HTTPD from POODLE

If you are running Apache, as I do you may want to take steps to secure your system but making a slight adjustment to your configuration.

By adding the simply line:

SSLProtocol All -SSLv2 -SSLv3

The file location: /etc/apache2

The file name: apache2.conf

Remember to always backup a configuration file before making changes.

Once completed restart apache:  service apache2 restart or /etc/init.d/apache2 restart


Tech Short: Let’s test for POODLE or SSLv3

First thing that came to my mind when reading about POODLE was how can I test, followed by what to do to patch/fix this.

So the first thing is to test for the vulnerability. And from all I have read so far is that you are vulnerable if your servers support SSLv3. I am confident that many of the ones I manage do; so lets test this out.

First thing I did was log into my Greyhat Test Box, thank you Kali Linux. Note: this could be any Linux distribution I just wanted to plug those guys/and/gals.

At the command line we will be using the OpenSSL tools to test by typing the following:

openssl s_client -connect <server>:<port> -ssl3

If this connects you have SSLv3 enabled, if it failed then you will see:

error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

So if you run a server check out the following links:





And for the end users, disable SSL 3.0 in your browser, avoid MITM attack by using a VPN connection and always, always use HTTPS.


Security News – POODLE Security Vulnerability

On Tuesday, October 14, 2014, Google researchers announced the discovery of a vulnerability that affects systems with SSL 3.0 enabled. This vulnerability has been named POODLE (Padding Oracle On Downgraded Legacy Encryption). Details are available at

It has been strongly encouraged to discontinue the use of SSL 3.0.

Info Sources


Man-in-the-Middle (MITM)

You are on vacation or spending the weekend at the beach. Like normal your using your laptop or smartphone.  You may be computer savvy; so you don’t allow onlookers view you typing your secure passwords.

But its not those that you can see you need to worry about.

Its the person watching your network activity; logging every site you visit, logging you bank credentials,  email, home address , contacts (friend lists), and anything else s/he can obtain. The ultimate eavesdropper.

This persons mission; to steal data from you, about you. This is the man(or woman) in the middle (MITM).

The man-in-the-middle will use many tools and security vulnerabilities which are exploited to allow them to see your data as clear as looking at it on your screen.  More so they can see your passwords even when they are all dotted out from the naked eye.

The MITM can inject code into your session to redirect you to fake sites, they can even see what you are viewing in real time.

Attackers use non-secured log-ins to apps on your phone and web sites you visit to obtain data about you.

So how do I protect myself from this?

There are many solutions; the best methods are to always use applications (apps) on your phone that use secure connections to the services it connects to.  This may be a shock to you; many do not, and this is part of the problem.

Always use sites that are secured with HTTPS from start to finish.  Again, many do not, and this leaves you exposed.

If and when possible use a VPN (virtual private network) solution.

This is another form of protection as your communication is sent encrypted threw a network you trust to be more secure than the one you are presently on.

So best advice I can offer you is

  • Be aware of the sites you visit
  • Ensure the sites you use , are using SSL
  • Be sure the apps you choose to use, are using SSL
  • Get a VPN Solution
  • And change your passwords often
  • And don’t use the same password for everything