You are viewing a plain text version of this content. The canonical link for it is here.

Posted to wiki-changes@httpd.apache.org by Apache Wiki <wi...@apache.org> on 2010/02/10 19:25:58 UTC

[Httpd Wiki] Update of "NameBasedSSLVHostsWithSNI" by YK

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.

The "NameBasedSSLVHostsWithSNI" page has been changed by YK.
The comment on this change is: 0.9.8k has enable-tlsext.
http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI?action=diff&rev1=6&rev2=7

--------------------------------------------------

  == Prerequisites to use SNI ==
  
   * Use OpenSSL 0.9.8f or later
-  * Build OpenSSL with the TLS Extensions option enabled (option enable-tlsext; OpenSSL 0.9.9 might have this enabled by default).
+  * Build OpenSSL with the TLS Extensions option enabled (option enable-tlsext; OpenSSL 0.9.8k and later has this enabled by default).
   * Apache must have been built with that OpenSSL (./configure --with-ssl=/path/to/your/openssl).  In that case, mod_ssl will automatically detect the availability of the TLS extensions and support SNI.
   * Apache must use that OpenSSL at run-time, which might require setting LD_LIBRARY_PATH or equivalent to point to that OpenSSL, maybe in bin/envvars.  (You'll get unresolved symbol errors at Apache startup if Apache was built with SNI but isn't finding the right openssl libraries at run-time.)