You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Petr Matousek (JIRA)" <ji...@apache.org> on 2015/06/12 19:52:02 UTC
[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)