Oh, I found a solution. pn_sasl(pn_transport_t *transport);
Tomas 2015-07-30 10:41 GMT+02:00 Tomáš Šoltys <tomas.sol...@gmail.com>: > Hi, > > I see there is a new function pn_sasl_set_allow_insecure_mechs(pn_sasl_t > *sasl, bool insecure) > > Is there a way how I can get an access to "pn_sasl_t *sasl" object? > > Regards, > Tomas > > 2015-07-28 20:55 GMT+02:00 ASF subversion and git services (JIRA) < > j...@apache.org>: > >> >> [ >> https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644850#comment-14644850 >> ] >> >> ASF subversion and git services commented on PROTON-950: >> -------------------------------------------------------- >> >> Commit c954cf3e4f35e79a6cd5832cc977d136c607a20b in qpid-proton's branch >> refs/heads/master from [~astitcher] >> [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=c954cf3 ] >> >> PROTON-950: Allow PLAIN over clear text if you ask nicely >> >> >> > SASL PLAIN over cleartext should be supported >> > --------------------------------------------- >> > >> > Key: PROTON-950 >> > URL: https://issues.apache.org/jira/browse/PROTON-950 >> > Project: Qpid Proton >> > Issue Type: Bug >> > Components: proton-c >> > Affects Versions: 0.10 >> > Reporter: Ted Ross >> > Assignee: Andrew Stitcher >> > Priority: Blocker >> > Fix For: 0.10 >> > >> > >> > In the current 0.10 alpha, if SASL PLAIN is selected, it will only work >> if the connection is encrypted (using SSL). This is a surprising change of >> behavior from earlier versions of Proton and it's arguable that a security >> policy like that should be left to the application using the Proton library. >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >> > > > > -- > Tomáš Šoltys > tomas.sol...@gmail.com > http://www.range-software.com > (+420) 776-843-663 > -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663
