Re: Two Way authentication - Urgent Help
Already imported your client.p12 into firefox? http://www.utexas.edu/its/help/user-certs/817 Il 16/giu/2014 00:22 Grip In gripic...@gmail.com ha scritto: Getting An error occurred during a connection to localhost:8443. SSL peer cannot verify your certificate. (Error code: ssl_error_bad_cert_alert) In firefox on windows 7 with tomcat 7 Here is what I did as per http://tomcat.10.x6.nabble.com/tomcat-mutual-authentication-doesn-t-work-td2133404.html#a5018750 1. keytool.exe -genkeypair -keystore tomcat.keystore 2. keytool.exe -genkeypair -keystore client.keystore 3a. keytool.exe -exportcert -keystore client.keystore -file client.cert 3b. keytool.exe -importcert -keystore server.truststore -file client.cert 4. keytool.exe -importkeystore -srckeystore client.keystore -srcstoretype jks -destkeystore client.p12 -deststoretype pkcs12 keytool.exe -list -keystore tomcat.keystore Enter keystore password: Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry mykey, Jun 16, 2014, PrivateKeyEntry, Certificate fingerprint (SHA1): E7:5E:F8:1F:BC:24:96:E2:D6:87:BF:3A:94:CD:53:14:C6:0E:A6:A5 keytool.exe -list -keystore server.truststore Enter keystore password: Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry mykey, Jun 16, 2014, trustedCertEntry, Certificate fingerprint (SHA1): 81:C9:BF:20:E9:D8:18:7E:E5:F7:54:B1:68:0B:00:65:DB:13:8E:52 My server.xml enteries are Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true keystoreFile=path\tomcat.keystore keystorePass=tomcat truststorefile=path\server.truststore truststorepass=client maxThreads=1500 scheme=https secure=true clientAuth=true sslProtocol=TLS / My tomcat user enteries are user username=CN=Server, OU=Gripic, O=TechnoPotence, L=Pune, ST=MH, C=IN password=null roles=admin/ But could not get the resolution Please help urgent.
Re: mod_jk 1.2.27 stack smashing detected on centos
I have Apache/2.2.15 (Unix) mod_jk/1.2.37 PHP/5.3.3 Apache, and PHP are installed via RPM (centos packages), while mod_jk was compiled from source. Subject says 1.2.27 and above says 1.2.37. I assume 1.2.37 is correct but please check. Yes, I'm sorry. It's a typo. I have jk 1.2.37. In any case, can you re-test with 1.2.40, and make sure that debugging symbols are included in the build? OK, thanks. I'll schedule a module recompilation with debug symbols. Thank you! -- Dino Ciuffetti Linux System Administrator and Architect TuxWeb S.r.l. - http://www.tuxweb.it/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
mod_jk 1.2.27 stack smashing detected on centos
Hi there. My name is Dino Ciuffetti, I'm a linux sysadmin and I'm new to this list. I have a sporadic problem with mod_jk (tomcat connectors), I hope someone can help me on this. I have Apache/2.2.15 (Unix) mod_jk/1.2.37 PHP/5.3.3 Apache, and PHP are installed via RPM (centos packages), while mod_jk was compiled from source. I have sporadic segmentation fault and stack smashing detected errors on my error_log: [Mon May 26 11:03:31 2014] [notice] child pid 59191 exit signal Segmentation fault (11) [Mon May 26 11:03:36 2014] [notice] child pid 57331 exit signal Segmentation fault (11) *** stack smashing detected ***: /usr/sbin/httpd.worker terminated === Backtrace: = /lib64/libc.so.6(__fortify_fail+0x37)[0x7fa19ef57507] /lib64/libc.so.6(__fortify_fail+0x0)[0x7fa19ef574d0] /etc/httpd/modules/mod_jk.so(jk_open_socket+0xa3e)[0x7fa19bd0796e] /etc/httpd/modules/mod_jk.so(ajp_connect_to_endpoint+0x65)[0x7fa19bd25405] /etc/httpd/modules/mod_jk.so(+0x32900)[0x7fa19bd25900] /etc/httpd/modules/mod_jk.so(+0x35952)[0x7fa19bd28952] /etc/httpd/modules/mod_jk.so(+0x1f96a)[0x7fa19bd1296a] /etc/httpd/modules/mod_jk.so(+0xd869)[0x7fa19bd00869] /usr/sbin/httpd.worker(ap_run_handler+0x70)[0x7fa1a0945530] /usr/sbin/httpd.worker(ap_invoke_handler+0xce)[0x7fa1a0948dee] /usr/sbin/httpd.worker(ap_process_request+0x1c0)[0x7fa1a09541f0] /usr/sbin/httpd.worker(+0x38068)[0x7fa1a0951068] /usr/sbin/httpd.worker(ap_run_process_connection+0x68)[0x7fa1a094d038] /usr/sbin/httpd.worker(+0x40f02)[0x7fa1a0959f02] /lib64/libpthread.so.0(+0x7851)[0x7fa19f1ef851] /lib64/libc.so.6(clone+0x6d)[0x7fa19ef3d90d] Reading the backtrace, it seems to me that there is something with jk_open_socket() that is causing the stack smashing protection check to fire. We have those errors only on high loads. Anyone have something similar? I cannot find fixed bugs like this on newer versions (bugzilla). Thank you. -- Dino Ciuffetti Linux System Administrator and Architect TuxWeb S.r.l. - http://www.tuxweb.it/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
