[jira] [Created] (PROTON-2011) dns based auto-meching function
Gordon Sim created PROTON-2011: -- Summary: dns based auto-meching function Key: PROTON-2011 URL: https://issues.apache.org/jira/browse/PROTON-2011 Project: Qpid Proton Issue Type: New Feature Reporter: Gordon Sim It would be useful to have a module in the router that would query dns record for a given address and use the results to set up inter-router connectors. When running in kubernetes this could then keep a group of routers connected based on a headless service over them. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1273) 'to' field not authorized against valid targets for anonymous sender
Gordon Sim created DISPATCH-1273:
Summary: 'to' field not authorized against valid targets for
anonymous sender
Key: DISPATCH-1273
URL: https://issues.apache.org/jira/browse/DISPATCH-1273
Project: Qpid Dispatch
Issue Type: Bug
Affects Versions: 1.5.0
Reporter: Gordon Sim
With following policy, attempts to attach a sender link to 'bar' will fail as
expected, but if an anonymous sender is attached and a message is sent to
'bar', it gets through.
{noformat}
[
["vhost",
{
"id": "$default",
"allowUnknownUser": true,
"groups": {
"$default" : {
"users": "*",
"remoteHosts": "*",
"allowDynamicSource": true,
"allowAnonymousSender": true,
"sources": "*",
"targets": "foo"
}
}
}
]
]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1232) Edge router test failing on RHEL6
[ https://issues.apache.org/jira/browse/DISPATCH-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779716#comment-16779716 ] ASF GitHub Bot commented on DISPATCH-1232: -- fgiorgetti commented on pull request #434: DISPATCH-1232 - Improved mechanism to identify openssl version installed URL: https://github.com/apache/qpid-dispatch/pull/434 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Edge router test failing on RHEL6 > - > > Key: DISPATCH-1232 > URL: https://issues.apache.org/jira/browse/DISPATCH-1232 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Reporter: Fernando Giorgetti >Assignee: Fernando Giorgetti >Priority: Major > Fix For: 1.5.0 > > > System tests for edge router are failing on RHEL6. > The test_broker.py is calling count attribute of collections.deque(), but > count was introduced in python2.7 and RHEL6 comes with python 2.6 only. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1232) Edge router test failing on RHEL6
[ https://issues.apache.org/jira/browse/DISPATCH-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779715#comment-16779715 ] ASF GitHub Bot commented on DISPATCH-1232: -- fgiorgetti commented on issue #434: DISPATCH-1232 - Improved mechanism to identify openssl version installed URL: https://github.com/apache/qpid-dispatch/pull/434#issuecomment-468005900 Closing this PR as a new one (more appropriate) will be provided soon. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Edge router test failing on RHEL6 > - > > Key: DISPATCH-1232 > URL: https://issues.apache.org/jira/browse/DISPATCH-1232 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Reporter: Fernando Giorgetti >Assignee: Fernando Giorgetti >Priority: Major > Fix For: 1.5.0 > > > System tests for edge router are failing on RHEL6. > The test_broker.py is calling count attribute of collections.deque(), but > count was introduced in python2.7 and RHEL6 comes with python 2.6 only. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] fgiorgetti closed pull request #434: DISPATCH-1232 - Improved mechanism to identify openssl version installed
fgiorgetti closed pull request #434: DISPATCH-1232 - Improved mechanism to identify openssl version installed URL: https://github.com/apache/qpid-dispatch/pull/434 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] fgiorgetti commented on issue #434: DISPATCH-1232 - Improved mechanism to identify openssl version installed
fgiorgetti commented on issue #434: DISPATCH-1232 - Improved mechanism to identify openssl version installed URL: https://github.com/apache/qpid-dispatch/pull/434#issuecomment-468005900 Closing this PR as a new one (more appropriate) will be provided soon. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779648#comment-16779648
]
ASF GitHub Bot commented on PROTON-1998:
gemmellr commented on issue #31: PROTON-1998: add SASL protocol trace logging
(v2)
URL: https://github.com/apache/qpid-proton-j/pull/31#issuecomment-467986048
I noted while trying this out that the headers still aren't logged as
proton-c would also do, but I think we can add that separately.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] gemmellr commented on issue #31: PROTON-1998: add SASL protocol trace logging (v2)
gemmellr commented on issue #31: PROTON-1998: add SASL protocol trace logging (v2) URL: https://github.com/apache/qpid-proton-j/pull/31#issuecomment-467986048 I noted while trying this out that the headers still aren't logged as proton-c would also do, but I think we can add that separately. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779644#comment-16779644
]
ASF GitHub Bot commented on PROTON-1998:
gemmellr commented on issue #30: PROTON-1998: Add SASL protocol trace
URL: https://github.com/apache/qpid-proton-j/pull/30#issuecomment-467985025
Hi Keith, sorry for the delay getting back to this. I've raised #31 based on
your changes with some additional tweaks. Can you give it a look over to see
what you think?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] gemmellr commented on issue #30: PROTON-1998: Add SASL protocol trace
gemmellr commented on issue #30: PROTON-1998: Add SASL protocol trace URL: https://github.com/apache/qpid-proton-j/pull/30#issuecomment-467985025 Hi Keith, sorry for the delay getting back to this. I've raised #31 based on your changes with some additional tweaks. Can you give it a look over to see what you think? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779642#comment-16779642
]
ASF GitHub Bot commented on PROTON-1998:
gemmellr commented on pull request #31: PROTON-1998: add SASL protocol trace
logging (v2)
URL: https://github.com/apache/qpid-proton-j/pull/31
Based on #30 but with updates to minimise some of the changes, use a common
method for writing the output, move the point of logging SASL frame to be
consistent with non-SASL cases, and add a couple more tests.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] gemmellr opened a new pull request #31: PROTON-1998: add SASL protocol trace logging (v2)
gemmellr opened a new pull request #31: PROTON-1998: add SASL protocol trace logging (v2) URL: https://github.com/apache/qpid-proton-j/pull/31 Based on #30 but with updates to minimise some of the changes, use a common method for writing the output, move the point of logging SASL frame to be consistent with non-SASL cases, and add a couple more tests. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1272) Router crashes when detach from receiver and detach from broker arrive at the same time on a link route
[
https://issues.apache.org/jira/browse/DISPATCH-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779581#comment-16779581
]
ASF subversion and git services commented on DISPATCH-1272:
---
Commit 8e94c5cf6f98083af3066b8cff2fd5aa0b176027 in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=8e94c5c ]
DISPATCH-1272 - Zeroed the qd_link->pn_link reference so there would be no
attempt to send out a detach by CORE_link_detach if the outgoing pn_link has
already been freed
> Router crashes when detach from receiver and detach from broker arrive at the
> same time on a link route
> ---
>
> Key: DISPATCH-1272
> URL: https://issues.apache.org/jira/browse/DISPATCH-1272
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.6.0
>
>
> A receiver attaches to the router on a link routed address which is serviced
> by the *standalone* router via a route-container connection connected to the
> broker.
> When the receiver and the broker send detaches at the same time, the receiver
> side pn_link gets freed and the router tries to forward the detach received
> from the broker on to this freed pn_link and crashes.
> {noformat}
> (gdb) thread 1
> [Switching to thread 1 (LWP 8445)]
> #0 pn_data_clear (data=data@entry=0x15) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
> 409 data->size = 0;
> (gdb) bt
> #0 pn_data_clear (data=data@entry=0x15) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
> #1 0x7fb9385e1e21 in pn_data_copy (data=0x15, src=0x93dbfc0) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:2071
> #2 0x7fb938851f89 in qdr_error_copy (from=from@entry=0x7fb91c209698,
> to=) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_core/error.c:96
> #3 0x7fb93886738b in CORE_link_detach (context=0x18185c0,
> link=0x7fb91c104fd8, error=0x7fb91c209698, first=,
> close=) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_node.c:1345
> #4 0x7fb93884d792 in qdr_connection_process (conn=0x7fb91c059f18) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_core/connections.c:330
> #5 0x7fb938833558 in writable_handler (container=0x182f6d0,
> container=0x182f6d0, conn=0x7fb921a96650, qd_conn=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/container.c:332
> #6 qd_container_handle_event (container=0x182f6d0,
> event=event@entry=0x307aa10, conn=conn@entry=0x7fb921a96650,
> qd_conn=qd_conn@entry=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/container.c:640
> #7 0x7fb93886c4df in handle (qd_server=qd_server@entry=0x182dde0,
> e=e@entry=0x307aa10, pn_conn=pn_conn@entry=0x7fb921a96650,
> ctx=ctx@entry=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/server.c:985
> #8 0x7fb93886d2cf in thread_run (arg=0x182dde0) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/server.c:1010{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1272) Router crashes when detach from receiver and detach from broker arrive at the same time on a link route
[
https://issues.apache.org/jira/browse/DISPATCH-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1272.
-
Resolution: Fixed
> Router crashes when detach from receiver and detach from broker arrive at the
> same time on a link route
> ---
>
> Key: DISPATCH-1272
> URL: https://issues.apache.org/jira/browse/DISPATCH-1272
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.6.0
>
>
> A receiver attaches to the router on a link routed address which is serviced
> by the *standalone* router via a route-container connection connected to the
> broker.
> When the receiver and the broker send detaches at the same time, the receiver
> side pn_link gets freed and the router tries to forward the detach received
> from the broker on to this freed pn_link and crashes.
> {noformat}
> (gdb) thread 1
> [Switching to thread 1 (LWP 8445)]
> #0 pn_data_clear (data=data@entry=0x15) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
> 409 data->size = 0;
> (gdb) bt
> #0 pn_data_clear (data=data@entry=0x15) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
> #1 0x7fb9385e1e21 in pn_data_copy (data=0x15, src=0x93dbfc0) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:2071
> #2 0x7fb938851f89 in qdr_error_copy (from=from@entry=0x7fb91c209698,
> to=) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_core/error.c:96
> #3 0x7fb93886738b in CORE_link_detach (context=0x18185c0,
> link=0x7fb91c104fd8, error=0x7fb91c209698, first=,
> close=) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_node.c:1345
> #4 0x7fb93884d792 in qdr_connection_process (conn=0x7fb91c059f18) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_core/connections.c:330
> #5 0x7fb938833558 in writable_handler (container=0x182f6d0,
> container=0x182f6d0, conn=0x7fb921a96650, qd_conn=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/container.c:332
> #6 qd_container_handle_event (container=0x182f6d0,
> event=event@entry=0x307aa10, conn=conn@entry=0x7fb921a96650,
> qd_conn=qd_conn@entry=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/container.c:640
> #7 0x7fb93886c4df in handle (qd_server=qd_server@entry=0x182dde0,
> e=e@entry=0x307aa10, pn_conn=pn_conn@entry=0x7fb921a96650,
> ctx=ctx@entry=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/server.c:985
> #8 0x7fb93886d2cf in thread_run (arg=0x182dde0) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/server.c:1010{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8281) [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
[
https://issues.apache.org/jira/browse/QPID-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779579#comment-16779579
]
ASF subversion and git services commented on QPID-8281:
---
Commit 45e5f9013eb0ca53166cf25b00f773f44685d57f in qpid-broker-j's branch
refs/heads/7.1.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=45e5f90 ]
QPID-8281: [Broker-J][Tests] Regenerate test certificates with RSA 2048bits
keys and copy the keystores into corresponding module test resources
(cherry picked from commit d946bec02cf8cd5d72ab65df38c2733173dbc10b)
> [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
> --
>
> Key: QPID-8281
> URL: https://issues.apache.org/jira/browse/QPID-8281
> Project: Qpid
> Issue Type: Test
> Components: Java Tests
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2,
> qpid-java-broker-7.0.8
>
>
> Unit and integration tests operating with pre-generated test key-stores are
> failing with newer JDKs like openjdk-1.8.0.201.b09-2 due to deprecation of
> RSA 1024bit keys:
> {noformat}
> Caused by: java.security.cert.CertPathValidatorException: Algorithm
> constraints check failed on keysize limits. RSA 1024bit key used with
> certificate: CN=MyRootCA, O=ACME, ST=Ontario, C=CA. Usage was tls server
> at
> sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817)
> at
> sun.security.util.DisabledAlgorithmConstraints$Constraints.permits(DisabledAlgorithmConstraints.java:419)
> at
> sun.security.util.DisabledAlgorithmConstraints.permits(DisabledAlgorithmConstraints.java:167)
> at
> sun.security.provider.certpath.AlgorithmChecker.check(AlgorithmChecker.java:332)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1222)
> {noformat}
> Test kestores and key materials based on RSA 1024bit keys need to be
> re-created with stronger RSA keys
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1272) Router crashes when detach from receiver and detach from broker arrive at the same time on a link route
[
https://issues.apache.org/jira/browse/DISPATCH-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1272:
Summary: Router crashes when detach from receiver and detach from broker
arrive at the same time on a link route (was: Router crashes when detach from
reciver and detach from broker arrive at the same time on a link route)
> Router crashes when detach from receiver and detach from broker arrive at the
> same time on a link route
> ---
>
> Key: DISPATCH-1272
> URL: https://issues.apache.org/jira/browse/DISPATCH-1272
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.6.0
>
>
> A receiver attaches to the router on a link routed address which is serviced
> by the router via a route-container connection connected to the broker.
> When the receiver and the broker send detaches at the same time, the receiver
> side pn_link gets freed and the router tries to forward the detach received
> from the broker on to this freed pn_link and crashes.
> {noformat}
> (gdb) thread 1
> [Switching to thread 1 (LWP 8445)]
> #0 pn_data_clear (data=data@entry=0x15) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
> 409 data->size = 0;
> (gdb) bt
> #0 pn_data_clear (data=data@entry=0x15) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
> #1 0x7fb9385e1e21 in pn_data_copy (data=0x15, src=0x93dbfc0) at
> /usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:2071
> #2 0x7fb938851f89 in qdr_error_copy (from=from@entry=0x7fb91c209698,
> to=) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_core/error.c:96
> #3 0x7fb93886738b in CORE_link_detach (context=0x18185c0,
> link=0x7fb91c104fd8, error=0x7fb91c209698, first=,
> close=) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_node.c:1345
> #4 0x7fb93884d792 in qdr_connection_process (conn=0x7fb91c059f18) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/router_core/connections.c:330
> #5 0x7fb938833558 in writable_handler (container=0x182f6d0,
> container=0x182f6d0, conn=0x7fb921a96650, qd_conn=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/container.c:332
> #6 qd_container_handle_event (container=0x182f6d0,
> event=event@entry=0x307aa10, conn=conn@entry=0x7fb921a96650,
> qd_conn=qd_conn@entry=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/container.c:640
> #7 0x7fb93886c4df in handle (qd_server=qd_server@entry=0x182dde0,
> e=e@entry=0x307aa10, pn_conn=pn_conn@entry=0x7fb921a96650,
> ctx=ctx@entry=0x7fb9201f31d8) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/server.c:985
> #8 0x7fb93886d2cf in thread_run (arg=0x182dde0) at
> /usr/src/debug/qpid-dispatch-1.5.0/src/server.c:1010{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1272) Router crashes when detach from receiver and detach from broker arrive at the same time on a link route
[
https://issues.apache.org/jira/browse/DISPATCH-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1272:
Description:
A receiver attaches to the router on a link routed address which is serviced by
the *standalone* router via a route-container connection connected to the
broker.
When the receiver and the broker send detaches at the same time, the receiver
side pn_link gets freed and the router tries to forward the detach received
from the broker on to this freed pn_link and crashes.
{noformat}
(gdb) thread 1
[Switching to thread 1 (LWP 8445)]
#0 pn_data_clear (data=data@entry=0x15) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
409 data->size = 0;
(gdb) bt
#0 pn_data_clear (data=data@entry=0x15) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
#1 0x7fb9385e1e21 in pn_data_copy (data=0x15, src=0x93dbfc0) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:2071
#2 0x7fb938851f89 in qdr_error_copy (from=from@entry=0x7fb91c209698,
to=) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_core/error.c:96
#3 0x7fb93886738b in CORE_link_detach (context=0x18185c0,
link=0x7fb91c104fd8, error=0x7fb91c209698, first=,
close=) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_node.c:1345
#4 0x7fb93884d792 in qdr_connection_process (conn=0x7fb91c059f18) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_core/connections.c:330
#5 0x7fb938833558 in writable_handler (container=0x182f6d0,
container=0x182f6d0, conn=0x7fb921a96650, qd_conn=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/container.c:332
#6 qd_container_handle_event (container=0x182f6d0,
event=event@entry=0x307aa10, conn=conn@entry=0x7fb921a96650,
qd_conn=qd_conn@entry=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/container.c:640
#7 0x7fb93886c4df in handle (qd_server=qd_server@entry=0x182dde0,
e=e@entry=0x307aa10, pn_conn=pn_conn@entry=0x7fb921a96650,
ctx=ctx@entry=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/server.c:985
#8 0x7fb93886d2cf in thread_run (arg=0x182dde0) at
/usr/src/debug/qpid-dispatch-1.5.0/src/server.c:1010{noformat}
was:
A receiver attaches to the router on a link routed address which is serviced by
the router via a route-container connection connected to the broker.
When the receiver and the broker send detaches at the same time, the receiver
side pn_link gets freed and the router tries to forward the detach received
from the broker on to this freed pn_link and crashes.
{noformat}
(gdb) thread 1
[Switching to thread 1 (LWP 8445)]
#0 pn_data_clear (data=data@entry=0x15) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
409 data->size = 0;
(gdb) bt
#0 pn_data_clear (data=data@entry=0x15) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
#1 0x7fb9385e1e21 in pn_data_copy (data=0x15, src=0x93dbfc0) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:2071
#2 0x7fb938851f89 in qdr_error_copy (from=from@entry=0x7fb91c209698,
to=) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_core/error.c:96
#3 0x7fb93886738b in CORE_link_detach (context=0x18185c0,
link=0x7fb91c104fd8, error=0x7fb91c209698, first=,
close=) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_node.c:1345
#4 0x7fb93884d792 in qdr_connection_process (conn=0x7fb91c059f18) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_core/connections.c:330
#5 0x7fb938833558 in writable_handler (container=0x182f6d0,
container=0x182f6d0, conn=0x7fb921a96650, qd_conn=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/container.c:332
#6 qd_container_handle_event (container=0x182f6d0,
event=event@entry=0x307aa10, conn=conn@entry=0x7fb921a96650,
qd_conn=qd_conn@entry=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/container.c:640
#7 0x7fb93886c4df in handle (qd_server=qd_server@entry=0x182dde0,
e=e@entry=0x307aa10, pn_conn=pn_conn@entry=0x7fb921a96650,
ctx=ctx@entry=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/server.c:985
#8 0x7fb93886d2cf in thread_run (arg=0x182dde0) at
/usr/src/debug/qpid-dispatch-1.5.0/src/server.c:1010{noformat}
> Router crashes when detach from receiver and detach from broker arrive at the
> same time on a link route
> ---
>
> Key: DISPATCH-1272
> URL: https://issues.apache.org/jira/browse/DISPATCH-1272
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.6.0
>
>
> A receiver attaches to the router on a link routed address which is serviced
> by the *standalone* router via a route-container connection conn
[jira] [Created] (DISPATCH-1272) Router crashes when detach from reciver and detach from broker arrive at the same time on a link route
Ganesh Murthy created DISPATCH-1272:
---
Summary: Router crashes when detach from reciver and detach from
broker arrive at the same time on a link route
Key: DISPATCH-1272
URL: https://issues.apache.org/jira/browse/DISPATCH-1272
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 1.5.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 1.6.0
A receiver attaches to the router on a link routed address which is serviced by
the router via a route-container connection connected to the broker.
When the receiver and the broker send detaches at the same time, the receiver
side pn_link gets freed and the router tries to forward the detach received
from the broker on to this freed pn_link and crashes.
{noformat}
(gdb) thread 1
[Switching to thread 1 (LWP 8445)]
#0 pn_data_clear (data=data@entry=0x15) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
409 data->size = 0;
(gdb) bt
#0 pn_data_clear (data=data@entry=0x15) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:409
#1 0x7fb9385e1e21 in pn_data_copy (data=0x15, src=0x93dbfc0) at
/usr/src/debug/qpid-proton-0.26.0/c/src/core/codec.c:2071
#2 0x7fb938851f89 in qdr_error_copy (from=from@entry=0x7fb91c209698,
to=) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_core/error.c:96
#3 0x7fb93886738b in CORE_link_detach (context=0x18185c0,
link=0x7fb91c104fd8, error=0x7fb91c209698, first=,
close=) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_node.c:1345
#4 0x7fb93884d792 in qdr_connection_process (conn=0x7fb91c059f18) at
/usr/src/debug/qpid-dispatch-1.5.0/src/router_core/connections.c:330
#5 0x7fb938833558 in writable_handler (container=0x182f6d0,
container=0x182f6d0, conn=0x7fb921a96650, qd_conn=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/container.c:332
#6 qd_container_handle_event (container=0x182f6d0,
event=event@entry=0x307aa10, conn=conn@entry=0x7fb921a96650,
qd_conn=qd_conn@entry=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/container.c:640
#7 0x7fb93886c4df in handle (qd_server=qd_server@entry=0x182dde0,
e=e@entry=0x307aa10, pn_conn=pn_conn@entry=0x7fb921a96650,
ctx=ctx@entry=0x7fb9201f31d8) at
/usr/src/debug/qpid-dispatch-1.5.0/src/server.c:985
#8 0x7fb93886d2cf in thread_run (arg=0x182dde0) at
/usr/src/debug/qpid-dispatch-1.5.0/src/server.c:1010{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8281) [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
[
https://issues.apache.org/jira/browse/QPID-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779483#comment-16779483
]
ASF subversion and git services commented on QPID-8281:
---
Commit d946bec02cf8cd5d72ab65df38c2733173dbc10b in qpid-broker-j's branch
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=d946bec ]
QPID-8281: [Broker-J][Tests] Regenerate test certificates with RSA 2048bits
keys and copy the keystores into corresponding module test resources
> [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
> --
>
> Key: QPID-8281
> URL: https://issues.apache.org/jira/browse/QPID-8281
> Project: Qpid
> Issue Type: Test
> Components: Java Tests
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2,
> qpid-java-broker-7.0.8
>
>
> Unit and integration tests operating with pre-generated test key-stores are
> failing with newer JDKs like openjdk-1.8.0.201.b09-2 due to deprecation of
> RSA 1024bit keys:
> {noformat}
> Caused by: java.security.cert.CertPathValidatorException: Algorithm
> constraints check failed on keysize limits. RSA 1024bit key used with
> certificate: CN=MyRootCA, O=ACME, ST=Ontario, C=CA. Usage was tls server
> at
> sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817)
> at
> sun.security.util.DisabledAlgorithmConstraints$Constraints.permits(DisabledAlgorithmConstraints.java:419)
> at
> sun.security.util.DisabledAlgorithmConstraints.permits(DisabledAlgorithmConstraints.java:167)
> at
> sun.security.provider.certpath.AlgorithmChecker.check(AlgorithmChecker.java:332)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1222)
> {noformat}
> Test kestores and key materials based on RSA 1024bit keys need to be
> re-created with stronger RSA keys
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8281) [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
[
https://issues.apache.org/jira/browse/QPID-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8281:
Assignee: Alex Rudyy
> [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
> --
>
> Key: QPID-8281
> URL: https://issues.apache.org/jira/browse/QPID-8281
> Project: Qpid
> Issue Type: Test
> Components: Java Tests
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2,
> qpid-java-broker-7.0.8
>
>
> Unit and integration tests operating with pre-generated test key-stores are
> failing with newer JDKs like openjdk-1.8.0.201.b09-2 due to deprecation of
> RSA 1024bit keys:
> {noformat}
> Caused by: java.security.cert.CertPathValidatorException: Algorithm
> constraints check failed on keysize limits. RSA 1024bit key used with
> certificate: CN=MyRootCA, O=ACME, ST=Ontario, C=CA. Usage was tls server
> at
> sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817)
> at
> sun.security.util.DisabledAlgorithmConstraints$Constraints.permits(DisabledAlgorithmConstraints.java:419)
> at
> sun.security.util.DisabledAlgorithmConstraints.permits(DisabledAlgorithmConstraints.java:167)
> at
> sun.security.provider.certpath.AlgorithmChecker.check(AlgorithmChecker.java:332)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1222)
> {noformat}
> Test kestores and key materials based on RSA 1024bit keys need to be
> re-created with stronger RSA keys
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8281) [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
Alex Rudyy created QPID-8281:
Summary: [Broker-J] Regenerate test keystores and trustores
containing RSA 1024bit keys
Key: QPID-8281
URL: https://issues.apache.org/jira/browse/QPID-8281
Project: Qpid
Issue Type: Test
Components: Java Tests
Reporter: Alex Rudyy
Fix For: qpid-java-broker-7.1.2, qpid-java-broker-7.0.8,
qpid-java-broker-8.0.0
Unit and integration tests operating with pre-generated test key-stores are
failing with newer JDKs like openjdk-1.8.0.201.b09-2 due to deprecation of RSA
1024bit keys:
{noformat}
Caused by: java.security.cert.CertPathValidatorException: Algorithm constraints
check failed on keysize limits. RSA 1024bit key used with certificate:
CN=MyRootCA, O=ACME, ST=Ontario, C=CA. Usage was tls server
at
sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817)
at
sun.security.util.DisabledAlgorithmConstraints$Constraints.permits(DisabledAlgorithmConstraints.java:419)
at
sun.security.util.DisabledAlgorithmConstraints.permits(DisabledAlgorithmConstraints.java:167)
at
sun.security.provider.certpath.AlgorithmChecker.check(AlgorithmChecker.java:332)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1222)
{noformat}
Test kestores and key materials based on RSA 1024bit keys need to be re-created
with stronger RSA keys
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
