[jira] [Updated] (QPID-4049) Linux C++ broker crashes when Windows client connects SSL with expired certificate

2012-06-12 Thread Gordon Sim (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gordon Sim updated QPID-4049:
-

 Priority: Critical  (was: Major)
Fix Version/s: 0.17

 Linux C++ broker crashes when Windows client connects SSL with expired 
 certificate
 --

 Key: QPID-4049
 URL: https://issues.apache.org/jira/browse/QPID-4049
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.16
 Environment: Linux
Reporter: Steve Huston
Assignee: Andrew Stitcher
Priority: Critical
 Fix For: 0.17


 Testing Windows client - Linux broker SSL connections. The SSL cert is 
 expired and this results in the following on Linux:
 2012-06-08 17:08:12 error Error reading socket: Encountered end of file 
 [-5938]
 2012-06-08 17:08:14 error Connection 192.168.10.4:5671-192.168.10.40:60748 No 
 protocol received closing
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0x40a00940 (LWP 15265)]
 0x2c0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
 (gdb) where
 #0  0x2c0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
 #1  0x2b51c7bc in qpid::sys::TimerTask::fireTask() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #2  0x2b51c952 in 
 qpid::sys::Timer::fire(boost::intrusive_ptrqpid::sys::TimerTask) ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #3  0x2b51d22d in qpid::sys::Timer::run() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #4  0x2b4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
 () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #5  0x00318f60677d in start_thread () from /lib64/libpthread.so.0
 #6  0x00318eed325d in clone () from /lib64/libc.so.6
 (gdb) 
 On Windows, this error looks like:
 2012-06-08 17:07:06 notice SSL negotiation failed to smokey:5671: The 
 received certificate has expired.
 2012-06-08 17:07:06 warning Connect failed: The received certificate has 
 expired
 .  (..\..\..\..\cpp\src\qpid\client\windows\SslConnector.cpp:111)
 2012-06-08 17:07:06 warning Connection [192.168.10.40:60748-smokey:5671] 
 closed
 Connection [192.168.10.40:60748-smokey:5671] closed
 E:\

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPID-4049) Linux C++ broker crashes when Windows client connects SSL with expired certificate

2012-06-12 Thread Andrew Stitcher (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher updated QPID-4049:
--

Affects Version/s: (was: 0.16)
   0.17

 Linux C++ broker crashes when Windows client connects SSL with expired 
 certificate
 --

 Key: QPID-4049
 URL: https://issues.apache.org/jira/browse/QPID-4049
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.17
 Environment: Linux
Reporter: Steve Huston
Assignee: Andrew Stitcher
Priority: Critical
 Fix For: 0.17


 Testing Windows client - Linux broker SSL connections. The SSL cert is 
 expired and this results in the following on Linux:
 2012-06-08 17:08:12 error Error reading socket: Encountered end of file 
 [-5938]
 2012-06-08 17:08:14 error Connection 192.168.10.4:5671-192.168.10.40:60748 No 
 protocol received closing
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0x40a00940 (LWP 15265)]
 0x2c0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
 (gdb) where
 #0  0x2c0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
 #1  0x2b51c7bc in qpid::sys::TimerTask::fireTask() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #2  0x2b51c952 in 
 qpid::sys::Timer::fire(boost::intrusive_ptrqpid::sys::TimerTask) ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #3  0x2b51d22d in qpid::sys::Timer::run() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #4  0x2b4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
 () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
 #5  0x00318f60677d in start_thread () from /lib64/libpthread.so.0
 #6  0x00318eed325d in clone () from /lib64/libc.so.6
 (gdb) 
 On Windows, this error looks like:
 2012-06-08 17:07:06 notice SSL negotiation failed to smokey:5671: The 
 received certificate has expired.
 2012-06-08 17:07:06 warning Connect failed: The received certificate has 
 expired
 .  (..\..\..\..\cpp\src\qpid\client\windows\SslConnector.cpp:111)
 2012-06-08 17:07:06 warning Connection [192.168.10.40:60748-smokey:5671] 
 closed
 Connection [192.168.10.40:60748-smokey:5671] closed
 E:\

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org