-
Notifications
You must be signed in to change notification settings - Fork 431
OpenSSL lower 1.02f/1.01r is vulnerable and not recommended by Google #129
Comments
Thanks for the heads up. We will definitely update the libraries much before the deadline. |
We merged #130 and added one more commit, so now we are using OpenSSL1.0.2g. Thanks again! |
Hello Everyone,I got the following mail from google developer console account- Hello Google Play Developer, Vulnerability APK Version(s) Actually i am using C sip simple library for VoIP calling , and in that i am using pjsplib.so files , in that library open ssl is used in project.Can anyone help me please what should i do, because my app is live on play store and it is rejecting again and again because of this issue.Please help me. Thanks . |
To the developer having troubles with psjplib.so. I would use all the ways Said that: A) if that library uses openssl as a separate .so you could replace it for B) if that library uses openssl and generates a single .so (which is what Good luck! On Mon, Sep 12, 2016 at 11:18 PM, shree notifications@github.com wrote:
|
Hello, Thanks for replying , i will check this. On Thu, Sep 15, 2016 at 9:54 PM, Helios notifications@github.com wrote:
Thanks and Regards Website : http://www.advantal.net/ CONFIDENTIALITY NOTICE: This email and attachments are private, |
I had this issue, I resolved issue by below steps: The cause of the issue is the libavformat.so file which is using OpenSSL 1.0.2d. We need to update it. But, just updating libavformat.so will cause crashing, so we need to update all relating lib (javacv and javacpp).
Reference - sourab-sharma/TouchToRecord#23 |
I've got a email from Google Play about Openssl vulnerability.
According to release tag, the latest version of conceal is using openssl 1.0.2e.
Could you update it to OpenSSL 1.02f/1.01r or higher?
The text was updated successfully, but these errors were encountered: