Hi ,
Thanks you for the quick respond.
So according to the link you send, the keystore type is jks as well.
I will try and update...
But according the client configuration (I found this document for it:
We check - the PKCS12 works - (as we saw it in the s_client)
It looks like the server did not found a valid certificate...
Maybe you have a working example? When the client is native c++?
Thanks!!
-Original Message-
From: Liron Ben Ari
Sent: Tuesday, June 12, 2018 11:25 AM
To:
---
Spring Data GemFire > Nightly-ApacheGeode > #946 was successful.
---
Scheduled
2420 tests in total.
https://build.spring.io/browse/SGF-NAG-946/
--
This
CVE-2017-15695 Apache Geode remote code execution vulnerability
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected: Apache Geode 1.0.0 through 1.4.0
Description:
When a Geode server is configured with a security manager, a user with
DATA:WRITE privileges is allowed
All,
Please attach any 1.8.0 client/sever protocol changes to GEODE-5316 [1].
This will help the Geode Native people keep track of changes that need to
be made when updating the protocol version the native client uses. In the
future, when rolling the protocol ordinal please open a ticket like
Hello,
For "native" C++ interaction have a look at
geode-native/cppcache/integration-test/testThinClientSSL
This should provide an example of connecting with SSL enabled...
EB
On Tue, Jun 12, 2018 at 2:48 AM, Liron Ben Ari
wrote:
>
> We check - the PKCS12 works - (as we saw it in the
