[jira] [Commented] (PROTON-988) pn_messenger_set_flags does not support new SASL flag correctly

[ https://issues.apache.org/jira/browse/PROTON-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737538#comment-14737538 ] Andrew Stitcher commented on PROTON-988: It probably doesn't matter here much, but it's not good

[jira] [Commented] (PROTON-988) pn_messenger_set_flags does not support new SASL flag correctly

[ https://issues.apache.org/jira/browse/PROTON-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737502#comment-14737502 ] Andrew Stitcher commented on PROTON-988: I think, on balance, (at the cost of making more noise

[jira] [Resolved] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython

[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-952. Resolution: Fixed Building Proton with python 2.6 and python 3.4 on Travis CI finds and

[jira] [Commented] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

[ https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682291#comment-14682291 ] Andrew Stitcher commented on PROTON-978: As far as I can tell this will happen on

[jira] [Commented] (PROTON-975) crash occurs if buffer containing outcome and first encrypted frame is received

[ https://issues.apache.org/jira/browse/PROTON-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14663247#comment-14663247 ] Andrew Stitcher commented on PROTON-975: I've looked into this a bit now: *Good

[jira] [Updated] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-969: --- Fix Version/s: (was: 0.11) Cyrus SASL module calls sasl_server_init once for every

[jira] [Comment Edited] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652380#comment-14652380 ] Andrew Stitcher edited comment on PROTON-950 at 8/3/15 8:00 PM:

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652413#comment-14652413 ] Andrew Stitcher commented on PROTON-950: Also what are you doing when receiving

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652357#comment-14652357 ] Andrew Stitcher commented on PROTON-950: [~gsim] Could you bug report that last

[jira] [Comment Edited] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652415#comment-14652415 ] Andrew Stitcher edited comment on PROTON-950 at 8/3/15 8:16 PM:

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652448#comment-14652448 ] Andrew Stitcher commented on PROTON-950: To be clear: * The client mechanisms

[jira] [Commented] (PROTON-970) SASL options for setting path and name should not be transport-specific

[ https://issues.apache.org/jira/browse/PROTON-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648223#comment-14648223 ] Andrew Stitcher commented on PROTON-970: This is more-or-less the same as

[jira] [Commented] (PROTON-970) SASL options for setting path and name should not be transport-specific

[ https://issues.apache.org/jira/browse/PROTON-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648226#comment-14648226 ] Andrew Stitcher commented on PROTON-970: From an API stand point I believe that

[jira] [Commented] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648268#comment-14648268 ] Andrew Stitcher commented on PROTON-969: I'm pretty sure this isn't a blocker. The

[jira] [Assigned] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-969: -- Assignee: Andrew Stitcher Cyrus SASL module calls sasl_server_init once for every

[jira] [Commented] (PROTON-923) [SASL] PN_TRANSPORT_ERROR event not raised

[ https://issues.apache.org/jira/browse/PROTON-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644471#comment-14644471 ] Andrew Stitcher commented on PROTON-923: This is the issue for raising the correct

[jira] [Created] (PROTON-963) [SASL] Raise PN_TRANSPORT_ERROR events with correct condition for authentication failure

Andrew Stitcher created PROTON-963: -- Summary: [SASL] Raise PN_TRANSPORT_ERROR events with correct condition for authentication failure Key: PROTON-963 URL: https://issues.apache.org/jira/browse/PROTON-963

[jira] [Updated] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-950: --- Description: In the current 0.10 alpha, if SASL PLAIN is selected, it will only work if the

[jira] [Resolved] (PROTON-960) On error Proton can send an open and a close frame during the SASL negotiation (before sending the AMQP header)

[ https://issues.apache.org/jira/browse/PROTON-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-960. Resolution: Fixed Fix Version/s: 0.10 On error Proton can send an open and a close

[jira] [Resolved] (PROTON-959) On error Proton can send an open and a close frame before sending the AMQP header

[ https://issues.apache.org/jira/browse/PROTON-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-959. Resolution: Fixed Fix Version/s: 0.10 On error Proton can send an open and a close

[jira] [Resolved] (PROTON-963) [SASL] Raise PN_TRANSPORT_ERROR events with correct condition for authentication failure

[ https://issues.apache.org/jira/browse/PROTON-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-963. Resolution: Fixed [SASL] Raise PN_TRANSPORT_ERROR events with correct condition for

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644675#comment-14644675 ] Andrew Stitcher commented on PROTON-950: This can only be a change in behaviour

[jira] [Comment Edited] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644842#comment-14644842 ] Andrew Stitcher edited comment on PROTON-950 at 7/28/15 6:49 PM:

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644842#comment-14644842 ] Andrew Stitcher commented on PROTON-950: I don't understand - the previous code

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644849#comment-14644849 ] Andrew Stitcher commented on PROTON-950: Given that the 0.10 version of the Python

[jira] [Commented] (PROTON-923) [SASL] PN_TRANSPORT_ERROR event not raised

[ https://issues.apache.org/jira/browse/PROTON-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643485#comment-14643485 ] Andrew Stitcher commented on PROTON-923: I can't reproduce this bug with the

[jira] [Updated] (PROTON-959) On error Proton can send an open and a close frame before sending the AMQP header

[ https://issues.apache.org/jira/browse/PROTON-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-959: --- Description: In the following trace of some transport tests you will see that many of the

[jira] [Created] (PROTON-959) On error Proton can send an open and a close frame before sending the AMQP header

Andrew Stitcher created PROTON-959: -- Summary: On error Proton can send an open and a close frame before sending the AMQP header Key: PROTON-959 URL: https://issues.apache.org/jira/browse/PROTON-959

[jira] [Created] (PROTON-960) On error Proton can send an open and a close frame during the SASL negotiation (before sending the AMQP header)

Andrew Stitcher created PROTON-960: -- Summary: On error Proton can send an open and a close frame during the SASL negotiation (before sending the AMQP header) Key: PROTON-960 URL:

[jira] [Created] (PROTON-953) Travis CI tox tests fail to correctly build python 2.6 extension lib

Andrew Stitcher created PROTON-953: -- Summary: Travis CI tox tests fail to correctly build python 2.6 extension lib Key: PROTON-953 URL: https://issues.apache.org/jira/browse/PROTON-953 Project: Qpid

[jira] [Updated] (PROTON-953) Travis CI tox tests fail to correctly build python 2.6 extension lib

[ https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-953: --- Assignee: Ken Giusti Travis CI tox tests fail to correctly build python 2.6 extension lib

[jira] [Updated] (PROTON-953) Travis CI tox tests fail to correctly build python 2.6 extension lib

[ https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-953: --- Description: In the current Travis CI build the tox tests fail to correctly build the python

[jira] [Comment Edited] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython

[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633992#comment-14633992 ] Andrew Stitcher edited comment on PROTON-952 at 7/21/15 4:30 PM:

[jira] [Commented] (PROTON-941) pn_transport_set_server should fail if invoked after binding.

[ https://issues.apache.org/jira/browse/PROTON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622493#comment-14622493 ] Andrew Stitcher commented on PROTON-941: I think that starts next week!

[jira] [Commented] (PROTON-941) pn_transport_set_server should fail if invoked after binding.

[ https://issues.apache.org/jira/browse/PROTON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622503#comment-14622503 ] Andrew Stitcher commented on PROTON-941: Agreed. Incidentally The python binding

[jira] [Created] (PROTON-934) Build tests fail if Java is not available

Andrew Stitcher created PROTON-934: -- Summary: Build tests fail if Java is not available Key: PROTON-934 URL: https://issues.apache.org/jira/browse/PROTON-934 Project: Qpid Proton Issue

[jira] [Updated] (PROTON-201) Provide a C++ Messenger and Message class

[ https://issues.apache.org/jira/browse/PROTON-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-201: --- Assignee: Cliff Jansen (was: Andrew Stitcher) Provide a C++ Messenger and Message class

[jira] [Created] (PROTON-933) Cyrus SASL GSSAPI plugin can error if sent long buffers.

Andrew Stitcher created PROTON-933: -- Summary: Cyrus SASL GSSAPI plugin can error if sent long buffers. Key: PROTON-933 URL: https://issues.apache.org/jira/browse/PROTON-933 Project: Qpid Proton

[jira] [Resolved] (PROTON-933) Cyrus SASL GSSAPI plugin can error if sent long buffers.

[ https://issues.apache.org/jira/browse/PROTON-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-933. Resolution: Fixed Fix Version/s: 0.10 Cyrus SASL GSSAPI plugin can error if sent

[jira] [Commented] (PROTON-201) Provide a C++ Messenger and Message class

[ https://issues.apache.org/jira/browse/PROTON-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615620#comment-14615620 ] Andrew Stitcher commented on PROTON-201: [~cliffjansen], I believe this is

[jira] [Resolved] (PROTON-911) Implement SASL security layer

[ https://issues.apache.org/jira/browse/PROTON-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-911. Resolution: Implemented Fix Version/s: 0.10 Except for bug fixing, this is now

[jira] [Resolved] (PROTON-929) [SASL] If both client and server specify ANONYMOUS mech connection setup does not complete

[ https://issues.apache.org/jira/browse/PROTON-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-929. Resolution: Fixed [SASL] If both client and server specify ANONYMOUS mech connection setup

[jira] [Created] (PROTON-918) Jython interop tests failing since e38957ae5115

Andrew Stitcher created PROTON-918: -- Summary: Jython interop tests failing since e38957ae5115 Key: PROTON-918 URL: https://issues.apache.org/jira/browse/PROTON-918 Project: Qpid Proton

[jira] [Commented] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14591729#comment-14591729 ] Andrew Stitcher commented on PROTON-915: The current implementation will send AMQP

[jira] [Commented] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590432#comment-14590432 ] Andrew Stitcher commented on PROTON-915: Assigned to [~rhs] for comment on spec

[jira] [Updated] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-915: --- Assignee: Rafael H. Schloming (was: Andrew Stitcher) Incompatible protocol header handled

[jira] [Updated] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-915: --- Attachment: 0001-PROTON-915-Send-correct-AMQP-header-upon-protocol-mi.patch Putative fix for

[jira] [Commented] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590430#comment-14590430 ] Andrew Stitcher commented on PROTON-915: I have a fix for this now - try the

[jira] [Commented] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590772#comment-14590772 ] Andrew Stitcher commented on PROTON-915: I've now committed the patch, with fixes

[jira] [Resolved] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-915. Resolution: Fixed Incompatible protocol header handled incorrectly

[jira] [Commented] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590579#comment-14590579 ] Andrew Stitcher commented on PROTON-915: [~gemmellr] I think this was a deliberate

[jira] [Commented] (PROTON-915) Incompatible protocol header handled incorrectly

[ https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590056#comment-14590056 ] Andrew Stitcher commented on PROTON-915: A reproducer script would be nice.

[jira] [Created] (PROTON-909) Tests for new SASL features and mechanisms

Andrew Stitcher created PROTON-909: -- Summary: Tests for new SASL features and mechanisms Key: PROTON-909 URL: https://issues.apache.org/jira/browse/PROTON-909 Project: Qpid Proton Issue

[jira] [Assigned] (PROTON-909) Tests for new SASL features and mechanisms

[ https://issues.apache.org/jira/browse/PROTON-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-909: -- Assignee: Andrew Stitcher Tests for new SASL features and mechanisms

[jira] [Created] (PROTON-910) Proton-J SASL implementation should support new SASL APIs

Andrew Stitcher created PROTON-910: -- Summary: Proton-J SASL implementation should support new SASL APIs Key: PROTON-910 URL: https://issues.apache.org/jira/browse/PROTON-910 Project: Qpid Proton

[jira] [Assigned] (PROTON-911) Implement SASL security layer

[ https://issues.apache.org/jira/browse/PROTON-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-911: -- Assignee: Andrew Stitcher Implement SASL security layer

[jira] [Resolved] (PROTON-866) Implement SASL external with TLS client authentication

[ https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-866. Resolution: Fixed Fix Version/s: 0.10 Implement SASL external with TLS client

[jira] [Commented] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

[ https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582476#comment-14582476 ] Andrew Stitcher commented on PROTON-867: It would be helpful to the user if there

[jira] [Comment Edited] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

[ https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582476#comment-14582476 ] Andrew Stitcher edited comment on PROTON-867 at 6/11/15 8:28 PM:

[jira] [Resolved] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

[ https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-867. Resolution: Fixed Fix Version/s: 0.10 This issue has been resolved with the changes

[jira] [Created] (PROTON-911) Implement SASL security layer

Andrew Stitcher created PROTON-911: -- Summary: Implement SASL security layer Key: PROTON-911 URL: https://issues.apache.org/jira/browse/PROTON-911 Project: Qpid Proton Issue Type: Sub-task

[jira] [Commented] (PROTON-344) Need Ruby version of msgr-send/msgr-recv tools

[ https://issues.apache.org/jira/browse/PROTON-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14569559#comment-14569559 ] Andrew Stitcher commented on PROTON-344: Note that all these commits are actually

[jira] [Created] (PROTON-887) Windows SSL implementation needs working version of pn_ssl_get_remote_subject()

Andrew Stitcher created PROTON-887: -- Summary: Windows SSL implementation needs working version of pn_ssl_get_remote_subject() Key: PROTON-887 URL: https://issues.apache.org/jira/browse/PROTON-887

[jira] [Commented] (PROTON-885) Allow setup.py to bundle qpid-proton

[ https://issues.apache.org/jira/browse/PROTON-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542256#comment-14542256 ] Andrew Stitcher commented on PROTON-885: [~flaper87] Just eyeballing the patch it

[jira] [Resolved] (PROTON-562) More gracefully handle connections to non-1.0 parties

[ https://issues.apache.org/jira/browse/PROTON-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-562. Resolution: Fixed The misleading error messages are no longer present, and the underlying

[jira] [Updated] (PROTON-562) More gracefully handle connections to non-1.0 parties

[ https://issues.apache.org/jira/browse/PROTON-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-562: --- Fix Version/s: (was: 0.10) 0.9 More gracefully handle connections to

[jira] [Resolved] (PROTON-877) proton-c sasl client hangs on server pipeline

[ https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-877. Resolution: Fixed proton-c sasl client hangs on server pipeline

[jira] [Resolved] (PROTON-868) Make Pipelined ANONYMOUS authentication work with fallback SASL implementation

[ https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-868. Resolution: Fixed Fix Version/s: 0.10 Make Pipelined ANONYMOUS authentication work

[jira] [Resolved] (PROTON-879) null initial response makes cyrus challenge when it probably shouldn't

[ https://issues.apache.org/jira/browse/PROTON-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-879. Resolution: Fixed null initial response makes cyrus challenge when it probably shouldn't

[jira] [Updated] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

[ https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-867: --- Description: Currently PLAIN is never offered by Proton acting as a server because the SASL

[jira] [Commented] (PROTON-877) proton-c sasl client hangs on server pipeline

[ https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526709#comment-14526709 ] Andrew Stitcher commented on PROTON-877: [~rhs] could you give some more context

[jira] [Assigned] (PROTON-875) Proton-C SASL changes break windows self tests

[ https://issues.apache.org/jira/browse/PROTON-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-875: -- Assignee: Andrew Stitcher Proton-C SASL changes break windows self tests

[jira] [Commented] (PROTON-875) Proton-C SASL changes break windows self tests

[ https://issues.apache.org/jira/browse/PROTON-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523247#comment-14523247 ] Andrew Stitcher commented on PROTON-875: This is the symptom of fallback ANONYMOUS

[jira] [Closed] (PROTON-875) Proton-C SASL changes break windows self tests

[ https://issues.apache.org/jira/browse/PROTON-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher closed PROTON-875. -- Resolution: Duplicate Proton-C SASL changes break windows self tests

[jira] [Created] (PROTON-868) Make Pipelined ANONYMOUS authentication work with fallback SASL implementation

Andrew Stitcher created PROTON-868: -- Summary: Make Pipelined ANONYMOUS authentication work with fallback SASL implementation Key: PROTON-868 URL: https://issues.apache.org/jira/browse/PROTON-868

[jira] [Commented] (PROTON-866) Implement SASL external with TLS client authentication

[ https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14511873#comment-14511873 ] Andrew Stitcher commented on PROTON-866: Amongst other things this will require

[jira] [Assigned] (PROTON-866) Implement SASL external with TLS client authentication

[ https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-866: -- Assignee: Andrew Stitcher Implement SASL external with TLS client authentication

[jira] [Created] (PROTON-866) Implement SASL external with TLS client authentication

Andrew Stitcher created PROTON-866: -- Summary: Implement SASL external with TLS client authentication Key: PROTON-866 URL: https://issues.apache.org/jira/browse/PROTON-866 Project: Qpid Proton

[jira] [Assigned] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

[ https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-867: -- Assignee: Andrew Stitcher Enable PLAIN SASL mech iff connection is encrypted

[jira] [Created] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

Andrew Stitcher created PROTON-867: -- Summary: Enable PLAIN SASL mech iff connection is encrypted Key: PROTON-867 URL: https://issues.apache.org/jira/browse/PROTON-867 Project: Qpid Proton

[jira] [Resolved] (PROTON-859) cyrus sasl not compatible with pre 2.1.24 versions

[ https://issues.apache.org/jira/browse/PROTON-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-859. Resolution: Fixed Fix Version/s: 0.10 cyrus sasl not compatible with pre 2.1.24

[jira] [Updated] (PROTON-862) Proton using Cyrus SASL library is problematic because the library has global state

[ https://issues.apache.org/jira/browse/PROTON-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-862: --- Description: The Cyrus SASL library is not 100% suitable for use in other libraries because

[jira] [Created] (PROTON-862) Proton using Cyrus SASL library is problematic because the library has global state

Andrew Stitcher created PROTON-862: -- Summary: Proton using Cyrus SASL library is problematic because the library has global state Key: PROTON-862 URL: https://issues.apache.org/jira/browse/PROTON-862

[jira] [Commented] (PROTON-334) SASL Implementation for Proton C

[ https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486890#comment-14486890 ] Andrew Stitcher commented on PROTON-334: Link to the work on github:

[jira] [Updated] (PROTON-334) SASL Implementation for Proton C

[ https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-334: --- Summary: SASL Implementation for Proton C (was: SASL Plug-in for Proton) SASL

[jira] [Commented] (PROTON-334) SASL Plug-in for Proton

[ https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335443#comment-14335443 ] Andrew Stitcher commented on PROTON-334: Link to documentation on this work:

[jira] [Resolved] (PROTON-823) Proton prints some log/trace information to stdout/stderr.

[ https://issues.apache.org/jira/browse/PROTON-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-823. Resolution: Fixed Proton prints some log/trace information to stdout/stderr.

[jira] [Resolved] (PROTON-804) the transport doesn't always shutdown its output properly

[ https://issues.apache.org/jira/browse/PROTON-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-804. Resolution: Fixed Fix Version/s: 0.9 the transport doesn't always shutdown its

[jira] [Commented] (PROTON-808) Binaries have their library locations stripped

[ https://issues.apache.org/jira/browse/PROTON-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318808#comment-14318808 ] Andrew Stitcher commented on PROTON-808: The stack overflow discussion is somewhat

[jira] [Commented] (PROTON-808) Binaries have their library locations stripped

[ https://issues.apache.org/jira/browse/PROTON-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14319157#comment-14319157 ] Andrew Stitcher commented on PROTON-808: The risk is putting a generally

[jira] [Commented] (PROTON-808) Binaries have their library locations stripped

[ https://issues.apache.org/jira/browse/PROTON-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14319208#comment-14319208 ] Andrew Stitcher commented on PROTON-808: Privileged executable = executable run as

[jira] [Commented] (PROTON-804) the transport doesn't always shutdown its output properly

[ https://issues.apache.org/jira/browse/PROTON-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317031#comment-14317031 ] Andrew Stitcher commented on PROTON-804: I believe I have a fix for this problem,

[jira] [Commented] (PROTON-804) the transport doesn't always shutdown its output properly

[ https://issues.apache.org/jira/browse/PROTON-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317027#comment-14317027 ] Andrew Stitcher commented on PROTON-804: I believe that the test case is in error:

[jira] [Commented] (PROTON-791) c-reactor-tests fails because it listens to an IPv4 socket but connects to an IPv6 socket

[ https://issues.apache.org/jira/browse/PROTON-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266135#comment-14266135 ] Andrew Stitcher commented on PROTON-791: Ah the specified addresses will be the

[jira] [Commented] (PROTON-791) c-reactor-tests fails because it listens to an IPv4 socket but connects to an IPv6 socket

[ https://issues.apache.org/jira/browse/PROTON-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266273#comment-14266273 ] Andrew Stitcher commented on PROTON-791: I think using IPv4 is likely to be more

[jira] [Created] (PROTON-791) c-reactor-tests fails because it listens to an IPv4 socket but connects to an IPv6 socket

Andrew Stitcher created PROTON-791: -- Summary: c-reactor-tests fails because it listens to an IPv4 socket but connects to an IPv6 socket Key: PROTON-791 URL: https://issues.apache.org/jira/browse/PROTON-791

[jira] [Created] (PROTON-790) Use git tag for release (rather than branch)

Andrew Stitcher created PROTON-790: -- Summary: Use git tag for release (rather than branch) Key: PROTON-790 URL: https://issues.apache.org/jira/browse/PROTON-790 Project: Qpid Proton Issue

[jira] [Commented] (PROTON-790) Use git tag for release (rather than branch)

[ https://issues.apache.org/jira/browse/PROTON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257581#comment-14257581 ] Andrew Stitcher commented on PROTON-790: In the current tree {code}git tag

[jira] [Commented] (PROTON-790) Use git tag for release (rather than branch)

[ https://issues.apache.org/jira/browse/PROTON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257582#comment-14257582 ] Andrew Stitcher commented on PROTON-790: Another benefit of using tags is that

[jira] [Resolved] (PROTON-750) Have distinct API to indicate SSL layer is not really implemented

[ https://issues.apache.org/jira/browse/PROTON-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-750. Resolution: Fixed Fix Version/s: 0.9 Have distinct API to indicate SSL layer is not

<    1   2   3   4   >