October 2019 - jboss-jira - Jboss List Archives

[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: -------------------------------- Excellent! I intend to add TLS support directly to BaseServer and subclasses, so this will take a bit of time, and only once I've released an initial 5.0. This won't be available in 4.x (unless someone backports it). > 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.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2386) Support for encryption ciphers that require an initialization vector

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2386?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2386: --------------------------- Fix Version/s: 4.1.6 > Support for encryption ciphers that require an initialization vector > -------------------------------------------------------------------- > > Key: JGRP-2386 > URL: https://issues.jboss.org/browse/JGRP-2386 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.1.5, 3.6.19 > Reporter: Nick Sawadsky > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.6 > > > By default, Encrypt sets sym_algorithm to "AES". As a result, the default cipher mode is used, which is ECB. ECB encrypts a given plaintext block to the same ciphertext every time, which can allow attackers to see [patterns in messages being exchanged|https://crypto.stackexchange.com/questions/20941/why-shouldnt-i...]. > Modes like CBC, that use a random initialization vector (IV) avoid this problem (assuming a different IV is used for each message). > It would be good to modify Encrypt to support ciphers that require an IV, such as AES/CBC/PKCS5Padding. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1872) elytron-tool.sh usage with symbolic links

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/ELY-1872?page=com.atlassian.jira.plugin.s... ] Ivo Studensky updated ELY-1872: ------------------------------- Labels: downstream_dependency (was: ) > elytron-tool.sh usage with symbolic links > ----------------------------------------- > > Key: ELY-1872 > URL: https://issues.jboss.org/browse/ELY-1872 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Affects Versions: 2.0.0.Alpha4 > Environment: Red Hat JBoss Enterprise Application Platform (7.2.3) > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > It looks like elytron-tool.sh doesn't work well with symbolic links. > The soft link becomes a credential store - in a "standard" file - with the newly added alias but the original credential store will not be updated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2385) Node heartbeat checks are failing with TCP

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2385?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2385. -------------------------- Resolution: Rejected 3.4.0 was released 6 years ago: I don't support such an old version. Besides, please use the forums or mailing list to ask questions, not JIRA! Regards, > Node heartbeat checks are failing with TCP > ------------------------------------------ > > Key: JGRP-2385 > URL: https://issues.jboss.org/browse/JGRP-2385 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.19 > Environment: Windows > Reporter: Rashmi Acharya > Assignee: Bela Ban > Priority: Critical > > Hi Bela, > One of our customer which is still on 3.4.0 Jgroups are facing issue with Node -Node cluster heartbeat communication with TCP. > Node is not responding intermittently and moved out of cluster group (around 3 nodes as part of the cluster along with 3 container nodes) > when port_range=0 setting, it works fine.. Can you please explain the significance of this with TCP option ? What is the recommended value which is suggested with Jgroups ? > Here is the property String: > jgroups_cluster.property_string=TCP(bind_addr=10.1.231.73;bind_port=8141):TCPPING(initial_hosts=10.1.231.73,10.1.231.10;port_range=1;timeout=5000;num_initial_members=2):MERGE2(min_interval=3000;max_interval=5000):FD_ALL(interval=5000;time > out=20000):FD(timeout=5000;max_tries=48;level=ERROR):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(retransmit_timeout=100,200,300,600,1200,2400,4800;discard_delivered_msgs=true):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pb > cast.GMS(print_local_addr=true;join_timeout=5000) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4697) Upgrade WildFly Elytron to 1.10.4.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4697?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4697: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade WildFly Elytron to 1.10.4.Final > --------------------------------------- > > Key: WFCORE-4697 > URL: https://issues.jboss.org/browse/WFCORE-4697 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4698) Upgrade WildFly Elytron to 1.10.4.Final

by Ivo Studensky (Jira)

