Skip to content
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

Cannot sign windows binary in electronuserland/builder:wine because libcrypto.so.1.1 doesn't exist #7092

Closed
asmsuechan opened this issue Aug 26, 2022 · 6 comments · Fixed by #7109
Labels

Comments

@asmsuechan
Copy link

asmsuechan commented Aug 26, 2022

  • Electron-Builder Version: 23.4.0
  • Node Version: 16.13.1
  • Electron Version: 16.0.7
  • Electron Type (current, beta, nightly): current
  • Target: windows

Hi, developers. My electron build fails with the following error after electronuserland/builder:wine is updated.

/root/.cache/electron-builder/winCodeSign/winCodeSign-2.6.0/linux/osslsigncode: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

My situation: I build an electron app inside electronuserland/builder:wine container.

I investigated the new container and found that the version of libcrypto isn't 1.1, it's 3.

root@1c6f31ac3c40:/project# find / | grep libcrypto
/usr/lib/x86_64-linux-gnu/libcrypto.so.3
/usr/lib/x86_64-linux-gnu/pkgconfig/libcrypto.pc
/usr/lib/x86_64-linux-gnu/libcrypto.a
/usr/lib/x86_64-linux-gnu/libcrypto.so
/usr/lib/i386-linux-gnu/libcrypto.so.3

I guess that's because of container image update to Ubuntu 22.04 in this commit.

Note: I use electronuserland/builder:wine-chrome-05.21 to avoid this error.

Do you plan to make electron-builder use OpenSSL 3.0 instead of 1.1? Or, are there some smart answers to solve my problem?

Thank you.

Edited: People who need a workaround for now

  • Use electronuserland/builder:wine-chrome-05.21 instead of electronuserland/builder:wine
  • Update GPG key by wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -
@NeuralMayu
Copy link

Please ask how you use electronuserland/builder:wine-chrome-05.21 to avoid this error ?

@asmsuechan
Copy link
Author

@NeuralMayu I changed the image from electronuserland/builder:wine to electronuserland/builder:wine-chrome-05.21 and updated GPG key by wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -. Other flows are same.

@NeuralMayu
Copy link

@NeuralMayu I changed the image from electronuserland/builder:wine to electronuserland/builder:wine-chrome-05.21 and updated GPG key by wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -. Other flows are same.

the electronuserland/builder is electron-userland/electron-builder ?

@asmsuechan
Copy link
Author

No, it's not. As this page https://hub.docker.com/r/electronuserland/builder/tags shows, the container is electronuserland/builder.

@acutus
Copy link

acutus commented Aug 26, 2022

Ran into this as well. Thank you @asmsuechan for investigating and providing a workaround.

@Muukuro
Copy link

Muukuro commented Aug 26, 2022

Yup, same issue here. I managed to work around it by using electronuserland/builder:14-wine-05.22 instead of electronuserland/builder:wine (thanks @asmsuechan!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants