When trying to use the BMCS Python SDK, I get an SSL/TLS exception. Why?
Exception:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
Bare Metal Cloud Services requires TLS 1.2 connections. Your version of OpenSSL is probably too old and does not support TLS 1.2. Please upgrade your version of OpenSSL and try again.
Related
I am having issues connecting to a mysql database over TLSV1.2, using Ruby and the mysql2 gem. The ruby script is running on Windows. I get the following error:
TLS version used does not meet minimal requirements for this server. Please use a higher TLS version and retry.
Based on some research I believe that mysql2 uses the Connector/C library (6.1.1), which seems to be built against YASSL, which only supports up to TLSV1.1. I can successfully connect via TLSV1.1, but if I restrict the connection to TLSV1.2 then I get the above error.
It seems possible to get a version built against OpenSSL, which supports high TLS versions, but I have found conflicting information on whether that is only for the commercial version, or if that is also available via the community edition. Does anyone have expertise in this area and can recommend a possible solution? Is it possible to get mysql2 and a compatible connector which works with TLSV1.2?
You are right about mysql2 using connector/c.
Not sure where the 6.1.1 version comes from. Did you mean MariaDB-connector-c-3.1.11? who's release notes advertised TLS-1.3 in the openssl version of this.
I checked the centos8 binary download from the above link and its linked against the system openssl (looking at ldd ./lib/mariadb/libmariadb.so).
As far as I know there's no community vs enterprise differentiation here.
We are having exactly the same issue as mentioned on this link https://access.redhat.com/solutions/4827341 but we want to use OKD version probably the latest one which is OKD 4.6. My question is does it support KMS storage encryption in AWS?
While installing openshift OKD cluster on unencrypted disk is not the solution for us so does new OKD 4.6 version support KMS encryption to encrypt disk? As far as I know the redhat document says "This RFE was accomplished for OpenShift Container Platform 4.5" which means it should support KMS encryption from onward OCP version 4.5 and I think would be same for OKD version 4.5. I may be wrong please correct me.
Thanks
Well, the feature is in the OpenShift 4.5 Release Notes:
You can now define a KMS key to encrypt EBS instance volumes. This is useful if you have explicit compliance and security guidelines when deploying to AWS. The KMS key can be configured in the install-config.yaml file by setting the optional kmsKeyARN field. For example:
apiVersion: v1
baseDomain: example.com
compute:
- architecture: amd64
hyperthreading: Enabled
name: worker
platform:
aws:
rootVolume:
kmsKeyARN: arn:aws:kms:us-east-2:563456982459:key/4f5265b4-16f7-xxxx-xxxx-xxxxxxxxxxxx
...
So yes, I would guess that the same can be used in OKD 4.6.
I have the MySQL version 5.7.26 that is using the TLS versions TLSv1.1. I had seen this when I had executed the command SHOW GLOBAL VARIABLES LIKE 'tls_version';. And I would like to upgrade to version TLSv1.2. Unfortunately I can't find a good tutorial site guiding me step by step on how to make this change. Can someone help me out. Thank you
P.S. I am running the server on Mac OS Catalina.
Most probably the openssl library on your system does not support tls 1.2 yet.
You can try
brew upgrade openssl
I have to use Restheart APIs in an OpenShift application.
I tried to execute restheart.jar as suggested in the installation and use guide, but it produced an error, due to the difference between the installed java version (openjdk 7) and the required one (oracle java 8).
Is there any trick to get Restheart APIs working in an OpenShift app?
OpenShift does not support JDK 8 but that doesn’t mean you can’t run Java 8 applications.
You can use a DIY cartridge and install your own JDK version.
I am developing android app using Oracle mobile ADF that uses MySQL database to retrieve data. I have used JDeveloper 11, MySQL 5.6, jdbc connector-5.1.25, JDK1.7, but still I am getting com/mysql/jdbc/Driver (unsupported major.minor version 49.0) error in Android emulator.
Could you run this command and come back to us with result: java -version
Is your database local on your phone or on a remote server.
If it is on a remote server, you can't JDBC into it from ADF Mobile.
You need to go through Web services.