Intel XDK OpenSSL fixed?

0 favourites
  • Hi,

    Firstly i wanna say that I read almost all what I found on the forum on the OpenSSL Intel XDK problem.

    So i made a game and I recived that warning with intel xdk and after 1-2 weeks it disappears.

    Since than i didn't republish my game anymore ( with the updated Intel XDK )

    Today <img src="{SMILIES_PATH}/icon_e_sad.gif" alt=":(" title="Sad"> I recive a warning with a deadline on mail ( from Google Play)

    Mail (optional):

    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 use https://groups.google.com/forum/#!forum ... nssl.users or http://www.stackoverflow.com/questions.

    This is the second warning you’ve received from Google Play. In 60 days, we will not accept app updates containing the vulnerabilities. In addition, we will reject new apps containing the vulnerabilities.

    ... and they warned me about beeing banned for 3 apps like this.

    And in 60 (if i didn't solve this my game will be "banned")

    So what to do?

    I reexported the app again with Intel XDK and nothing changed...

    Do I must add anything else in Intel XDK/ C2?

    Thank You

  • got the same warning last night. perhaps it is because there are some people that never updated to my cw 10 build( i told many not to upgrade for obvious reasons). contemplating re-releasing my 7 build now,.. if i'm reading this correctly they will not pull the game, rather they will prevent any more updates/new releases?

  • Unfortunately, there has yet to be a resolution to this.

    I tried to get this resolved by contacting Google, but they basically said 'no, we won't fix it because it's really old'. I tried to point out that this was a unique case, and that the fix was elementary, but in the end it felt like I was trying to reason with the Daleks. Eventually they locked the bug, took up their plungers, and went home.

    Another avenue of appeal is to the crosswalk project itself. I suspect they may be a little more open to reason, but I haven't had time to write up a bug yet and submit it to them.

    Intel is being strange about this, in that they acted like they wanted to get this resolved, made a blog post about it...and then just dropped the ball. I'm glad they are being active in the forum, and a recent alpha of the latest crosswalk build looks to be a big improvement, but part of providing a reliable method of deployment is supporting the only freakin' version of the exporter that works well on less-than-bleeding-edge devices.

    tl;dr: Why the hell does it come down to users to resolve an issue like this? And what happens when a more significant bug crops up...?

    /rant

    P.S.

    No hard feelings at Scirra, I get that Ashley is crazy overloaded, and this really isn't their responsibility in the first place.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • [quote:avhxy6rg]Recently we sent you a notification that one or more of your apps should be upgraded to more recent version of OpenSSL, due to security vulnerabilities. The notification was sent in error, and we thank you for previously making the necessary changes to your app.

    We apologize for any confusion this may have caused.

    Regards,

    Google Play Team

    ©2015 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043

    Email preferences: You have received this mandatory email service announcement to update you about important changes to your Google Play Developer account.

    As mentioned in the other thread about this. Google just sent out this to us about the OpenSLL and they have dropped the warnings on the CW7 OpenSLL and wont be deleting the apps made in CW7.

    I have not made any changes and my games are all made in CW7. So I guess they accepted it now

  • Anonnymitet

    CW = Crosswalk ?

    headpain

    They said they will take down my app in 60 days ....

    TiAm

    The problem is since nov. 2014 why isn't a fix yet?

    Anonnymitet

    headpain

    TiAm

    What should I do now?

    Should I just wait. I dont know what CW version I made the game but I think that in 2 weeks I will republish my game...

    Thanks guys.

  • Radulepy The problem was the OpenSLL on crosswalk 7 and all other crosswalk versions had bad performance which made it impossible to switch. I also got the warnings from google but they now emailed me and said that they wont take down the apps made with cw7.

    So I guess that it is solved now. But if you want to republish it with another crosswalk version you can because it seems like they finally found a solution for the bad performance on the later crosswalk versions and you should be able to export the game with good performance again even if you are using crosswalk 10+

  • Anonnymitet

    OK, when did you gat that email?

    after how many days after you recived the warning dead line email?

  • I got the warning yesterday and the other mail today. But the last email ended up in my spam folder for some reason. But if you check the other thread you can see that others got the last email as well

  • Anonnymitet

    Bro, thanks you so much, I will keep you in touch.

  • I received again this information from Google, they will remove my app in July if I don't fix it.

    I was trying to rebuild my application using Crosswalk 10 but it crashes a lot.

    Does anyone have a good solution for this problem?

    Thank you!

  • I'd recommend rebuilding your app with the latest Crosswalk version (CW12?), although it has bad performance, and re-upload it to Google Play. I know that the performance sucks (thats's what my games will be suffering from, too), but your app being kicked from the Google Play Store is way worse. If Crosswalk improves in future versions, then you'll still have the possibility to re-upload your app with great performance. Just my thoughts.

    For my next project, I'll try exporting via PhoneGap build and will let you guys know how it worked out for me. Has anyone experiences with PhoneGap already? Also, is there a way to get to know the sign-code of apps which have been signed automatically via IntelXDK?

  • DMCunha

    I have just removed my app till I will buy a license and export it using cw 10+.

    In like 20 days I will publish it.

    I don't know what kind of crashes?

    Try rebuilding it with Cw 7 (more stable).

  • Radulepy, many times when game is running, it closes without error message.

    I published again using CW7 and there is no problem.

    Besides this problem, performance (FPS) is so poor..

    Below you can find log about crash.

    05-12 08:42:26.224 1428-26182/? W/Binder﹕ Caught a RuntimeException from the binder stub implementation.

    java.lang.NullPointerException

    at android.inputmethodservice.IInputMethodWrapper.setSessionEnabled(IInputMethodWrapper.java:280)

    at com.android.internal.view.IInputMethod$Stub.onTransact(IInputMethod.java:129)

    at android.os.Binder.execTransact(Binder.java:407)

    at dalvik.system.NativeStart.run(Native Method)

  • DMCunha

    ok, let's try to solve this.

    Try exporting your game with cw 7 and cw 10 than import on a regular phone ( Samsung, etc) DONT FORGER< FIRST TRY TO PLAY YOUR GAME WITH ARM Arhitecture and than with x86.

    What is about your game ( how many sprites per layout and particles?) why could be so poor fps ?

  • Hello,

    I'm still seeing Google Play alert about OpenSSL. I've contacted Google again (about a week ago), but they haven't responded. What can I do? I really don't want for Square Eater to be deleted on 7th July.

    EDIT: After calling Google 2 times, contacting them via email 3 times, "marking the alert as current", "Dismissing" the alert, selecting "There's a mistake", the alert has gone, I have no problems anymore.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)