Ivo Studensky created WFCORE-4698: ------------------------------------- Summary: Upgrade WildFly Elytron to 1.10.4.Final Key: WFCORE-4698 URL: https://issues.jboss.org/browse/WFCORE-4698 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Ivo Studensky Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4697) Upgrade WildFly Elytron to 1.10.4.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4697?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4697: ---------------------------------- Fix Version/s: (was: 10.0.0.Final) > Upgrade WildFly Elytron to 1.10.4.Final > --------------------------------------- > > Key: WFCORE-4697 > URL: https://issues.jboss.org/browse/WFCORE-4697 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Assignee: Darran Lofthouse > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4697) Upgrade WildFly Elytron to 1.10.4.Final

by Ivo Studensky (Jira)

Ivo Studensky created WFCORE-4697: ------------------------------------- Summary: Upgrade WildFly Elytron to 1.10.4.Final Key: WFCORE-4697 URL: https://issues.jboss.org/browse/WFCORE-4697 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Ivo Studensky Assignee: Darran Lofthouse Fix For: 10.0.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4697) Upgrade WildFly Elytron to 1.10.4.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4697?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4697: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3960) > Upgrade WildFly Elytron to 1.10.4.Final > --------------------------------------- > > Key: WFCORE-4697 > URL: https://issues.jboss.org/browse/WFCORE-4697 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Assignee: Darran Lofthouse > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-209) WildFlyServerStatus is not present in operator description

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFWIP-209?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka commented on WFWIP-209: ---------------------------------------- I assume it was fixed with recent changes https://github.com/wildfly/wildfly-operator/pull/90#pullrequestreview-294... in operator. > WildFlyServerStatus is not present in operator description > ----------------------------------------------------------- > > Key: WFWIP-209 > URL: https://issues.jboss.org/browse/WFWIP-209 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > WFWIP-163 is back. > Operator image build from https://github.com/wildfly/wildfly-operator/commit/73722306343d8650b7d3f9... > Install the operator using the run-openshift.sh script (yaml files from ^ are used) > reproduce: > {noformat} > $ oc apply -f quickstart-cr.yaml > $ oc get pods > NAME READY STATUS RESTARTS AGE > quickstart-0 1/1 Running 0 3m39s > quickstart-1 1/1 Running 0 3m39s > wildfly-operator-777b5ccd87-cf2vf 1/1 Running 0 4m22s > $ oc describe wildflyserver quickstart > Name: quickstart > Namespace: pkremens-namespace > Labels: <none> > Annotations: kubectl.kubernetes.io/last-applied-configuration: > {"apiVersion":"wildfly.org/v1alpha1","kind":"WildFlyServer","metadata":{"annotations":{},"name":"quickstart","namespace":"pkremens-namespa... > API Version: wildfly.org/v1alpha1 > Kind: WildFlyServer > Metadata: > Creation Timestamp: 2019-09-26T10:10:43Z > Generation: 1 > Resource Version: 337905 > Self Link: /apis/wildfly.org/v1alpha1/namespaces/pkremens-namespace/wildflyservers/quickstart > UID: e63168ce-e045-11e9-9045-52fdfc072182 > Spec: > Application Image: quay.io/wildfly-quickstarts/wildfly-operator-quickstart:17.0 > Size: 2 > Storage: > Volume Claim Template: > Spec: > Resources: > Requests: > Storage: 3Gi > Events: <none> > {noformat} > Status is missing. > Operator log error: > {noformat} > {"level":"error","ts":1569492856.288481,"logger":"wildlfyserver_resources","msg":"Failed to update status of WildFlyServer","WildFlyServer.Namespace":"pkremens-namespace","WildFlyServer.Name":"quickstart","error":"the server could not find the requested resource (put wildflyservers.wildfly.org quickstart)","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {"level":"error","ts":1569492856.288641,"logger":"wildflyserver_controller","msg":"Failed to update WildFlyServer status.","Request.Namespace":"pkremens-namespace","Request.Name":"quickstart","error":"the server could not find the requested resource (put wildflyservers.wildfly.org quickstart)","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {"level":"error","ts":1569492856.288895,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"pkremens-namespace/quickstart","error":"the server could not find the requested resource (put wildflyservers.wildfly.org quickstart)","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019