qpid ssl environment var's
by Adam Stokes
little history..
QPID_SSL_CERT_DB and QPID_SSL_CERT_PASSWORD_FILE need to be set in order to make the broker load the sslconnector library and provide us with SSL capabilities during communication. Unfortunately, there is no command level way to set these options and so we are looking at alternatives.
So far:
1) setting the variables QPID_SSL_CERT_DB and QPID_SSL_CERT_PASSWORD_FILE with setenv() prior to making the amqp connection. The broker failed to see variables
2) Placing them in /etc/qpid/qpidc.conf, I thought this may work but did not have luck. There is code for checking at least the cert database in qpid.
3) Prior to running any agents, brokers, prepend QPID_SSL_CERT_DB and QPID_SSL_CERT_PASSWORD_FILE on the commandline. works.
Other options may be to set them in an initscript or maybe some configuration items in our own matahari.conf
thoughts?
--
__ __
.-----.| |_.-----.| |--.-----.-----.
|__ --|| _| _ || <| -__|__ --|
|_____||____|_____||__|__|_____|_____|
.----------------------------------.
( ajs(a)redhat.com || 919.754.4187 )
`----------------------------------'
13 years
asprintf changes
by Andrew Beekhof
commit cd96dcdd620e08c879d91bea895432e1d6394360
Author: Russell Bryant <russell(a)russellbryant.net>
Date: Sat Mar 26 14:04:18 2011 -0500
Misc cleanups in src/lib/services.c.
...
3) Use asprintf() instead of a malloc() + snprintf().
We'll have to revert this I'm afraid... asprintf() isn't available
when cross compiling.
Not really your fault, we haven't been able to cross compile on fedora
for a while (fixed now).
-- Andrew
13 years