If you're worried about the Heartbleed SSL issue the services stopped won't matter. If you've patched SSL, the patch will be applied when and if you do start them again.
I ungraded my openssl on sun solaris 8 from openssl 0.9.6c to openssl 0.9.6g the ungrade went
fine but when I tried to ssh in to server, I received the following error message
"ld.so.1: ./sshd: fatal: relocation error: file /usr/local/ssl/lib/libcrypto.so.0.9.6: symbol main: referenced symbol... (2 Replies)
Hi everybody:
here is my tale: I need to create some ssl certificates, so I did it with my Linux; I created de CA key and all the other stuff, and of course the certificates needed.
The thing is I had to replace mi hard drive and I backed up all the info but I forgot to backup the /etc/ssl.
Of... (0 Replies)
All,
I am new to openssl and I have not been able to figure out exactly how to use it. What I need to do is to create a shell script which FTPS's (SFTP is not allowed on my project) a file to a mainframe. The mainframe will not initiate a session with my server.
Question. Are the packages... (7 Replies)
Hi Peeps,
Having trouble compiling openssl 0.9.8r on Solaris 10 x86. The make test fails when running the shatests (segmentation faults). There is a PROBLEM file that references a file called values.c. Anyone know whereabouts in the source tree you put this file as the file doesn't tell you... (2 Replies)
Hi,
I have a web server running on Debian 6.0.4 in a computer outside my university, but the web URL is blocked by my university, the security group of the university said because it was scanning computers inside university.
I could not find any applications in my web server are doing... (3 Replies)
I just started playing around with Unix's OpenSSL utility. I can't seem to get the hang of it, and the man page isn't helping much. I wanted to experiment with file encryption, so I created a dummy text file with one line of text and tried to encrypt it using DES. I used the following command:
... (2 Replies)
We have a legacy HP-UX 11.11 server that has a number of security vulnerabilities associated with OpenSSL. We have a project in the works to replace this server but until then I need to deal with the vulnerabilities. No applications on the server utilize SSL, so my plan was to simply remove it. ... (8 Replies)
Discussion started by: jduehmig
8 Replies
LEARN ABOUT OSX
openssl_no_config
OPENSSL_config(3) OpenSSL OPENSSL_config(3)NAME
OPENSSL_config, OPENSSL_no_config - simple OpenSSL configuration functions
SYNOPSIS
#include <openssl/conf.h>
void OPENSSL_config(const char *config_name);
void OPENSSL_no_config(void);
DESCRIPTION
OPENSSL_config() configures OpenSSL using the standard openssl.cnf configuration file name using config_name. If config_name is NULL then
the default name openssl_conf will be used. Any errors are ignored. Further calls to OPENSSL_config() will have no effect. The
configuration file format is documented in the conf(5) manual page.
OPENSSL_no_config() disables configuration. If called before OPENSSL_config() no configuration takes place.
NOTES
It is strongly recommended that all new applications call OPENSSL_config() or the more sophisticated functions such as CONF_modules_load()
during initialization (that is before starting any threads). By doing this an application does not need to keep track of all configuration
options and some new functionality can be supported automatically.
It is also possible to automatically call OPENSSL_config() when an application calls OPENSSL_add_all_algorithms() by compiling an
application with the preprocessor symbol OPENSSL_LOAD_CONF #define'd. In this way configuration can be added without source changes.
The environment variable OPENSSL_CONF can be set to specify the location of the configuration file.
Currently ASN1 OBJECTs and ENGINE configuration can be performed future versions of OpenSSL will add new configuration options.
There are several reasons why calling the OpenSSL configuration routines is advisable. For example new ENGINE functionality was added to
OpenSSL 0.9.7. In OpenSSL 0.9.7 control functions can be supported by ENGINEs, this can be used (among other things) to load dynamic
ENGINEs from shared libraries (DSOs). However very few applications currently support the control interface and so very few can load and
use dynamic ENGINEs. Equally in future more sophisticated ENGINEs will require certain control operations to customize them. If an
application calls OPENSSL_config() it doesn't need to know or care about ENGINE control operations because they can be performed by editing
a configuration file.
Applications should free up configuration at application closedown by calling CONF_modules_free().
RESTRICTIONS
The OPENSSL_config() function is designed to be a very simple "call it and forget it" function. As a result its behaviour is somewhat
limited. It ignores all errors silently and it can only load from the standard configuration file location for example.
It is however much better than nothing. Applications which need finer control over their configuration functionality should use the
configuration functions such as CONF_load_modules() directly.
RETURN VALUES
Neither OPENSSL_config() nor OPENSSL_no_config() return a value.
SEE ALSO conf(5), CONF_load_modules_file(3), CONF_modules_free(3),CONF_modules_free(3)HISTORY
OPENSSL_config() and OPENSSL_no_config() first appeared in OpenSSL 0.9.7
0.9.8 2009-04-03 OPENSSL_config(3)