Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Let's say you have a web app and you distribute an embedded Apache HTTPD with that web app. It's difficult to manage customers that want to run SSL. The best way appears to be to let the customer manage installing SSL certificates on the embedded Apache -- or to recommend the customer use a front-end SSL accelerator card or pizza box.

Are there better ways of doing this?

share|improve this question
up vote 1 down vote accepted

You've pretty much covered it. SSL requires the user install valid certs. The best you can do is give them good instructions on how to do so.

share|improve this answer

One option I've seen on embedded systems that's potentially easier to configure than using Apache's built-in support for SSL is stunnel.

It handles all of the SSL layer, and then communicates with the local web server over the loopback interface.

If the only reason to run Apache is to get SSL support, this can provide a way of running an alternate HTTP server with a smaller footprint.

share|improve this answer
Currently, we use Apache HTTPD for multiple purposes, but I'll keep stunnel in mind in case it fits a future use. Thanks. – Eddie May 4 '09 at 22:57

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.