“ javax.net.ssl.SSLHandshakeException:握手失败”即使添加了自定义TrustManager和证书固定之后

时间:2019-09-10 18:27:02

标签: android kotlin retrofit2 sslhandshakeexception x509trustmanager

我打算使用 Jamendo API 下载音乐,但是在连接到API时抛出了以下错误

javax.net.ssl.SSLHandshakeException: Handshake failed
        at com.android.org.conscrypt.ConscryptFileDescriptorSocket.startHandshake(ConscryptFileDescriptorSocket.java:286)
        at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.kt:351)
        at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.kt:310)
        at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:178)
        at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:236)
        at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:109)
        at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:77)
        at okhttp3.internal.connection.Transmitter.newExchange$okhttp(Transmitter.kt:162)
        at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:35)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
        at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:82)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
        at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:84)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
        at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:71)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
        at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
        at okhttp3.RealCall.execute(RealCall.kt:66)
        at com.example.musicplayer.utils.CertificatePinningKt.certificatePinning(CertificatePinning.kt:26)
        at com.example.musicplayer.fragments.HomeFragment$onActivityCreated$1$1.invokeSuspend(HomeFragment.kt:42)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:740)
     Caused by: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xedb6ee48: Failure in SSL library, usually a protocol error
    error:100000f0:SSL routines:OPENSSL_internal:UNSUPPORTED_PROTOCOL (external/boringssl/src/ssl/handshake_client.cc:576 0xe5faba43:0x00000000)
        at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
        at com.android.org.conscrypt.NativeSsl.doHandshake(NativeSsl.java:375)
        at com.android.org.conscrypt.ConscryptFileDescriptorSocket.startHandshake(ConscryptFileDescriptorSocket.java:224)
            ... 27 more

然后我知道Android并不知道某些CA证书,而解决办法是启用 TrustManager 以不对 https 请求进行任何验证,例如接受this SO post的答案,或添加自定义 TrustManager 以接受需要与according to this google doc 通信的服务器的CA证书,于是我采用了后一种方法。

!)首先,我使用以下命令

检查了 Jamendo的服务器信息
$ openssl s_client -connect jamendo.com:443 | openssl x509 -noout -subject -issuer

这将导致

  

depth = 3 C =美国,O =“ Go Daddy Group,Inc。”,OU = Go Daddy 2类证书颁发机构   验证返回:1
  深度= 2 C =美国,ST =亚利桑那州,L =斯科茨代尔,O =“ GoDaddy.com,Inc。”,CN = Go Daddy根证书颁发机构-G2   验证返回:1
  depth = 1 C =美国,ST =亚利桑那州,L =斯科茨代尔,O =“ GoDaddy.com,Inc。”,OU = {http://certs.godaddy.com/repository/,CN = Go Daddy安全证书颁发机构-G2   验证返回:1
  深度= 0 C = LU,L =卢森堡,O = Jamendo SA,CN = .jamendo.com   验证返回:1
  subject = / C = LU / L =卢森堡/ O = Jamendo SA / CN =
.jamendo.com   发行者= / C = US / ST =亚利桑那州/L=Scottsdale/O=GoDaddy.com,Inc./OU=http://certs.godaddy.com/repository//CN=Go爸爸安全证书颁发机构-G2

看起来 Jamendo 正在使用 GoDaddy的托管服务,所以我转到了他们的certification page,如上面的输出所示,使用的证书来自< em> G2 组,所以我下载了输出中提到的 root intermediate 证书(前两个)。

2)而且然后,我尝试创建自定义的 SSLSocketFactory TrustManager ,这会导致相同的错误。 该方法显示在以下代码中

