F-9116: apply the requested verify mode when the setVerify callback cannot be registered
parent
cf37bf963c
commit
c6763af087
|
|
@ -4997,7 +4997,8 @@ JNIEXPORT void JNICALL Java_com_wolfssl_WolfSSLSession_setVerify
|
|||
*verifyCb = (*jenv)->NewGlobalRef(jenv, callbackIface);
|
||||
if (*verifyCb == NULL) {
|
||||
printf("error storing global callback interface\n");
|
||||
XFREE(verifyCb, NULL, DYNAMIC_TYPE_TMP_BUFFER);
|
||||
XFREE(verifyCb, NULL, DYNAMIC_TYPE_TMP_BUFFER);
|
||||
verifyCb = NULL;
|
||||
}
|
||||
else {
|
||||
/* Publish under g_verifyCbMutex so a concurrent callback
|
||||
|
|
@ -5010,6 +5011,11 @@ JNIEXPORT void JNICALL Java_com_wolfssl_WolfSSLSession_setVerify
|
|||
wolfSSL_set_verify(ssl, mode, NativeSSLVerifyCallback);
|
||||
}
|
||||
}
|
||||
|
||||
/* If callback could not be registered, still apply requested mode */
|
||||
if ((appData == NULL) || (verifyCb == NULL)) {
|
||||
wolfSSL_set_verify(ssl, mode, NULL);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue