DO NOT REPLY [Bug 45763] No openssl.cnf defined by default causes OpenSSL commands to fail

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=45763



--- Comment #1 from Gregg L. Smith <li...@glewis.com> 2009-08-31 12:09:02 PDT ---
Wow, this is one year old next week. I can answer this one in two parts for
you.

1. This is a simple fix as you point, but it has to be done at compile time and
therefore is *set in stone*, which leads to #2

2. The .msi installer from Apache.org allows you to put Apache anywhere your
heart desires (last time I gave it a try), or just accept it's default. For
most the default is fine, but I'd imagine, like me, people get tired of the
super long path when working with configuration files and over time have come
to put Apache in another place. Well, the developers cannot read your, mine or
everyone elses mind to know exactly where that file is going to land on the
file system once installed, thus the problem.

If they compile Openssl to look in C:/Program Files/Apache Software
Foundation/Apache2.2/conf (which wouldn't be a bad idea) but you install Apache
in C:/Apache2.2, you are right back to the same problem again.

As far as /usr/local/ssl/, that is where the OpenSSL people decided was the
default location, if not change during compile, that is where it looks. 

Both of these software packages are first and foremost Unix, that is where it
all started. Over time they have been ported to Windows, so most likely that is
why the default path is just that, a unix path.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org