SSL: Problem generating CRS with SHA1 instead of MD5

On the Secure Socket Layer (SSL) Configuration page, I've generated a Certificate Signing Request (CSR). When I paste the CSR on my cert provider (https://StartSSL.com), it complains that "MD5 Signature Algorithm Detected".

How do I setup JumpBox to generate a CSR using SHA1?

I had a look at the source files (but I'm not a programmer). I've modified some ruby files (eassl_fix.rb and signing_request.rb) by OpenSSL::Digest::SHA1 instead of OpenSSL::Digest::MD5, but that doesn't change the outputted CSR.

Does anyone has a solution or an hint on the correct file/option to modify?

SSL: Problem generating CRS with SHA1 instead of MD5

Hi,
Could you email me your changes or the changed files? I might have a chance to try this. Changing that default is a good idea. I will file a ticket to explore that.

Austin
godber@jumpbox.com

The modified files and another suspect

Sent to Austin:

  • /jumpbox/application_portal/vendor/plugins/eassl_fix/lib/eassl_fix.rb
  • /jumpbox/application_portal/vendor/gems/eassl-0.1.1643/lib/eassl/signing_request.rb

Meanwhile I've found this in /jumpbox/application_portal/privileged_scripts/ubuntu/lib/ssl.rb:
if EaSSL::Certificate.load(file_path) && (`openssl x509 -noout -modulus -in #{file_path} | openssl md5`.strip == `openssl rsa -noout -modulus -in #{Ssl::Constants::CUSTOM_KEY_FILE} | openssl md5`.strip)