> But most applications will share the same config file settings, at least > as far as ENGINEs are concerned. > > It isn't really appropriate to provide a function to set the config file > location. OPENSSL_config() is meant as a simple solution for existing > applications and it does rather horrible things (like writing error > messages to standard output and calling exit(1) for fatal errors). An > application could provide more appropriate behaviour using the > CONF_modules_load_file() (which OPENSSL_config() calls). > > Steve. > --
The problem is that on Windows there is rarely a single version of OpenSSL installed. There is the version that I use in Kermit 95; there is the version that Time Warner ships with Road Runner; there is another version that is part of some other terminal emulator that is on my system. If there is only one single config file there are bound to be problems if multiple versions are compiled with different options. It would seem that (at least on windows) the concept of a config file is a bad idea. Even so, there is a serious question on Windows of where such a file would be placed. In the old days one would simply dump the file in the %SystemRoot% directory (C:\WINDOWS). However, under current practice this would not be permitted as the %SystemRoot% tree should not be writeable. It would be possible to define some standard practices for the installation of OpenSSL on Windows. In order for us to do that I believe we would need to provide a standard binary distribution and installer. As well as specify a set of rules for use. Jeffrey Altman * Sr.Software Designer C-Kermit 8.0 available now!!! The Kermit Project @ Columbia University includes Telnet, FTP and HTTP http://www.kermit-project.org/ secured with Kerberos, SRP, and [EMAIL PROTECTED] OpenSSL. Interfaces with OpenSSH ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
