[jira] [Commented] (PROTON-716) Reject SSL clients that attempt to use SSLv3

2014-10-15 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172907#comment-14172907 ] ASF subversion and git services commented on PROTON-716: Commit 16

[jira] [Commented] (PROTON-716) Reject SSL clients that attempt to use SSLv3

2014-10-15 Thread Ken Giusti (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172881#comment-14172881 ] Ken Giusti commented on PROTON-716: --- Reviewboard: https://reviews.apache.org/r/26773/

[jira] [Assigned] (PROTON-716) Reject SSL clients that attempt to use SSLv3

2014-10-15 Thread Ken Giusti (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-716: - Assignee: Ken Giusti > Reject SSL clients that attempt to use SSLv3 > ---

[jira] [Created] (PROTON-716) Reject SSL clients that attempt to use SSLv3

2014-10-15 Thread Ken Giusti (JIRA)
Ken Giusti created PROTON-716: - Summary: Reject SSL clients that attempt to use SSLv3 Key: PROTON-716 URL: https://issues.apache.org/jira/browse/PROTON-716 Project: Qpid Proton Issue Type: Bug

VOTE: Release Proton 0.8 RC3 as 0.8 final

2014-10-15 Thread Rafael Schloming
Hi Everyone, As usual the call for a formal vote flushed out a few last minute issues, so here is a quick respin with the following items fixed. - PROTON-708 - PROTON-711 (fixed for Java6) - PROTON-712 - PROTON-714 - PROTON-715 The sources can be found at the usual location: http:

[jira] [Resolved] (PROTON-676) proton-c: transport layer SSL failures not propagated back to Messenger in pni_connection_readable

2014-10-15 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-676. Resolution: Fixed > proton-c: transport layer SSL failures not propagated back to Me

[jira] [Resolved] (PROTON-708) C proton driver needs a getter function to access the pn_error so it can be cleared

2014-10-15 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-708. Resolution: Fixed Fix Version/s: 0.8 > C proton driver needs a getter functio

[jira] [Commented] (PROTON-708) C proton driver needs a getter function to access the pn_error so it can be cleared

2014-10-15 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172492#comment-14172492 ] ASF subversion and git services commented on PROTON-708: Commit 16

[jira] [Assigned] (PROTON-708) C proton driver needs a getter function to access the pn_error so it can be cleared

2014-10-15 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reassigned PROTON-708: -- Assignee: Rafael H. Schloming > C proton driver needs a getter function to acce

[jira] [Resolved] (PROTON-715) [contrib/proton-jms] delivery-count is set incorrectly during Native outbound transformation

2014-10-15 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-715. --- Resolution: Fixed > [contrib/proton-jms] delivery-count is set incorrectly during Native outbo

[jira] [Resolved] (PROTON-712) Seg fault due to missing NULL return value check of getprotobyname

2014-10-15 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-712. Resolution: Fixed Fix Version/s: 0.8 > Seg fault due to missing NULL return v

[jira] [Commented] (PROTON-712) Seg fault due to missing NULL return value check of getprotobyname

2014-10-15 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172473#comment-14172473 ] ASF subversion and git services commented on PROTON-712: Commit 16

[jira] [Commented] (PROTON-715) [contrib/proton-jms] delivery-count is set incorrectly during Native outbound transformation

2014-10-15 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172472#comment-14172472 ] ASF subversion and git services commented on PROTON-715: Commit 16

[jira] [Updated] (PROTON-715) [contrib/proton-jms] delivery-count is set incorrectly during Native outbound transformation

2014-10-15 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-715: -- Description: In the proton-jms contrib artifact, delivery-count is set incorrectly (based on JM

[jira] [Created] (PROTON-715) [contrib/proton-jms] delivery-count is set incorrectly during Native outbound transformation

2014-10-15 Thread Robbie Gemmell (JIRA)
Robbie Gemmell created PROTON-715: - Summary: [contrib/proton-jms] delivery-count is set incorrectly during Native outbound transformation Key: PROTON-715 URL: https://issues.apache.org/jira/browse/PROTON-715

Re: SASL / non SASL connections...

2014-10-15 Thread Clebert Suconic
On Oct 15, 2014, at 11:09 AM, Robbie Gemmell wrote: > What Ted already implemented on the C side would enable what you are > seeking, allowing the server to be configured (depending on your security > configuration; some wouldnt want the without-sasl case to ever work, other > may allow it in no

[jira] [Assigned] (PROTON-712) Seg fault due to missing NULL return value check of getprotobyname

2014-10-15 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reassigned PROTON-712: -- Assignee: Rafael H. Schloming > Seg fault due to missing NULL return value chec

Re: SASL / non SASL connections...

2014-10-15 Thread Robbie Gemmell
What Ted already implemented on the C side would enable what you are seeking, allowing the server to be configured (depending on your security configuration; some wouldnt want the without-sasl case to ever work, other may allow it in no-auth scenarios) to accept either the sasl or non sasl header a

Re: SASL / non SASL connections...

2014-10-15 Thread Clebert Suconic
I think you should have an event for SASL_NEGOTATION.. or any name you chose.. then you could negotiate it properly. I don't think it would be too hard to implement. The clients I'm working don't know how to negotiate ANONYMOUS. All the Java clients I'm dealing with now will throw a bad NPE if

[jira] [Commented] (PROTON-714) SSL buffer overflow with large frames

2014-10-15 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172325#comment-14172325 ] ASF subversion and git services commented on PROTON-714: Commit 16

[jira] [Commented] (PROTON-714) SSL buffer overflow with large frames

2014-10-15 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172322#comment-14172322 ] Rafael H. Schloming commented on PROTON-714: >From an email thread: I am deve

[jira] [Created] (PROTON-714) SSL buffer overflow with large frames

2014-10-15 Thread Rafael H. Schloming (JIRA)
Rafael H. Schloming created PROTON-714: -- Summary: SSL buffer overflow with large frames Key: PROTON-714 URL: https://issues.apache.org/jira/browse/PROTON-714 Project: Qpid Proton Issue T

[jira] [Created] (PROTON-713) TransportImpl#setChannelMax does not enforce legal value range, may cause unexpected results

2014-10-15 Thread Robbie Gemmell (JIRA)
Robbie Gemmell created PROTON-713: - Summary: TransportImpl#setChannelMax does not enforce legal value range, may cause unexpected results Key: PROTON-713 URL: https://issues.apache.org/jira/browse/PROTON-713

Re: SASL / non SASL connections...

2014-10-15 Thread Robbie Gemmell
Hi Clebert, As a little extra context for readers...with AMQP 1.0, if the client wishes to use SASL security it first establishes a SASL layer beginning with the AMQP%d3.1.0.0 header, and then if successfull proceed to establish the 'regular' AMQP connection over it beginning with the AMQP%d0.1.0.