1 2 3 Previous Next 36 Replies Latest reply on Dec 1, 2015 8:06 AM by TSGal

    SHA-2 based digital certificates do not work.

    NickLowe

      Summary

      SHA-2 based digital certificates do not work.

      Product

      FileMaker Server

      Version

      13v4

      Operating system version

      Windows Server 2012 R2

      Description of the issue

      SHA-1 has been deprecated from its use in digital certificates by Microsoft, Google and Mozilla who collectively develop and maintain the majority of Web browsers that are in use worldwide.

      This is because they believe it to be insecure. Going forward, CAs will issue SHA-2 based certificates by default and will soon no longer issue SHA-1 based certificates at all.

      SHA-2 is the replacement and FileMaker needs to support this to interoperate with the modern secure Web.

      For background information on why this is needed and why it must be treated as a bug and blocking issue, see:

      https://konklone.com/post/why-google-is-hurrying-the-web-to-kill-sha-1

      http://googleonlinesecurity.blogspot.sg/2014/09/gradually-sunsetting-sha-1.html

      http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx

      https://wiki.mozilla.org/CA:Problematic_Practices#SHA-1_Certificates

      Steps to reproduce the problem

      Attempt to install a SHA-2 (SHA-256) based certificate in to FileMaker 13 from one of the major CAs.

      Expected result

      It should be possible to install and use a SHA-2 based certificate in to FileMaker from one of the major CAs.

      Actual result

      It is not possible to install and use a SHA-2 based certificate in to FileMaker from one of the major CAs.

        • 1. Re: SHA-2 based digital certificates do not work.
          TSGal

          Nick Lowe:

          Thank you for your post.

          At this time, we only cover those certificates covered in Knowledge Base Article #11413:

          http://help.filemaker.com/app/answers/detail/a_id/11413/

          This article was last updated on 3 Sep 2014.  When other certificates are added, the article will be updated again.

          TSGal
          FileMaker, Inc.

          • 2. Re: SHA-2 based digital certificates do not work.
            NickLowe

            Ah, great, thanks for the article link, it is helpful!smiley

            So, as the certificates from those CAs with the product names listed do not work with FileMaker when they are issued as SHA-2 (SHA-256), how do we progress this to get a code fix?

            The certificates listed in that article only work with FileMaker when they are issued as SHA-1.

            I assume that this makes this a clear cut bug then from your perspective as they are documented as working?

            Incidentally, you should be in the position, as certificates are all the same, where you support/cover all certificates that meet the CA/Browser forum baseline requirements:

            https://cabforum.org/about-the-baseline-requirements/

            The member CAs who issue compliant, interoperable certificates are:

            https://cabforum.org/members/

            Thanks,

            Nick

            • 3. Re: SHA-2 based digital certificates do not work.
              NickLowe

              The other concern is that the cipher suites offered are not configured correctly.

              OpenSSL should be configured to use a server defined order and the cipher suites configuration string should be set to:

              "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+AES+SHA384 EECDH+aRSA+AES+SHA384 EECDH+ECDSA+AES+SHA256 EECDH+aRSA+AES+SHA256 EECDH+ECDSA+AES+SHA1 EECDH+aRSA+AES+SHA1 EECDH+ECDSA+3DES+SHA1 EECDH+aRSA+3DES+SHA1 EDH+DSS+AESGCM EDH+aRSA+AESGCM EDH+DSS+AES+SHA384 EDH+aRSA+AES+SHA384 EDH+DSS+AES+SHA256 EDH+aRSA+AES+SHA256 EDH+DSS+AES+SHA1 EDH+aRSA+AES+SHA1 EDH+DSS+3DES+SHA1 EDH+aRSA+3DES+SHA1 aRSA+AESGCM RSA+AES+SHA256 RSA+AES+SHA1 RSA+3DES+SHA1"

              The would then give:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         
              Cipher Suites (In server-preferred order)
              TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)   ECDH 256 bits (eq. 3072 bits RSA)   FS256
              TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)   ECDH 256 bits (eq. 3072 bits RSA)   FS128
              TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)   ECDH 256 bits (eq. 3072 bits RSA)   FS256
              TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)   ECDH 256 bits (eq. 3072 bits RSA)   FS128
              TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)   ECDH 256 bits (eq. 3072 bits RSA)   FS256
              TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)   ECDH 256 bits (eq. 3072 bits RSA)   FS128
              TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012)   ECDH 256 bits (eq. 3072 bits RSA)   FS112
              TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS256
              TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS128
              TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS256
              TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS128
              TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS256
              TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS128
              TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x16)   DH 2048 bits (p: 256, g: 1, Ys: 256)   FS112
              TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)256
              TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c)128
              TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d)256
              TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c)128
              TLS_RSA_WITH_AES_256_CBC_SHA (0x35)256
              TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)128
              TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)112

               

              The SSL 2.0 and SSL 3.0 protocols should also be disabled.

              It should also be possible to easily configure a HSTS header to help mitigate MITM attacks.

               

              To observe the configuration of an Internet facing FileMaker server, use the SSL Labs tester:

              https://www.ssllabs.com/ssltest/

              The development version of the tester that includes detection of SHA-1 issues:

              https://dev.ssllabs.com/ssltest/

              • 4. Re: SHA-2 based digital certificates do not work.
                JohnDCCIU

                Someone needs to (again) light a fire under the FMS dev team, this time to support SHA-2 SSL certs ASAP.  The fact that it has gone on this long is getting close to inexcusable.  I've mentioned this in other posts awhile back, but they're still dragging their heels for some reason.

                Supporting only SHA-1 certs is no longer an option for professional, high-quality server software:



                Is this on the radar of the server dev team?

                • 5. Re: SHA-2 based digital certificates do not work.
                  TSGal

                  Nick Lowe and JohnDCCIU:

                  Thank you both for your posts.

                  I have forwarded your comments to Product Management and Development for review.

                  TSGal
                  FileMaker, Inc.

                  • 6. Re: SHA-2 based digital certificates do not work.
                    NickLowe

                    A month on, is there any update on when this will be fixed?

                    The POODLE vulnerability should definitely kill SSL 3.0 now, I suggested disabling it in my earlier comment about other issues.

                    • 7. Re: SHA-2 based digital certificates do not work.
                      JohnDCCIU

                      The SSLv3 "POODLE" vulnerability is a separate issue, not directly related to SHA-1 vs. SHA-2.  But....yes, it's yet another vulnerability the the shiny new FMS 13 is exposing us to, since they saw fit to roll their own (half-baked) SSL functionality in FMS 13 instead of continuing to use the (fully-tested) OS functionality as they did in previous versions.  

                      Hey, it's just fine to roll your own SSL if you know what you're doing:  if you're all over the vulnerabilities, on top keeping everything up-to-date, and committed to making it work properly with things like enterprise wildcard certs, etc.  But when you take on that responsibility and instead deploy the PlaySkool version of SSL that still isn't fixed almost a year later....let's just say it doesn't exactly inspire confidence.

                      Anyway....I'm going to post the POODLE vulnerability issue as a separate thread, since FMS v13 is indeed answering to SSL v3 and we need a way to turn that off.

                      • 8. Re: SHA-2 based digital certificates do not work.
                        NickLowe

                        Yes, it is definitely a separate issue - I listed a few others above previously. Prima facie, the support from FileMaker for FM13 relating to HTTPS (TLS) is dysfunctional or indifferent and it is worrying.

                        I did contact FileMaker support in the UK who completely misunderstood and confused the issues, I gave up...

                        Perhaps, as a subsidiary of Apple, we should try contacting the Apple security team if FileMaker lack the in-house expertise?

                        • 9. Re: SHA-2 based digital certificates do not work.
                          JohnDCCIU

                          Actually, I finally did some more reading and researching this morning and it appears that FMI is using Apache on OS X, but they're installing their own version, in /Library/FileMaker Server/HTTPServer/ (thanks, TSFalcon!).

                          So it's not clear why there's all this nonsense (including FMS Support telling me "Nope, can't do it, not nohow") with not supporting wildcard certs and SHA-2, etc.  Maybe you can't do it with the built-in PlaySkool fmsadmin CERTIFICATE command, but seems like you could do what you want:  it's Apache.

                          To test this, I poked around in there and found that the SSL functionality is controlled in an Apache config include file, namely /Library/FileMaker Server/HTTPServer/conf/extra/httpd-ssl.conf  I edited that file with TextWrangler and applied the POODLE mitigation (adding "-SSLv3" on the end of the existing "SSLProtocol" line), restarted the server, and poof:  no more POODLE vulnerability.  You can test your server's POODLE vulnerability at http://whodig.com/poodle/ or for a more comprehensive test (including POODLE), try https://www.ssllabs.com/ssltest/

                           

                          • 10. Re: SHA-2 based digital certificates do not work.
                            atsushimatsuo

                            Knowledge Base Article #11413 has been updated. FileMaker Pro 13.0v4 and FileMaker Go 13.0.6 support SHA-2 SSL certs.

                            • 11. Re: SHA-2 based digital certificates do not work.
                              atsushimatsuo

                              FileMaker Pro 13.0v4 and FileMaker Go 13.0.6 can't connect to FileMaker Server 13.0v5 which installed SSL certificate "Entrust Advantage SSL with SHA256 (under SHA-1 Root)" and enabled SSL/TLS of FileMaker Network sharing. This certificate was issued last week.

                              Recently (this month or last month?) Entrust has changed the intermediate certificate authority for SHA-2. Please investigate and fix.
                              I think an intermediate certificate should be on the server (not on the client).

                              • 12. Re: SHA-2 based digital certificates do not work.
                                TSGal

                                Atsushi Matsuo:

                                Thank you for your posts.

                                I have sent your request to our Development and Testing departments for review.  When I receive any feedback, I will let you know.

                                TSGal
                                FileMaker, Inc.

                                • 13. Re: SHA-2 based digital certificates do not work.
                                  TSGal

                                  Atsushi Matsuo:

                                  Our Testing department contacted Entrust and verified both the Root "Entrust.net Certification Authority (2048)" SHA1 and Chain certificate "Entrust Certification Authority - L1C" SHA2 for the "Advantage" have not changed at this time.

                                  The testers would like you to run the certutil to dump the contents of the certificate file out:

                                  C:\certutil -dump (path to returned cert) >c:\entrust_cert.txt

                                  Testing would also like the Intermediate chain certificate.  You can get this from the SSL section in the accounts management page.

                                  Ensure that the download certificate was downloaded properly.  Testing is only concerned with the part about:

                                  ----BEGIN CERTIFICATE ----

                                  ----END CERTIFICATE ----

                                  http://www.entrust.net/knowledge-base/technote.cfm?tn=7563

                                  TSGal
                                  FileMaker, Inc.

                                  • 14. Re: SHA-2 based digital certificates do not work.
                                    atsushimatsuo

                                    Thank you for your response.

                                    Our server certificate (SHA-2) was issued by the intermediate CA "Entrust Certification Authority - L1K" (not "L1C") last month.

                                    Recently and usually almost all intermediate certificate needs to be installed on the server.
                                    Our web server works well because Apache HTTP Server has the "SSLCertificateChainFile" directive.

                                    But, I'm unable to install an intermediate certificate on our server using fmsadmin CERTIFICATE IMPORT command.
                                    And FileMaker Pro and Go have intermediate certificates inside. These are very odd.

                                    1 2 3 Previous Next