[jira] [Resolved] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved OPENWIRE-68. Resolution: Fixed > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?focusedWorklogId=895095=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895095 ] ASF GitHub Bot logged work on OPENWIRE-68: -- Author: ASF GitHub Bot Created on: 11/Dec/23 23:27 Start Date: 11/Dec/23 23:27 Worklog Time Spent: 10m Work Description: cshannon merged PR #9: URL: https://github.com/apache/activemq-openwire/pull/9 Issue Time Tracking --- Worklog Id: (was: 895095) Time Spent: 0.5h (was: 20m) > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795538#comment-17795538 ] ASF subversion and git services commented on OPENWIRE-68: - Commit 3ffad4eee3f226e5e1446d6d7b6f80a96f6d037a in activemq-openwire's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq-openwire.git;h=3ffad4e ] OPENWIRE-68 - Import OpenWire version 12 (#9) This adds support for OpenWire v12 which includes the BrokerSubsriptionInfo command that was added. Legacy marshallers were added as well as interop tests for the new command. > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?focusedWorklogId=895094=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895094 ] ASF GitHub Bot logged work on OPENWIRE-68: -- Author: ASF GitHub Bot Created on: 11/Dec/23 23:25 Start Date: 11/Dec/23 23:25 Worklog Time Spent: 10m Work Description: tabish121 commented on PR #9: URL: https://github.com/apache/activemq-openwire/pull/9#issuecomment-1851055665 LGTM Issue Time Tracking --- Worklog Id: (was: 895094) Time Spent: 20m (was: 10m) > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?focusedWorklogId=895091=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895091 ] ASF GitHub Bot logged work on OPENWIRE-68: -- Author: ASF GitHub Bot Created on: 11/Dec/23 23:07 Start Date: 11/Dec/23 23:07 Worklog Time Spent: 10m Work Description: cshannon opened a new pull request, #9: URL: https://github.com/apache/activemq-openwire/pull/9 This adds support for OpenWire v12 which includes the BrokerSubsriptionInfo command that was added. Legacy marshallers were added as well as interop tests for the new command. Issue Time Tracking --- Worklog Id: (was: 895091) Remaining Estimate: 0h Time Spent: 10m > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned OPENWIRE-68: -- Assignee: Christopher L. Shannon > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (OPENWIRE-68) Import v12 OpenWire version
[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OPENWIRE-68 started by Christopher L. Shannon. -- > Import v12 OpenWire version > --- > > Key: OPENWIRE-68 > URL: https://issues.apache.org/jira/browse/OPENWIRE-68 > Project: ActiveMQ OpenWire > Issue Type: Task >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 1.0.0 > > > The project currently only contains up to version 11, we need to import > version 12. There will need to be some refactoring and packaging done for > this. The CVE fix is actually handled at the base class level so we just need > to update the legacy test for the marshalling CVE fix. The CVE is fixed in > OPENWIRE-67 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9413) WebSite / AMQ6 confusion
[
https://issues.apache.org/jira/browse/AMQ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795420#comment-17795420
]
Mike Lothian commented on AMQ-9413:
---
Thanks for clarifying and I'll direct any future questions to the correct place
> WebSite / AMQ6 confusion
>
>
> Key: AMQ-9413
> URL: https://issues.apache.org/jira/browse/AMQ-9413
> Project: ActiveMQ
> Issue Type: Bug
> Components: website
>Affects Versions: 6.0.0, 6.0.1
>Reporter: Mike Lothian
>Priority: Minor
>
> Is ActiveMQ 6 now the previous ArtemisMQ code?
> If so does that mean Artemis is no longer being developed? Or is it just the
> next set of feature work
> activemq.apache.org doesn't really make this clear and I think is still using
> the wording from pre-6
> This section in particular:
> {quote}There are currently two "flavors" of ActiveMQ available - the
> well-known "classic" broker and the "next generation" broker code-named
> {_}Artemis{_}. Once Artemis reaches a sufficient level of feature parity with
> the "Classic" code-base it will become the next major version of ActiveMQ.
> Initial [migration
> documentation|https://activemq.apache.org/components/artemis/migration] is
> available as well as a development
> [roadmap|https://activemq.apache.org/activemq-artemis-roadmap] for Artemis.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9413) WebSite / AMQ6 confusion
[
https://issues.apache.org/jira/browse/AMQ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795415#comment-17795415
]
Robbie Gemmell commented on AMQ-9413:
-
Please ask questions on the users list or chat
https://activemq.apache.org/contact
ActiveMQ 6.0.0 is essentially a Jakarta'fied continuation of the ActiveMQ
5.18.x codebase, with related updates like switching to using Spring 6,
necessarily requiring Java 17 minimum, and other changes appropriate to the new
release stream. For a long time it was just going to be called 5.19.x but
following more recent discussion 6.x was used as it seemed clearer and more
appropriate especially as javax and jakarta release streams are likely to
coexist for some time. Artemis is still being developed and nothing really
changed there as Artemis releases have included both JMS 2 and Jakarta
Messaging 3.x support since 2021.
> WebSite / AMQ6 confusion
>
>
> Key: AMQ-9413
> URL: https://issues.apache.org/jira/browse/AMQ-9413
> Project: ActiveMQ
> Issue Type: Bug
> Components: website
>Affects Versions: 6.0.0, 6.0.1
>Reporter: Mike Lothian
>Priority: Minor
>
> Is ActiveMQ 6 now the previous ArtemisMQ code?
> If so does that mean Artemis is no longer being developed? Or is it just the
> next set of feature work
> activemq.apache.org doesn't really make this clear and I think is still using
> the wording from pre-6
> This section in particular:
> {quote}There are currently two "flavors" of ActiveMQ available - the
> well-known "classic" broker and the "next generation" broker code-named
> {_}Artemis{_}. Once Artemis reaches a sufficient level of feature parity with
> the "Classic" code-base it will become the next major version of ActiveMQ.
> Initial [migration
> documentation|https://activemq.apache.org/components/artemis/migration] is
> available as well as a development
> [roadmap|https://activemq.apache.org/activemq-artemis-roadmap] for Artemis.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (AMQ-9413) WebSite / AMQ6 confusion
[
https://issues.apache.org/jira/browse/AMQ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved AMQ-9413.
-
Resolution: Information Provided
> WebSite / AMQ6 confusion
>
>
> Key: AMQ-9413
> URL: https://issues.apache.org/jira/browse/AMQ-9413
> Project: ActiveMQ
> Issue Type: Bug
> Components: website
>Affects Versions: 6.0.0, 6.0.1
>Reporter: Mike Lothian
>Priority: Minor
>
> Is ActiveMQ 6 now the previous ArtemisMQ code?
> If so does that mean Artemis is no longer being developed? Or is it just the
> next set of feature work
> activemq.apache.org doesn't really make this clear and I think is still using
> the wording from pre-6
> This section in particular:
> {quote}There are currently two "flavors" of ActiveMQ available - the
> well-known "classic" broker and the "next generation" broker code-named
> {_}Artemis{_}. Once Artemis reaches a sufficient level of feature parity with
> the "Classic" code-base it will become the next major version of ActiveMQ.
> Initial [migration
> documentation|https://activemq.apache.org/components/artemis/migration] is
> available as well as a development
> [roadmap|https://activemq.apache.org/activemq-artemis-roadmap] for Artemis.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4528) TLS support PEM format for key and trust store type
[
https://issues.apache.org/jira/browse/ARTEMIS-4528?focusedWorklogId=895043=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895043
]
ASF GitHub Bot logged work on ARTEMIS-4528:
---
Author: ASF GitHub Bot
Created on: 11/Dec/23 15:06
Start Date: 11/Dec/23 15:06
Worklog Time Spent: 10m
Work Description: gtully commented on code in PR #4706:
URL: https://github.com/apache/activemq-artemis/pull/4706#discussion_r1422615766
##
artemis-core-client/src/main/java/org/apache/activemq/artemis/core/remoting/impl/ssl/SSLSupport.java:
##
@@ -351,6 +353,14 @@ private static KeyStore loadKeystore(final String
keystoreProvider,
return ks;
}
+ private static void checkPemProviderLoaded(String keystoreType) {
+ if (keystoreType != null && keystoreType.startsWith("PEM")) {
+ if (Security.getProvider("PEM") == null) {
+Security.insertProviderAt(new PemKeyStoreProvider(),
Integer.parseInt(System.getProperty("artemis.pemProvider.insertAt", "0"), 10));
+ }
+ }
+ }
Review Comment:
ok, removed! thanks
Issue Time Tracking
---
Worklog Id: (was: 895043)
Time Spent: 4h 20m (was: 4h 10m)
> TLS support PEM format for key and trust store type
> ---
>
> Key: ARTEMIS-4528
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4528
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Configuration
>Affects Versions: 2.31.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> managing key and trust store passwords when the credentials are securely
> stored or managed by other means is a nuisance.
> there is a nice PEM keystore provider at:
> [https://github.com/ctron/pem-keystore]
> This gives us an intuitive way to easily reference a simple cert or key
> without a password as is the case with jsk or pkcs12
> name="netty-ssl-acceptor">tcp://localhost:5500?sslEnabled=true;keyStorePath=server-keystore.pem;keyStoreType=PEM
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (AMQ-9413) WebSite / AMQ6 confusion
Mike Lothian created AMQ-9413:
-
Summary: WebSite / AMQ6 confusion
Key: AMQ-9413
URL: https://issues.apache.org/jira/browse/AMQ-9413
Project: ActiveMQ
Issue Type: Bug
Components: website
Affects Versions: 6.0.1, 6.0.0
Reporter: Mike Lothian
Is ActiveMQ 6 now the previous ArtemisMQ code?
If so does that mean Artemis is no longer being developed? Or is it just the
next set of feature work
activemq.apache.org doesn't really make this clear and I think is still using
the wording from pre-6
This section in particular:
{quote}There are currently two "flavors" of ActiveMQ available - the well-known
"classic" broker and the "next generation" broker code-named {_}Artemis{_}.
Once Artemis reaches a sufficient level of feature parity with the "Classic"
code-base it will become the next major version of ActiveMQ. Initial [migration
documentation|https://activemq.apache.org/components/artemis/migration] is
available as well as a development
[roadmap|https://activemq.apache.org/activemq-artemis-roadmap] for Artemis.
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
