Google Play alert about OpenSSL

Get help using Construct 2

Post » Thu Dec 18, 2014 6:46 pm

Try the OpenSSL update, and then re build. There is nothing to loose and as I have found after the 5 hours wait time from submitting in the Google play developer console, the alerts have gone away.
Some games: https://play.google.com/store/search?q= ... s&hl=en_GB Feel free to show the panda some support, he would appreciate it :)
B
19
S
5
G
1
Posts: 155
Reputation: 1,619

Post » Thu Dec 18, 2014 6:58 pm

Hi @BinaryPanda,

The build fails sometimes do you know why does this occur?? I managed to build one game and now my second game it fails. I even rexported from Construct 2 and created a new project in Intel XDK.

I am installing to Windows System Directory should I install to Open SSL binaries directory???

And I am installing 64 bit version right since my windows is 64 bit.
B
19
S
6
Posts: 179
Reputation: 2,202

Post » Thu Dec 18, 2014 7:09 pm

I ran the CYGWIN 64bit install download since my operating system is win7 64bit and just used the default install options that come up. Nothing else, it really was that simple.

The build could be failing for reasons unrelated, so I would check everything over carefully to make sure it is correct.
Some games: https://play.google.com/store/search?q= ... s&hl=en_GB Feel free to show the panda some support, he would appreciate it :)
B
19
S
5
G
1
Posts: 155
Reputation: 1,619

Post » Thu Dec 18, 2014 7:13 pm

Really weird the build worked after I reinstalled the SSL. The file name I installed was Win64OpenSSL_1_0_1j.exe Hope that is right. Also I did a silly thing first installed 32bit version then 64bit version maybe that is confusing the system. Now will try my 3rd game :)
B
19
S
6
Posts: 179
Reputation: 2,202

Post » Thu Dec 18, 2014 7:26 pm

BinaryPanda wrote:I have no idea how the Intel XDK is working, but it maybe using files on your computer to assist in the build, so updating those helps. It maybe that when Intel XDK is updated this has the same effect as updating now with the links I have used.


I have the same errors on C2 apps that were created on different machines. One was a brand new Windows 8.1 PC with all the updates. I think the problem lies in XDK itself.

I just unpublished all my C2 apps from Google Play. IMHO its not worth taking a chance as they will ban your account. ;(

We need a definitive fix.
B
15
S
2
Posts: 229
Reputation: 1,353

Post » Thu Dec 18, 2014 7:27 pm

@BinaryPanda ok for me the build never works at the first attempt! At first build it fails, I close the build tab and try to rebuild again and it works!! weird!

How long did it take for the warnings to dissappear in your Google Pla developer account?? Cause one of my updated game still has the yellow warning sign.
B
19
S
6
Posts: 179
Reputation: 2,202

Post » Thu Dec 18, 2014 7:47 pm

This is the email I just received from Google after contacting them today.

Thanks for contacting Google Play Developer Support about the security alert you have received with regard to using highly vulnerable version of OpenSSL.

We want you to have time to update now, but eventually, to help protect users we may need to block apps that have out of date dependent libraries or other vulnerabilities. We will provide a clear deadline before any action is taken. We recommend that you update OpenSSL as soon as possible to protect your users from the risk of compromise, and to make sure that your app is compliant with Google Play Policy on ‘dangerous products’.
B
19
S
6
Posts: 179
Reputation: 2,202

Post » Thu Dec 18, 2014 8:38 pm

volcank wrote:This is the email I just received from Google after contacting them today.

Thanks for contacting Google Play Developer Support about the security alert you have received with regard to using highly vulnerable version of OpenSSL.

We want you to have time to update now, but eventually, to help protect users we may need to block apps that have out of date dependent libraries or other vulnerabilities. We will provide a clear deadline before any action is taken. We recommend that you update OpenSSL as soon as possible to protect your users from the risk of compromise, and to make sure that your app is compliant with Google Play Policy on ‘dangerous products’.


@Volcank so is the update functional?
Intel XDK folks seem to be quiet on the matter. :/
B
5
S
1
Posts: 8
Reputation: 444

Post » Thu Dec 18, 2014 8:44 pm

volcank wrote:@BinaryPanda ok for me the build never works at the first attempt! At first build it fails, I close the build tab and try to rebuild again and it works!! weird!

How long did it take for the warnings to dissappear in your Google Pla developer account?? Cause one of my updated game still has the yellow warning sign.


@Volcank took a while to update. Think the times can vary. Google says 5 hours atleast
Some games: https://play.google.com/store/search?q= ... s&hl=en_GB Feel free to show the panda some support, he would appreciate it :)
B
19
S
5
G
1
Posts: 155
Reputation: 1,619

Post » Thu Dec 18, 2014 8:46 pm

Message: volcank can only post plain text URLS until they have 500 rep. 1 URLS modified. Why?
I don't think there seems to be an update with XDK recently but I also mentioned about the threads and how worried everyone of us about this situation at Intel's Developer Forum site. I hope this can fasten up the situation. You can check the thread and the subjects discussed from the link below.

https://software.intel.com/en-us/forums/topic/537301

For the time being I followed @BinaryPanda 's way and updated my SSL from the second link he had given. I just have to wait around 5 hours to see the results. But ofcouse the best and more safer way will be when the XDK is updated. I just wish good luck with this one to everyone and hope Googleplay do not ban our accounts. But from their reply to me it seems they will only disable the apps that has Open SSL alert. Well.....Hope so :))
B
19
S
6
Posts: 179
Reputation: 2,202

PreviousNext

Return to How do I....?

Who is online

Users browsing this forum: brunopalermo, ChesVCF, OBLIVION, shinkan, Solomon, yiuyiu6666 and 23 guests