Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-27

Windows: private key before PEM certificate causes Segfault

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • JWS 3.0.0 GA, JWS 3.0.1 DR1, JWS 3.0.1 ER1, JWS 3.0.2 DR2, JWS 3.0.3 DR3
    • httpd
    • None
    • Release Notes
    • Hide
      On Microsoft Windows, sending a request via a mod_proxy reverse proxy to a https backend results in a segfault. Using `gdb` shows that having the private key before the certificate in `SSLProxyMachineCertificateFile` triggers the segfault.

      This is a known issue in JBoss Web Server 3 and is currently under investigation.
      Show
      On Microsoft Windows, sending a request via a mod_proxy reverse proxy to a https backend results in a segfault. Using `gdb` shows that having the private key before the certificate in `SSLProxyMachineCertificateFile` triggers the segfault. This is a known issue in JBoss Web Server 3 and is currently under investigation.
    • Documented as Known Issue

    Description

      Can you check if we have patch for https://bugzilla.redhat.com/show_bug.cgi?id=968389 private key before PEM certificate causes Segfault in JWS30 httpd24 for MS Windows ?

      The httpd24 error_log on MS Windows from this BZ test:

      Starting the httpd service
      The httpd service is running.
      t configured for SSL proxy (missing or encrypted private key?)
      [Thu Feb 26 08:23:33.723861 2015] [ssl:emerg] [pid 5680:tid 484] AH02312: Fatal error initialising mod_ssl, exiting.
      

      Attachments

        Issue Links

          Activity

            People

              gzaronik@redhat.com George Zaronikas
              lfuka Libor Fuka
              Bogdan Sikora Bogdan Sikora (Inactive)
              Lucas Costi Lucas Costi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: