![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205042
https://bugzilla.suse.com/show_bug.cgi?id=1205042#c32
--- Comment #32 from Pedro Monreal Gonzalez
I've checked with embedded openssl in nodejs19 and sadly I'm getting similar results with failed unit tests. I will have to look at this more closely - perhaps I'm doing things wrong there.
Thanks for checking this. I'm also looking into this also from the openssl side.
In the meantime, I've prepared nodejs19 to build with openssl-1_1 but when trying to build against Staging:N with openssl-3 as default, I cannot install 1.1.1 openssl,
[ 8s] now installing cumulated packages [ 9s] Preparing... ######################################## [ 9s] file /etc/ssl/openssl.cnf conflicts between attempted installs of openssl-1_1-1.1.1s-2.4.x86_64 and libopenssl3-3.0.7-2.11.x86_64 [ 9s] exit ... [ 9s]
It seems the config file is part of a shared library?
In Staging:N, the actual openssl-1_1 ships openssl.cnf and I have modified it to be called openssl-1_1.cnf for the transition-to-default-openssl but this new version is not yet in Staging:N, that should fix the conflict. I'll submit sometime today as there is a running security update for openssl-3 in the middle. I have also moved the config file to be shipped by the library since it can be installed without the CLI and I think it should be the right package to ship it. But, we can keep the cnf file in the CLI if both packages should be installed always together. -- You are receiving this mail because: You are on the CC list for the bug.