Search the Community

How can I configure AWS Elastic Load Balancing (ELB) to use SSL/TLS encryption for secure communication between the client and the backend servers, and ensure that the SSL/TLS certificates are properly managed and updated on a regular basis? Additionally, what options are available for SSL/TLS termination, such as SSL offloading, SSL pass-through, or end-to-end SSL encryption, and how can I determine which option is best suited for my application's requirements and performance needs? Recently I joined AWS certification and I faced some queries So can you solve these queries? Thanks in advance.

Ok, I send links 1.) If you would like to test your host server how good it handle ssl/https https://www.ssllabs.com/ 2.) I add also two links which are good to scan your host server and check if there is any virus or such things.... https://www.virustotal.com/#/home/url https://vms.drweb.com/online/?lng=en Greeings

Hello everyone, I am new to the site. I am having an issue with a game I bought on CodeCanyon. Maybe someone here can help. This is the game link -> http://gametaz.com/html/summer/index.html It works fine as a normal link, But I need it to work on an SSL connection On this link -> https://gametaz.com/html/summer/index.html For some reason it does not load. Any help will be appreciated.

I've developed an HTML5 game using cocoonjs. I followed various guides online to get the thing SSL'd(?) and zipaligned (?) and was finally able to get the APK supplied by cocoon in a format that the play store would accept. I have received an email from the play store advising me of a 60 day deadline to resolve SSL issues with the app (pasted below). Does anyone know of any online resource (or would care to share their advice) that can hold my hand through resolving this (preferably the whole process from cocoon APK to play store ready APK) issue. Getting it to a play store ready format took a couple of hours and if I'm honest, I have no idea how I got there Thanks, BattyMilk Email from the play store We wanted to let you know that your app(s) listed below statically link against a version of OpenSSL that has multiple security vulnerabilities for users. Please migrate your app(s) to an updated version of OpenSSL within 60 days of this notification. Beginning 7/7/15, Google Play will block publishing of any new apps and updates that use older, unsupported versions of OpenSSL (see below for details). REASON FOR WARNING: Violation of the dangerous products provision of the Content Policy and section 4.4 of the Developer Distribution Agreement. The vulnerabilities were fixed in OpenSSL versions beginning with 1.0.1h, 1.0.0m, and 0.9.8za. To confirm your OpenSSL version, you can do a grep via: $ unzip -p YourApp.apk | strings | grep "OpenSSL" For more information about the vulnerability, please see this OpenSSL Security Advisory. To confirm that you’ve upgraded correctly, upload the updated version of the app(s) to the Developer Console and check back after five hours. For other technical questions about managing OpenSSL, please seehttps://groups.google.com/forum/#!forum/mailing.openssl.users. In 60 days, we will not accept app updates containing the vulnerabilities. In addition, we will reject new apps containing the vulnerabilities. Note: while the issues may not affect every app that uses OpenSSL versions prior to 1.0.1h, 1.0.0m, or 0.9.8za, developers should stay up to date on all security patches. Even if you think that specific issues may not be relevant, it's good practice to update any libraries in your app that have known issues. Please take this time to update apps that have out-of-date dependent libraries or other vulnerabilities. Before publishing applications, please ensure your apps’ compliance with the Developer Distribution Agreement and Content Policy. If you feel we have sent this warning in error, visit this Google Play Help Center article. Regards, Google Play Team