boringssl

解决“warning C4819: 该文件包含不能在当前代码页(936)中表示的字符。请将该文件保存为 Unicode 格式以防止数据丢失”的问题

由 拥有回忆 提交于 2020-02-27 00:37:47
最近在编译dart-sdk里的boringssl时遇到以下错误 warning C4819: 该文件包含不能在当前代码页(936)中表示的字符。请将该文件保存为 Unicode 格式以防止数据丢失 之前是靠把所有几十个源文件全部手动从ansi改为Unicode的撒币方法，虽然有效，但是太麻烦，还破坏了git代码版本，非常糟糕 几分钟前百度搜索“修改 cl.exe 默认使用utf8”时，垃圾百度显示的都是毫无关系的东西，简直令人想拿刀把李彦宏扌甬死，不过他也算干了件好事，如果没有把杂七杂八的没啥关系的搜索结果列出来，特别是把百度经验“ win10 设置系统默认编码为utf-8 ”这个自家东西排到第一名位置，我也就想不到试试这个方法了。 经过试验，把win10 设置系统默认编码为utf-8之后，就不报错了。真是皆大欢喜。 随便推测了下，VS的这个编译器可能应该或许是从系统设置里获取了默认的编码，系统原来是gbk(CP936)，改成utf8后，编译器就自动从936改成utf8的方式来默认处理代码了。 鉴于百度谷歌上都搜不到我这方法（至少两三页内没看到），我便在这里分享给大家，希望能帮大家解决问题。 又去看了下，该百度经验提示： win10系统支持默认编码修改.。 好处： 解决由utf8引起的cmd，powershell等乱码问题 Visual Studio 2017(其他版本没试过）

opentok-android-sdk-2.3.1 and OpenSSL vulnerability issue

由 你说的曾经没有我的故事 提交于 2019-12-24 17:28:10
问题 I have an app on Google play store. Recently i got a mail subjected: Google Play 60-day deadline for resolving OpenSSL vulnerabilities It states that i'm using a version of OpenSSL, which is vulnerable to some issues. However, i'm not using OpenSSL directly. I'm using OpenTok library for Video chatting feature, which internally uses OpenSSL. I'm currently using openTok SDK version 2.3.1. But according to this link http://www.tokbox.com/blog/mobile-sdks-2-2-1-resolve-openssl-vulnerability/ all

Linking errors in OpenSSL library

由 ≯℡__Kan透↙ 提交于 2019-12-24 00:38:48
问题 I am using OpenSSL in my project.library is detecting but getting some errors like below: Error:(23) undefined reference to 'RSA_generate_key' Error:(44) undefined reference to 'AES_set_encrypt_key' Error:(45) undefined reference to 'AES_encrypt' Error:(49) undefined reference to 'AES_set_decrypt_key' Error:(50) undefined reference to 'AES_decrypt' Error:error: linker command failed with exit code 1 (use -v to see invocation) my simple cpp code is here native-lib.cpp #include<jni.h> #include

Qt for Android and BoringSSL

由 こ雲淡風輕ζ 提交于 2019-12-22 08:41:08
问题 I'm developing a Qt-based app for Android, which uses QSslSocket to download data. Due to Android's moving away from OpenSSL to BoringSSL since Marshmallow Qt programs, relying on the OpenSSL library, produce the following warnings on Android 6+: W libtestopenssl.so: (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve CRYPTO_free W libtestopenssl.so: (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve EVP_CipherFinal W libtestopenssl.so: (null):0 ((null)): qt.network.ssl:

-fobjc-weak is not supported on the current deployment target

由 江枫思渺然 提交于 2019-12-12 19:21:35
问题 I just updated my Pods and one of them BoringSSL is now eroring my build with following error: Apple LLVM 9.0 Error -fobjc-weak is not supported on the current deployment target Not sure about what I need to do here? Is this an issue with BoringSSL package or my project? EDIT I believe this is used by grpc ? 回答1: This is CocoaPods/Xcodeproj#544 for which a fix was released recently. Update the Xcodeproj gem from 1.5.5 to 1.5.6. 来源： https://stackoverflow.com/questions/48643389/fobjc-weak-is

error:0c0890ba:ASN.1 encoding routines:asn1_check_tlen:WRONG_TAG

由 元气小坏坏 提交于 2019-12-12 09:25:05
问题 I am trying to implement ssl support in my volley request (also I saw answers in SO with similar issues, but it does not help me) With help of this article I converted my certificate extension from .cer to .bks That according to this SO answer I do next mRequestQueue = Volley.newRequestQueue(this, hurlStack); private HurlStack hurlStack = new HurlStack() { @Override protected HttpURLConnection createConnection(URL url) throws IOException { HttpsURLConnection httpsURLConnection =

Make a Android application use FIPS 140-2 valiated cryptography

由 |▌冷眼眸甩不掉的悲伤 提交于 2019-12-10 08:09:39
问题 I have client who wants our application to use FIPS 140-2 validated cryptography. The app uses Okhttp and does some HTTPS requests. AFAIK Android uses OpenSSL C library and uses java wrapper javax/net/ssl. Questions: How to make android Application FIPS 140 -2 Complaint? Is it not android at stack(OS) level should use FIPS Compliant OpenSSL, hence all app are default FIPS 140 -2 Compliant? Or our app should use FIPS 140-2 validated cryptography and make java javax/net/ssl to use it? Feasible?

error:0c0890ba:ASN.1 encoding routines:asn1_check_tlen:WRONG_TAG

由 生来就可爱ヽ(ⅴ＜●) 提交于 2019-12-04 19:50:56
I am trying to implement ssl support in my volley request (also I saw answers in SO with similar issues, but it does not help me) With help of this article I converted my certificate extension from .cer to .bks That according to this SO answer I do next mRequestQueue = Volley.newRequestQueue(this, hurlStack); private HurlStack hurlStack = new HurlStack() { @Override protected HttpURLConnection createConnection(URL url) throws IOException { HttpsURLConnection httpsURLConnection = (HttpsURLConnection) super.createConnection(url); try { httpsURLConnection.setSSLSocketFactory(getSSLSocketFactory()

SSL_ERROR_SSL(1): operation failed within the library

由 旧街凉风 提交于 2019-12-02 15:45:38
I am getting some SSL Error s (which are causing my project to stop/hang with no crash as I have a DispatchGroup waiting for the request), which I don't know how they are caused, what they are, or what to do about it. I have read numerous pages roughly about this problem, but there are not much documentation or people having the same problem. I have tried changing the info.plist but that doesn't seem to have helped. Both plist 's look like this: ( accounts.spotify.com is the domain for the URL of the access token request) I can see that my code is failing when I make a request to the server.

Compile OpenSSL to different name due to Android Zygote

由 亡梦爱人 提交于 2019-12-02 07:57:54
问题 I can build openssl-1.0.2j successfully for android (libcrypto.so and libssl.so) using GitHub stdchpie/android-openssl: Environment: Linux OS, (my case I use Mac OS) Android NDK: 12b On Android 5.x if using: System.loadLibrary("crypto"); System.loadLibrary("ssl"); It will get conflict with native OS libs which also have same names. And unluckily, manually change their names didn't work. So that I want to compile them into different names , like libcryptox.so and libsslx.so I try to play with
订阅 boringssl