[jira] [Closed] (PROTON-758) proton-c: assertion failure when SASL fails (PN_SASL_FAIL)

[ https://issues.apache.org/jira/browse/PROTON-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher closed PROTON-758. -- Resolution: Fixed Fix Version/s: 0.10 I think this is almost certainly fixed by the new S

[jira] [Resolved] (PROTON-1083) [C++] Simplify the messaging events

[ https://issues.apache.org/jira/browse/PROTON-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1083. - Resolution: Fixed > [C++] Simplify the messaging events > ---

[jira] [Created] (PROTON-1083) [C++] Simplify the messaging events

Andrew Stitcher created PROTON-1083: --- Summary: [C++] Simplify the messaging events Key: PROTON-1083 URL: https://issues.apache.org/jira/browse/PROTON-1083 Project: Qpid Proton Issue Type: I

[jira] [Comment Edited] (PROTON-1055) Username sent twice during SASL AUTH

[ https://issues.apache.org/jira/browse/PROTON-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018133#comment-15018133 ] Andrew Stitcher edited comment on PROTON-1055 at 11/20/15 3:12 PM:

[jira] [Commented] (PROTON-1055) Username sent twice during SASL AUTH

[ https://issues.apache.org/jira/browse/PROTON-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018133#comment-15018133 ] Andrew Stitcher commented on PROTON-1055: - Looking at the proton sasl code I see

[jira] [Commented] (PROTON-949) proton doesn't build with ccache swig

[ https://issues.apache.org/jira/browse/PROTON-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997122#comment-14997122 ] Andrew Stitcher commented on PROTON-949: I approve this fix for the 0.11 release

[jira] [Assigned] (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:all-tabpanel ] Andrew Stitcher reassigned PROTON-988: -- Assignee: Andrew Stitcher > pn_messenger_set_flags does not support new SASL flag corre

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875683#comment-14875683 ] Andrew Stitcher commented on PROTON-992: This is a fair point. It's worth noting

[jira] [Assigned] (PROTON-996) Allow Messenger API to set the allowed auth mechs

[ https://issues.apache.org/jira/browse/PROTON-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-996: -- Assignee: Andrew Stitcher > Allow Messenger API to set the allowed auth mechs > ---

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802937#comment-14802937 ] Andrew Stitcher commented on PROTON-992: Upon a few days reflection I've realised

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741422#comment-14741422 ] Andrew Stitcher commented on PROTON-992: cyrus is essentially a posix only library

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741144#comment-14741144 ] Andrew Stitcher commented on PROTON-992: I don't disagree, but remember that addin

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739538#comment-14739538 ] Andrew Stitcher commented on PROTON-992: You have missed the mutex use - it is act

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739534#comment-14739534 ] Andrew Stitcher commented on PROTON-992: The problem with introducing a per-proces

[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&focusedCommentId=14737538#comment-14737538 ] Andrew Stitcher commented on PROTON-988: It probably doesn't matter here much, but

[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&focusedCommentId=14737502#comment-14737502 ] Andrew Stitcher commented on PROTON-988: I think, on balance, (at the cost of maki

[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&focusedCommentId=14737269#comment-14737269 ] Andrew Stitcher commented on PROTON-988: Oh, D'oh I just realised what you mean h

[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&focusedCommentId=14737257#comment-14737257 ] Andrew Stitcher commented on PROTON-988: In looking at the code for on_messenger_s

[jira] [Commented] (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-tabpanel&focusedCommentId=14695989#comment-14695989 ] Andrew Stitcher commented on PROTON-952: It may be a "cmake bug" in that cmake doe

[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 li

[jira] [Reopened] (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 reopened PROTON-952: Assignee: Andrew Stitcher (was: Ken Giusti) > Building Proton with python 2.6 and python

[jira] [Updated] (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 updated PROTON-952: --- Fix Version/s: 0.11 > Building Proton with python 2.6 and python 3.4 on Travis CI finds and li

[jira] [Created] (PROTON-979) build tests fail if Cyrus SASL otp mech is installed

Andrew Stitcher created PROTON-979: -- Summary: build tests fail if Cyrus SASL otp mech is installed Key: PROTON-979 URL: https://issues.apache.org/jira/browse/PROTON-979 Project: Qpid Proton

[jira] [Resolved] (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:all-tabpanel ] Andrew Stitcher resolved PROTON-978. Resolution: Fixed > Framing errors after SASL exchange when max-frame-size is configured > -

[jira] [Commented] (PROTON-949) proton doesn't build with ccache swig

[ https://issues.apache.org/jira/browse/PROTON-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682465#comment-14682465 ] Andrew Stitcher commented on PROTON-949: mailing list message with some info: http

[jira] [Resolved] (PROTON-974) single symbol for mechanisms in sasl-mechanisms not recognised

[ https://issues.apache.org/jira/browse/PROTON-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-974. Resolution: Fixed Fix Version/s: 0.11 0.10.1 > single symbol for m

[jira] [Resolved] (PROTON-975) connecting with DIGEST-MD5 fails 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:all-tabpanel ] Andrew Stitcher resolved PROTON-975. Resolution: Fixed > connecting with DIGEST-MD5 fails if buffer containing outcome and first

[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-tabpanel&focusedCommentId=14682291#comment-14682291 ] Andrew Stitcher commented on PROTON-978: As far as I can tell this will happen on

[jira] [Resolved] (PROTON-899) Unnecessary relative path in include

[ https://issues.apache.org/jira/browse/PROTON-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-899. Resolution: Fixed > Unnecessary relative path in include > -

[jira] [Commented] (PROTON-899) Unnecessary relative path in include

[ https://issues.apache.org/jira/browse/PROTON-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682137#comment-14682137 ] Andrew Stitcher commented on PROTON-899: Interesting - I noticed this issue some t

[jira] [Assigned] (PROTON-899) Unnecessary relative path in include

[ https://issues.apache.org/jira/browse/PROTON-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-899: -- Assignee: Andrew Stitcher > Unnecessary relative path in include >

[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-tabpanel&focusedCommentId=14663247#comment-14663247 ] Andrew Stitcher commented on PROTON-975: I've looked into this a bit now: *Good n

[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-tabpanel&focusedCommentId=14658574#comment-14658574 ] Andrew Stitcher commented on PROTON-969: I've changed the fix in and priority of t

[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: --- Priority: Minor (was: Major) > Cyrus SASL module calls sasl_server_init once for every incomi

[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 incom

[jira] [Commented] (PROTON-974) single symbol for mechanisms in sasl-mechanisms not recognised

[ https://issues.apache.org/jira/browse/PROTON-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654199#comment-14654199 ] Andrew Stitcher commented on PROTON-974: This is an issue in the new Proton-C SASL

[jira] [Resolved] (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 resolved PROTON-950. Resolution: Fixed Fix Version/s: 0.11 Currently the change to the default behaviour o

[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-tabpanel&focusedCommentId=14652448#comment-14652448 ] Andrew Stitcher commented on PROTON-950: To be clear: * The client mechanisms ava

[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-tabpanel&focusedCommentId=14652428#comment-14652428 ] Andrew Stitcher commented on PROTON-950: It should be raising .._HEAD_CLOSED, .._T

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=14652415#comment-14652415 ] Andrew Stitcher commented on PROTON-950: With no Cyrus available the behaviour sho

[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-tabpanel&focusedCommentId=14652413#comment-14652413 ] Andrew Stitcher commented on PROTON-950: Also what are you doing when receiving PN

[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-tabpanel&focusedCommentId=14652404#comment-14652404 ] Andrew Stitcher commented on PROTON-950: There was a recent change to stop the SAS

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=14652380#comment-14652380 ] Andrew Stitcher commented on PROTON-950: @gsim unless you've manually set the flag

[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-tabpanel&focusedCommentId=14652377#comment-14652377 ] Andrew Stitcher commented on PROTON-950: As to the first issue - it is possible th

[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-tabpanel&focusedCommentId=14652357#comment-14652357 ] Andrew Stitcher commented on PROTON-950: [~gsim] Could you bug report that last is

[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-tabpanel&focusedCommentId=14649511#comment-14649511 ] Andrew Stitcher commented on PROTON-941: I removed the fix target as I don't belie

[jira] [Updated] (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:all-tabpanel ] Andrew Stitcher updated PROTON-941: --- Fix Version/s: (was: 0.10) > pn_transport_set_server should fail if invoked after binding.

[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-tabpanel&focusedCommentId=14649352#comment-14649352 ] Andrew Stitcher commented on PROTON-969: This is true, but not all that relevant t

[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 inc

[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-tabpanel&focusedCommentId=14648268#comment-14648268 ] Andrew Stitcher commented on PROTON-969: I'm pretty sure this isn't a blocker. The

[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: --- Priority: Major (was: Blocker) > Cyrus SASL module calls sasl_server_init once for every inco

[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-tabpanel&focusedCommentId=14648226#comment-14648226 ] Andrew Stitcher commented on PROTON-970: >From an API stand point I believe that d

[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-tabpanel&focusedCommentId=14648223#comment-14648223 ] Andrew Stitcher commented on PROTON-970: This is more-or-less the same as PROTON-8

[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-tabpanel&focusedCommentId=14648105#comment-14648105 ] Andrew Stitcher commented on PROTON-950: At this point I don't think master is blo

[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-tabpanel&focusedCommentId=14644849#comment-14644849 ] Andrew Stitcher commented on PROTON-950: Given that the 0.10 version of the Python

[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-tabpanel&focusedCommentId=14644842#comment-14644842 ] Andrew Stitcher edited comment on PROTON-950 at 7/28/15 6:49 PM: ---

[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-tabpanel&focusedCommentId=14644842#comment-14644842 ] Andrew Stitcher edited comment on PROTON-950 at 7/28/15 6:48 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-tabpanel&focusedCommentId=14644842#comment-14644842 ] Andrew Stitcher commented on PROTON-950: I don't understand - the previous code di

[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-tabpanel&focusedCommentId=14644822#comment-14644822 ] Andrew Stitcher commented on PROTON-950: Did the 0.9 Python "Reactive" API code se

[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-tabpanel&focusedCommentId=14644675#comment-14644675 ] Andrew Stitcher commented on PROTON-950: This can only be a change in behaviour fo

[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 co

[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 > aut

[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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=14643485#comment-14643485 ] Andrew Stitcher commented on PROTON-923: I can't reproduce this bug with the curre

[jira] [Commented] (PROTON-961) messenger doesn't handle multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642833#comment-14642833 ] Andrew Stitcher commented on PROTON-961: Is there a test for large messages? I'm g

[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: https://issues.apache.org/jira/br

[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 tes

[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 P

[jira] [Updated] (PROTON-951) Make install fails when building Proton-C with python 3.4

[ https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-951: --- Description: When building proton-C using a python 3.4 virtualenv make install fails: {noforma

[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-tabpanel&focusedCommentId=14633992#comment-14633992 ] Andrew Stitcher edited comment on PROTON-952 at 7/21/15 4:30 PM: ---

[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] [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] [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-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 updated PROTON-952: --- Assignee: Ken Giusti > Building Proton with python 2.6 and python 3.4 on Travis CI finds and l

[jira] [Updated] (PROTON-951) Make install fails when building Proton-C with python 3.4

[ https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-951: --- Assignee: Ken Giusti > Make install fails when building Proton-C with python 3.4 > ---

[jira] [Commented] (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-tabpanel&focusedCommentId=14633992#comment-14633992 ] Andrew Stitcher commented on PROTON-952: Build log for python 3.4 (2.6 is similar)

[jira] [Commented] (PROTON-951) Make install fails when building Proton-C with python 3.4

[ https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633983#comment-14633983 ] Andrew Stitcher commented on PROTON-951: This may not have been noticed before bec

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

Andrew Stitcher created PROTON-952: -- Summary: Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython Key: PROTON-952 URL: https://issues.apache.org/jira/browse/PROTON-952

[jira] [Updated] (PROTON-951) Make install fails when building Proton-C with python 3.4

[ https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-951: --- Attachment: py34fail Attached Output from "make install" > Make install fails when building P

[jira] [Created] (PROTON-951) Make install fails when building Proton-C with python 3.4

Andrew Stitcher created PROTON-951: -- Summary: Make install fails when building Proton-C with python 3.4 Key: PROTON-951 URL: https://issues.apache.org/jira/browse/PROTON-951 Project: Qpid Proton

[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-tabpanel&focusedCommentId=14622503#comment-14622503 ] Andrew Stitcher commented on PROTON-941: Agreed. Incidentally The python binding

[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-tabpanel&focusedCommentId=14622493#comment-14622493 ] Andrew Stitcher commented on PROTON-941: I think that starts next week! > pn_tran

[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-tabpanel&focusedCommentId=14615620#comment-14615620 ] Andrew Stitcher commented on PROTON-201: [~cliffjansen], I believe this is include

[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-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 Type:

[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 lo

[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-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 implem

[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 Issue

[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-tabpanel&focusedCommentId=14591729#comment-14591729 ] Andrew Stitcher commented on PROTON-915: The current implementation will send AMQP

[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-tabpanel&focusedCommentId=14590772#comment-14590772 ] Andrew Stitcher commented on PROTON-915: I've now committed the patch, with "fixes

[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-tabpanel&focusedCommentId=14590579#comment-14590579 ] Andrew Stitcher commented on PROTON-915: [~gemmellr] I think this was a deliberate

[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 i

<    1   2   3   4   5   >