Hi list, I ask for help please.
I have an apache server (2.0.59) built with OpenSSL 0.9.8b, it hosts a
python (2.4.4) based application (Edgewall's trac) wich access a PostgreSQL
SSL-secured server (8.2.3) throught DBI libraries (pyPgSQL/Psycopg2).
When I use directly trac (it has a lightweight server, tracd), it works with
no problems.
But when I use it throught apache2+mod_python, apache shows HTTP 500:
{{{
# error_log, using pyPgSQL
[Thu Apr 05 19:25:43 2007] [error] [client 192.168.2.52]
DatabaseError: SSL error: cipher or hash unavailable\n
[Thu Apr 05 19:25:43 2007] [debug] ssl_engine_kernel.c(1787): OpenSSL:
Write: SSL negotiation finished successfully
[Thu Apr 05 19:25:43 2007] [info] Connection to child 4 closed with
standard shutdown(server PCDCOM:443, client 192.168.2.52)
}}}
{{{
# error_log, using Psycopg2
[Mon Apr 09 22:03:32 2007] [error] [client 192.168.2.52]
OperationalError: SSL error: cipher or hash unavailable\n
[Mon Apr 09 22:03:33 2007] [debug] ssl_engine_kernel.c(1787): OpenSSL:
Write: SSL negotiation finished successfully
[Mon Apr 09 22:03:33 2007] [info] Connection to child 1 closed with
standard shutdown(server PCDCOM:443, client 192.168.2.52)
}}}
What does it really mean '''cipher or hash unavailable'''? (SSL Error
#138,SSL_R_CIPHER_OR_HASH_UNAVAILABLE).
The only thing I can guess is that ''apache2+mod_python'' (client-app role)
fails to access PostgreSQL+SSL (server role). Must be a missconfiguration in
apache2.
How do I configure Apache2 properly, to act as a SSL client, I have no
problem acting as SSL server role.
For a more detailed info, visit:
http://groups.google.com/group/trac-users/browse_thread/thread/901ef327b448b496?hl=en
Thanks,
Johans Marvin Taboada Villca
