installation problem with openSSL - please help (part 2)
We forgot to attach the httpsd.conf with our previous message. Here we go again: Dear Fellow Netizens and OpenSSL Users, We have been trying to migrate from mod_ssl to openSSL for our latest Apache installation, and are encountering a number of problems which we'd be grateful for helpful comments from established users: 1) When we run "[...]/apache/src/make certificate" the process does not ask for a secret pass phrase as mod_ssl used to do. Is this normal behavior? 2) We can not get the configuration to support making just specified parts of our document tree subject to secure transmission -- it's all or nothing. For example, if we have the following in the Apache configuration file [...]/apache/conf/httpsd.conf: [...] Port 80 Listen 80 Listen 443 SSLEnable SSLRequireSSL [...] The entire htdoc tree requires SSL, not just the htdocs/manual. By this we mean that if we access a file using "http://..." the brower reports that the document contains no data, whereas if we access the same file via "https://..." the document is fully accessible. In contrast, if the file contains: SSLDisable then no documents require the use of SSL, and all are accessible via the "http://..." URL convention. If someone would be willing to make some rapid interations on this with us by email or phone (our call) we would be highy grateful. Thanks in advance for any help... Cheerio, Rick Rodgers ([EMAIL PROTECTED]) Kelley Hu Kelley Hu ([EMAIL PROTECTED]) U.S. National Library of Medicine, Computer Science Branch Bethesda, MD (301) 435-3205 [EMAIL PROTECTED] httpsd.conf
installation problem with openSSL - please help
Dear Fellow Netizens and OpenSSL Users, We have been trying to migrate from mod_ssl to openSSL for our latest Apache installation, and are encountering a number of problems which we'd be grateful for helpful comments from established users: 1) When we run "[...]/apache/src/make certificate" the process does not ask for a secret pass phrase as mod_ssl used to do. Is this normal behavior? 2) We can not get the configuration to support making just specified parts of our document tree subject to secure transmission -- it's all or nothing. For example, if we have the following in the Apache configuration file [...]/apache/conf/httpsd.conf: [...] Port 80 Listen 80 Listen 443 SSLEnable SSLRequireSSL [...] The entire htdoc tree requires SSL, not just the htdocs/manual. By this we mean that if we access a file using "http://..." the brower reports that the document contains no data, whereas if we access the same file via "https://..." the document is fully accessible. In contrast, if the file contains: SSLDisable then no documents require the use of SSL, and all are accessible via the "http://..." URL convention. If someone would be willing to make some rapid interations on this with us by email or phone (our call) we would be highy grateful. Thanks in advance for any help... Cheerio, Rick Rodgers ([EMAIL PROTECTED]) Kelley Hu Kelley Hu ([EMAIL PROTECTED]) U.S. National Library of Medicine, Computer Science Branch Bethesda, MD (301) 435-3205 [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]