Hi,
Huge regards for your efforts. I am wee bit taking more time as I am also looking out for other options like using some SSL-supportive intermediaries; > http://svwe10.itex.at/downloads/mod_auth_mysql/ I used the updated source and now the error has become SSL connection specific. -------------- [Tue May 01 11:15:58 2007] [error] [client 192.168.1.17] MOD_AUTH_MYSQL: MYSQL ERROR: SSL connection error :: connect to DB [Tue May 01 11:15:58 2007] [error] [client 192.168.1.17] host (localhost.localdomain) not found in db [Tue May 01 11:15:58 2007] [crit] [client 192.168.1.17] configuration error: couldn't check user. No user file?: / -------------- > I'm just also hacking in the module, and I see this few lines above the > mysql connect: > > if (!conf->db_host || strcmp(conf->db_host,"localhost") == 0 || > strcmp(conf->db_host,"127.0.0.1") == 0) { > db_host = NULL; > db_port = 0; > } else { > db_host = conf->db_host; > db_port = conf->db_port; > } > > > I think its now mandatory that you access the mysql server from another > host than localhost to make sure you really establish a TCPIP > connection... I am still using the same box to for mysql server and my accessing code. Moreover I am using my box's IP in conf->db_host. conf->db_host = "192.168.x.x"; Will not this allow a TCPIP connection? What about skipping this part of the code at least for now? What would you suggest, should I really have to access mysql from some other host? The updates contain 5 new directives for SSL and ciphers. How these new directives can be set in httpd.conf like other AuthMySql* directives ? > and then I found a bug report related to this option: > http://bugs.mysql.com/bug.php?id=24121 I suppose this fixing at my end would need me to recompile my mysql. AM I RIGHT HERE? Thanks again, Naveen
