Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-15 Thread Thiago Macieira
On Friday 15 May 2015 11:29:43 m...@rpzdesign.com wrote: > The problem as I see it is that Android has the OpenSSL libraries > already on the device and Qt just dynamically links to them. And that might be the reason why Google retracted the notice. QtNetwork is just loading the libs already in

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-15 Thread Nuno Santos
The truth is that I received the message and after 15 minutes I had received another email saying the last email was a mistake. Have you received such email from Google? Nuno Santos Founder / CEO / CTO www.imaginando.pt +351 91 621 69 62 > On 15 May 2015, at 18:29, m...@rpzdesign.com wrote: >

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-15 Thread Nuno Santos
I don’t know either. I just build the Qt app on QtCreator. I have never invested time in learning what is being linked or not. Sorry :/ Nuno > On 15 May 2015, at 18:14, Thiago Macieira wrote: > > On Friday 15 May 2015 07:13:55 rpzrpz...@gmail.com wrote: >> Thiago: >> >> What do you mean b

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-15 Thread m...@rpzdesign.com
Oops, Sorry. The message replies boundaries were not that clear. Nuno, do you have a comment on how to get the proper OpenSSL requirements met from Google Play. Are the Openssl libraries linked into the APK so all we have to do is rebuild with QtCreator and re-upload to google play? Or is the

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-15 Thread Thiago Macieira
On Friday 15 May 2015 07:13:55 rpzrpz...@gmail.com wrote: > Thiago: > > What do you mean by the phrase "Upgrade and re-load to Google" > > Are the OpenSSL libraries linked into the APK from your local NDK? > > Or are the OpenSSL libraries on the smartphone or tablet device already? > > Thanks f

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-15 Thread rpzrpz...@gmail.com
Thiago: What do you mean by the phrase "Upgrade and re-load to Google" Are the OpenSSL libraries linked into the APK from your local NDK? Or are the OpenSSL libraries on the smartphone or tablet device already? Thanks for your response, Mark On 5/7/2015 7:51 PM, Thiago Macieira wrote: > On T

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-07 Thread Nuno Santos
I have received another email: … 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

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-07 Thread Thiago Macieira
On Thursday 07 May 2015 21:54:54 Nuno Santos wrote: > I have just received this message from Google Play. > > Since I haven’t linked with OpenSSL explicitly, is there any chance of this > being an implicit link from Qt. Yes, QtNetwork links to OpenSSL (or, rather, loads it dynamically). But in o

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-07 Thread Jason H
terests Qt" Subject: Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities Hi,   I have just received this message from Google Play.   Since I haven’t linked with OpenSSL explicitly, is there any chance of this being an implicit link from Qt.   My app onl

Re: [Interest] Google Play 60-day deadline for resolving OpenSSL vulnerabilities

2015-05-07 Thread Nuno Santos
Hi, I have just received this message from Google Play. Since I haven’t linked with OpenSSL explicitly, is there any chance of this being an implicit link from Qt. My app only links with Parse (1.3.0) regarding external libraries. Does anyone else has received this message? Thanks, Regards,