[JBoss JIRA] (JGRP-2274) ASYM_ENCRYPT: deprecate sign_msgs
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2274?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2274:
--------------------------------
As soon as I'm done with 4.1.5, I'll get back to 5. The rebase will be some effort, as 5 was branched off a while ago and 4 has diverged quite a bit.
> ASYM_ENCRYPT: deprecate sign_msgs
> ---------------------------------
>
> Key: JGRP-2274
> URL: https://issues.jboss.org/browse/JGRP-2274
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.12
>
>
> In {{ASYM_ENCRYPT}}, signing messages means that the checksum of an encrypted message is computed and used together with the secret key of the sender to sign the message. On the receiver side, the public key of the sender is used to validate the signature.
> However, this is redundant, as decryption of a message will fail if the contents have been changed.
> If needed, signing of messages can be done in a separate protocol.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (JGRP-2274) ASYM_ENCRYPT: deprecate sign_msgs
by Nick Sawadsky (Jira)
[ https://issues.jboss.org/browse/JGRP-2274?page=com.atlassian.jira.plugin.... ]
Nick Sawadsky commented on JGRP-2274:
-------------------------------------
[~belaban] Great, thanks! I'll watch that ticket for updates. Any info you currently have on the timeline for 5.0 is also much appreciated.
> ASYM_ENCRYPT: deprecate sign_msgs
> ---------------------------------
>
> Key: JGRP-2274
> URL: https://issues.jboss.org/browse/JGRP-2274
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.12
>
>
> In {{ASYM_ENCRYPT}}, signing messages means that the checksum of an encrypted message is computed and used together with the secret key of the sender to sign the message. On the receiver side, the public key of the sender is used to validate the signature.
> However, this is redundant, as decryption of a message will fail if the contents have been changed.
> If needed, signing of messages can be done in a separate protocol.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFCORE-4631) Create tests for Elytron syslog reconnect attempts
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4631?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4631:
---------------------------------------
I set this as a blocker for 18.0.0.Beta however it's more of a blocker for 18.0.0.Final. The tests should likely be there before we release. There are similar tests in Elytron itself, but the integration tests are important as well I think.
> Create tests for Elytron syslog reconnect attempts
> --------------------------------------------------
>
> Key: WFCORE-4631
> URL: https://issues.jboss.org/browse/WFCORE-4631
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 10.0.0.Beta6
>
>
> WFCORE-4394 currently has some tests which will be disabled for this. It's likely some integration tests will need to be done instead of unit tests. ELY-1864 is going to change the way the reconnect attempts are done resulting in the current unit tests failing.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFCORE-4631) Create tests for Elytron syslog reconnect attempts
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4631?page=com.atlassian.jira.plugi... ]
James Perkins reassigned WFCORE-4631:
-------------------------------------
Fix Version/s: 10.0.0.Beta6
Priority: Blocker (was: Major)
Assignee: James Perkins
> Create tests for Elytron syslog reconnect attempts
> --------------------------------------------------
>
> Key: WFCORE-4631
> URL: https://issues.jboss.org/browse/WFCORE-4631
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 10.0.0.Beta6
>
>
> WFCORE-4394 currently has some tests which will be disabled for this. It's likely some integration tests will need to be done instead of unit tests. ELY-1864 is going to change the way the reconnect attempts are done resulting in the current unit tests failing.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12456) Use a separate package for org.wildfly.dist.subsystem.xml in the dist-legacy module
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12456:
---------------------------------------
Summary: Use a separate package for org.wildfly.dist.subsystem.xml in the dist-legacy module
Key: WFLY-12456
URL: https://issues.jboss.org/browse/WFLY-12456
Project: WildFly
Issue Type: Task
Components: Build System, Test Suite
Reporter: Brian Stansberry
The same tests in package org.wildfly.dist.subsystem.xml are included in the code of both the 'dist' and 'dist-legacy' modules. It's not worth the hassle of trying to share the code. But to reduce confusion, change the package in dist-legacy so if there are test failures it is clear where.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-255?page=com.atlassian.jira.plugin... ]
James Perkins updated WFCORE-255:
---------------------------------
Description:
The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. They cannot be set as a system-property resource, but can be overridden via {{JAVA_OPTS}} or the command line. For a domain server these values need to be allowed to be set as a {{boot-time=true}} system property.
The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
{code}
[domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true,
"server-groups" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}},
"server-two" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}}
}}}}
}
{code}
These properties should also be allowed to be set in the {{/host=*/server-config=*/jvm=*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
was:
The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. They cannot be set as a system-property resource, but can be overridden via {{JAVA_OPTS}} or the command line. For a domain server these values need to be allowed to be set as a {{boot-time=true}} system property.
The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
{code}
[domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true,
"server-groups" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}},
"server-two" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}}
}}}}
}
{code}
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.jboss.org/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. They cannot be set as a system-property resource, but can be overridden via {{JAVA_OPTS}} or the command line. For a domain server these values need to be allowed to be set as a {{boot-time=true}} system property.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=*/server-config=*/jvm=*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-255?page=com.atlassian.jira.plugin... ]
James Perkins updated WFCORE-255:
---------------------------------
Description:
The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. They cannot be set as a system-property resource, but can be overridden via {{JAVA_OPTS}} or the command line. For a domain server these values need to be allowed to be set as a {{boot-time=true}} system property.
The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
{code}
[domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true,
"server-groups" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}},
"server-two" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}}
}}}}
}
{code}
These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
was:
The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. They cannot be set as a system-property resource, but can be overridden via {{JAVA_OPTS}} or the command line. For a domain server these values need to be allowed to be set as a {{boot-time=true}} system property.
The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
{code}
[domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true,
"server-groups" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}},
"server-two" => {"response" => {
"outcome" => "failed",
"failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
"rolled-back" => true
}}
}}}}
}
{code}
These properties should also be allowed to be set in the {{/host=*/server-config=*/jvm=*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.jboss.org/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. They cannot be set as a system-property resource, but can be overridden via {{JAVA_OPTS}} or the command line. For a domain server these values need to be allowed to be set as a {{boot-time=true}} system property.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months