[jira] [Updated] (PROTON-913) Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault
[ https://issues.apache.org/jira/browse/PROTON-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-913: -- Component/s: proton-c Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault Key: PROTON-913 URL: https://issues.apache.org/jira/browse/PROTON-913 Project: Qpid Proton Issue Type: Bug Components: proton-c, python-binding Affects Versions: 0.9.1 Environment: packages: qpid-proton-c-0.9-3 qpid-proton-c-devel-0.9-3 python-qpid-proton-0.9-3 Reporter: Petr Matousek Assignee: Gordon Sim Priority: Minor Fix For: 0.10 Attachments: ssl_client_allow_unsecured_client.py, stacktrace.txt Calling allow_unsecured_client() on SSLDomain.CLIENT_MODE object causes client segmentation fault. It is not intended to call this method on client instance, but obviously the client segfault should not appear. Please see the attached reproducer ssl_client_allow_unsecured_client.py for details. Attaching also client traces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-913) Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault
[ https://issues.apache.org/jira/browse/PROTON-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-913: - Attachment: ssl_client_allow_unsecured_client.py reproducer Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault Key: PROTON-913 URL: https://issues.apache.org/jira/browse/PROTON-913 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9.1 Environment: packages: qpid-proton-c-0.9-3 qpid-proton-c-devel-0.9-3 python-qpid-proton-0.9-3 Reporter: Petr Matousek Priority: Minor Attachments: ssl_client_allow_unsecured_client.py Calling allow_unsecured_client() on SSLDomain.CLIENT_MODE object causes client segmentation fault. It is not intended to call this method on client instance, but obviously the client segfault should not appear. Please see the attached reproducer ssl_client_allow_unsecured_client.py for details. Attaching also client traces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-913) Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault
[ https://issues.apache.org/jira/browse/PROTON-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-913: - Attachment: stacktrace.txt client stack trace Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault Key: PROTON-913 URL: https://issues.apache.org/jira/browse/PROTON-913 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9.1 Environment: packages: qpid-proton-c-0.9-3 qpid-proton-c-devel-0.9-3 python-qpid-proton-0.9-3 Reporter: Petr Matousek Priority: Minor Attachments: ssl_client_allow_unsecured_client.py, stacktrace.txt Calling allow_unsecured_client() on SSLDomain.CLIENT_MODE object causes client segmentation fault. It is not intended to call this method on client instance, but obviously the client segfault should not appear. Please see the attached reproducer ssl_client_allow_unsecured_client.py for details. Attaching also client traces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
