Hi Ryan! Thanks for the reply.
Bob's reply was quite helpful already with his hint that nothing should link against softokn3 or freebl. This was a bug in pkgsrc previously, but I fixed it after his message. Nothing in pkgsrc now links against either of the two directly. I think I followed all of his advice. nss seems to take great care to be interoperable with openssl. But I still don't understand how this works in detail. Perhaps you can shed some more light on this to help me debug this problem. Bob wrote that NSS hides the conflicting symbols through a dynamically loaded object and a function table. I assume this means using dlopen(). I'm not sure about the function table. I looked at the code a bit and see that HASH_Update calls a function indirectly, which in pk11cxt.c is forwarded and finally used in pkcs11c.c - which however, then uses the wrong function, the one from openssl. Can you please explain in more detail how the function table works? In my case, it seems the wrong MD5_Update function is used when openssl is linked into the binary. Perhaps it's a difference in linker behavior on NetBSD? As for pkgsrc - I cited the patches in my original email. The whole package information is [1], the Makefile contains the flags used when compiling and the patches directory the patches used. If you see what the problem is, that'd be very helpful, but I don't think it's something that's something obvious any longer. [1] https://github.com/NetBSD/pkgsrc/tree/trunk/devel/nss Thanks, Thomas -- You received this message because you are subscribed to the Google Groups "dev-tech-crypto@mozilla.org" group. To unsubscribe from this group and stop receiving emails from it, send an email to dev-tech-crypto+unsubscr...@mozilla.org. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/20210416181236.hjso6ogynzwzm3ml%40yt.nih.at.
