There is now a wolfssl branch with wolfssl 4.7.0 but something seems to have changed that breaks our code, or wolfssl has a bug. Added error reporting code shows that the function wolfSSL_X509_verify() is now returning 0 instead of 1, which prevents the node from making any p2p connections
There is now a `wolfssl` branch with wolfssl 4.7.0 but something seems to have changed that breaks our code, or wolfssl has a bug. Added error reporting code shows that the function `wolfSSL_X509_verify()` is now returning 0 instead of 1, which prevents the node from making any p2p connections
@jahway603 at the very least, we should report to wolfssl on github that they inadvertently broke backward compat between 4.6.0 and 4.7.0. Last I looked, there were no tests for some of the functions that we use. Maybe we get lucky and 5.4.0 works for us, but the complication is that we also need to make sure the new code can talk to the old code, otherwise new hush nodes will not be able to talk to Hush nodes using wolfssl 4.6.0
@jahway603 at the very least, we should report to wolfssl on github that they inadvertently broke backward compat between 4.6.0 and 4.7.0. Last I looked, there were no tests for some of the functions that we use. Maybe we get lucky and 5.4.0 works for us, but the complication is that we also need to make sure the new code can talk to the old code, otherwise new hush nodes will not be able to talk to Hush nodes using wolfssl 4.6.0
There is now a
wolfsslbranch with wolfssl 4.7.0 but something seems to have changed that breaks our code, or wolfssl has a bug. Added error reporting code shows that the functionwolfSSL_X509_verify()is now returning 0 instead of 1, which prevents the node from making any p2p connectionsSince version 5.4.0 was released 4 days ago, it might be time to re-eval this
@jahway603 at the very least, we should report to wolfssl on github that they inadvertently broke backward compat between 4.6.0 and 4.7.0. Last I looked, there were no tests for some of the functions that we use. Maybe we get lucky and 5.4.0 works for us, but the complication is that we also need to make sure the new code can talk to the old code, otherwise new hush nodes will not be able to talk to Hush nodes using wolfssl 4.6.0