New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build error with libressl 2.4.5 #3163
Comments
preliminary patch: --- JohnTheRipper-0d089b16ea1d77ec4dcebcbf2cca7e3ece9feaaa.org/src/gpg_common_plug.c
+++ JohnTheRipper-0d089b16ea1d77ec4dcebcbf2cca7e3ece9feaaa/src/gpg_common_plug.c
@@ -1077,7 +1077,7 @@
error();
}
-#if OPENSSL_VERSION_NUMBER >= 0x10100000
+#if 0 && OPENSSL_VERSION_NUMBER >= 0x10100000
DSA_get0_pqg(dsa, &p, &q, &g);
DSA_get0_key(dsa, &pub_key, &priv_key);
error = BN_mod_exp(res, g, priv_key, p, ctx);
@@ -1571,7 +1571,7 @@
OPENSSL_free(str);
if (gpg_common_cur_salt->pk_algorithm == PKA_DSA) { /* DSA check */
-#if OPENSSL_VERSION_NUMBER >= 0x10100000
+#if 0 && OPENSSL_VERSION_NUMBER >= 0x10100000
DSA *dsa = DSA_new();
BIGNUM *p, *q, *g, *pub_key, *priv_key;
|
So LibreSSL did not drop those functions yet? Is there a macro we can check for that indicates we're actually dealing with LibreSSL? |
I read it the wrong way: OpenSSL has to be new enough. LibreSSL apparently don't mimic OPENSSL_VERSION_NUMBER? |
I see this in my patch for wpa_supplicant 2.5: -#if OPENSSL_VERSION_NUMBER >= 0x10002000L
+#if OPENSSL_VERSION_NUMBER >= 0x10002000L && !defined(LIBRESSL_VERSION_NUMBER) |
I suspect the proper way might be to make a configure check "whether openssl library has DSA_get0_pqg" and then in the code: |
RFC solar, I have not idea if magnum has a good internet connection; anyway, this kind of bug is a good reason to install docker on one Openwall's test machine:
|
Solar is @solardiz here! FWIW I think we should get rid of OpenSSL (et al) dependencies ASAP. We have code for damn near everything in our tree already, yet we're using OpenSSL (which isn't even faster). |
We don't have own code for doing RSA/DSA asymmetric crypto stuff (yet). |
Could be copied from libtomcrypt, which is under the WTFPL. |
@kholia could you please refrain from "correcting" my caps? thanks. after all, this is not a grammar contest here. |
@rofl0r Hi! Sorry about that. I find that correctly formed sentences are easier and more pleasant to read, and follow. The "no caps" style is perhaps suitable for IRC communication but using well formed sentences seems more suitable on GitHub. |
The text was updated successfully, but these errors were encountered: