You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Steve Huston (JIRA)" <ji...@apache.org> on 2012/06/08 23:41:23 UTC
[jira] [Created] (QPID-4049) Linux C++ broker crashes when Windows
client connects SSL with expired certificate
Steve Huston created QPID-4049:
----------------------------------
Summary: 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
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)]
0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
(gdb) where
#0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
#1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
#2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
#3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
#4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
() from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
#5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
#6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4049) Linux C++ broker crashes when
Windows client connects SSL with expired certificate
Posted by "Steve Huston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293693#comment-13293693 ]
Steve Huston commented on QPID-4049:
------------------------------------
My apologies - you are correct. I found this error on Friday on trunk.
> 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4049) Linux C++ broker crashes when Windows
client connects SSL with expired certificate
Posted by "Andrew Stitcher (JIRA)" <ji...@apache.org>.
[ 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4049) Linux C++ broker crashes when
Windows client connects SSL with expired certificate
Posted by "Andrew Stitcher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293688#comment-13293688 ]
Andrew Stitcher commented on QPID-4049:
---------------------------------------
Steve - can you confirm this happens with 0.16? That doesn't sound correct to me as the code that prints the "no protocol received closing" message is on trunk only and after the 0.16 branch.
> 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4049) Linux C++ broker crashes when
Windows client connects SSL with expired certificate
Posted by "Andrew Stitcher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293695#comment-13293695 ]
Andrew Stitcher commented on QPID-4049:
---------------------------------------
Aargh, this looks like yet another place where we've fixed a bug only in one set of cut-and-paste code.
Alan fixed this bug for TCP in r1343397, but didn't fix the ssl code.
> 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4049) Linux C++ broker crashes when Windows
client connects SSL with expired certificate
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4049) Linux C++ broker crashes when
Windows client connects SSL with expired certificate
Posted by "Andrew Stitcher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295351#comment-13295351 ]
Andrew Stitcher commented on QPID-4049:
---------------------------------------
Fixed now in r1350406
> 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
> Labels: cut-n-paste-error
> 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Resolved] (QPID-4049) Linux C++ broker crashes when Windows
client connects SSL with expired certificate
Posted by "Andrew Stitcher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Stitcher resolved QPID-4049.
-----------------------------------
Resolution: Fixed
> 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
> Labels: cut-n-paste-error
> 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Assigned] (QPID-4049) Linux C++ broker crashes when Windows
client connects SSL with expired certificate
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim reassigned QPID-4049:
--------------------------------
Assignee: Andrew Stitcher
> 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
> 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)]
> 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> (gdb) where
> #0 0x00002aaaac0d9164 in qpid::sys::ssl::ProtocolTimeoutTask::fire() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/ssl.so
> #1 0x00002aaaab51c7bc in qpid::sys::TimerTask::fireTask() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #2 0x00002aaaab51c952 in qpid::sys::Timer::fire(boost::intrusive_ptr<qpid::sys::TimerTask>) ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #3 0x00002aaaab51d22d in qpid::sys::Timer::run() ()
> from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #4 0x00002aaaab4a9e74 in qpid::sys::(anonymous namespace)::runRunnable(void*)
> () from /qpidbuilds/trunk/qpid/cpp/rhel5/src/libqpidcommon.so.2.0.0
> #5 0x000000318f60677d in start_thread () from /lib64/libpthread.so.0
> #6 0x000000318eed325d 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org