fun getCACertificateAndroid(resources: Resources): Pair<SSLSocketFactory, X509TrustManager> {
    val cf: CertificateFactory = CertificateFactory.getInstance("X.509")

    //  certificate 1
    var caInput: InputStream = resources.openRawResource(R.raw.gdig2)
    val ca: X509Certificate = caInput.use {
        cf.generateCertificate(it) as X509Certificate
    }
    Log.d("GetCACertificateAndroid", "getCACertificateAndroid: ca= + ${ca.subjectDN}")

    //  certificate 2
    caInput = resources.openRawResource(R.raw.gdroot_g2)
    val ca1: X509Certificate = caInput.use {
        cf.generateCertificate(it) as X509Certificate
    }
    Log.d("GetCACertificateAndroid", "getCACertificateAndroid: ca1= + ${ca1.subjectDN}")

    // Create a KeyStore containing our trusted CAs
    val keyStoreType = KeyStore.getDefaultType()
    val keyStore = KeyStore.getInstance(keyStoreType).apply {
        load(null, null)
        setCertificateEntry("ca", ca)
        setCertificateEntry("ca1", ca1)
    }

    // Create a TrustManager that trusts the CAs inputStream our KeyStore
    val tmfAlgorithm: String = TrustManagerFactory.getDefaultAlgorithm()
    val tmf: TrustManagerFactory = TrustManagerFactory.getInstance(tmfAlgorithm).apply {
        init(keyStore)
    }

    // Create an SSLContext that uses our TrustManager
    val context: SSLContext = SSLContext.getInstance("TLS").apply {
        init(null, tmf.trustManagers, null)
    }


    return Pair(context.socketFactory, tmf.trustManagers[0] as X509TrustManager)
}

其他一些文件

...

val (_sslSocketFactory, x509tTrustManager) = getCACertificateAndroid(resources)

    val client = OkHttpClient.Builder()
        .sslSocketFactory(_sslSocketFactory, x509tTrustManager)
        .build()

    val gson = GsonBuilder()
        .setLenient()
        .create()

    val retrofit = Retrofit.Builder()
        .baseUrl("https://api.jamendo.com/v3.0/playlists/?client_id=c7668145&format=jsonpretty&namesearch=cool") //   "https://storage.googleapis.com/"
        .addConverterFactory(GsonConverterFactory.create(gson))
        .client(client)
        .build()

...

3)然后,我开始了解证书固定 in OKHttp,并考虑通过获取 base64编码下载的证书

openssl x509 -in cert.crt -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64

基于this post的可接受答案,然后尝试运行以下代码,但错误仍然存​​在。

fun certificatePinning() {
    val hostname = "api.jamendo.com/v3.0/playlists/?client_id=c7668145&format=jsonpretty&namesearch=cool"
    val sha256base64_hash1 = "sha256/Ko8tivDrEjiY90yGasP6ZpBU4jwXvHqVvQI0GS3GNdA="
    val sha256base64_hash2 = "sha256/8Rw90Ej3Ttt8RRkrg+WYDS9n7IS03bk5bjP/UXPtaY8="


    val certificatePinner = CertificatePinner.Builder()
        .add(hostname, sha256base64_hash1)
        .add(hostname, sha256base64_hash2)
        .build()
    val client = OkHttpClient.Builder()
        .certificatePinner(certificatePinner)
        .build()

    val request = Request.Builder()
        .url("https://$hostname")
        .build()
    client.newCall(request).execute()
}

如果有人可以指出正确的方向,那将是很大的帮助。

2 个答案:

答案 0 :(得分:1)

握手问题是由于Jamendo API使用的旧版TLS协议版本(1.0)已弃用,并且不支持更新的协议版本:
* https://github.com/square/okhttp/issues/4670 * https://medium.com/square-corner-blog/okhttp-3-13-requires-android-5-818bb78d07ce

旁注:我会绝对反对自定义TrustManager实施,这只会有意义,例如如果您的端点使用的是自签名证书。作为一项基本检查,我将尝试通过直接在电话/仿真器浏览器上打开Jamendo URL来查看您是否遇到任何问题,从而验证您的Android System TrustStore是否正常运行?固定提供了额外的保护,但不能解决您遇到的基本握手问题。

答案 1 :(得分:1)

检查您的“ TLS”支持。我已经遇到了这个问题。在我的应用程序中,我使用了改造库。因此,请尝试将“ COMPATIBLE_TLS”配置添加到您的OkHttpClient中,例如:

OkHttpClient client = new OkHttpClient();
List<ConnectionSpec> connectionSpecs = new ArrayList<>();
connectionSpecs.add(ConnectionSpec.COMPATIBLE_TLS);
client.setConnectionSpecs(connectionSpecs);
...

至少将gradle中的库更新到v2.7.5,例如:

implementation 'com.squareup.okhttp:okhttp:2.7.5'