Parity-ethereum: libssl1.0.0 is not available anymore

Created on 21 Jun 2017  路  19Comments  路  Source: openethereum/parity-ethereum

Do you plan to migrate to the libssl 1.1.0f-3 available in newly release debian stable?

F2-bug 馃悶 M0-build 馃彈 P5-sometimesoon 馃尣

Most helpful comment

If you wish to use parity on Debian 9 ( stretch ) you need download the package from https://packages.debian.org/jessie/libssl1.0.0 and install like dpkg --install libssl1.0.0_1.0.1t-+deb8u6_amd64.deb as root. For me works.

All 19 comments

ssl 1.1.0 has been around for a while, if dinosaurs like debian make the switch, we are probably good to do that, too :+1:

Is this already fixed by PR #4260 ?

No, PR #4260 introduced this issue.

Actually, can you build and release static binary of parity?

If you wish to use parity on Debian 9 ( stretch ) you need download the package from https://packages.debian.org/jessie/libssl1.0.0 and install like dpkg --install libssl1.0.0_1.0.1t-+deb8u6_amd64.deb as root. For me works.

Or just build parity from source.

@5chdn the problem is that stretch does not have this old version in package manager. how can you build one without dependency?

@iFA88 not ideal for production environment

@calvintam236 building from source just links the binary against any available libssl version.

This issue is that the precompiled binaries link against a certain version. But Ubuntu didn't make the switch to 1.1.x yet.... It's really hard to understand why. The only things I can recommend here is either stop using Debian-based systems or compile from source :)

@5chdn that's why I suggest to release a static build binary - all dependencies are included the binary, so it can run on any Linux.

@calvintam236 We are running parity in a docker container for production, that solves all the issues with dependencies.

Could anyone check if our debian binaries/packages work?

Parity/v1.8.4-beta-c74c8c1-20171211/x86_64-linux-gnu/rustc1.22.1 Works on 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) but i have separated installed the libssl. On my other debian:
image

Ok, thanks for confirming.

I ran the binary in docker using base debian:stretch-slim. I get this error with libssl1.1 installed: parity: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory. Tried installing binary on the same container, same error @iFA88 have.

On it. We have a debian pipeline, I just need to figure out why it does not link the new ssl lib.

Parity also requires gcc, g++, libssl-dev/openssl, libudev-dev and pkg-config packages to be installed.
See pls https://github.com/paritytech/parity/blob/master/README.md#build-dependencies

Someone with Debian, please test if this works for you!

debian | x86_64 | ethkey | 350fb2550e01243dff41670d65d73fe3
debian | x86_64 | ethstore | a694cc4c085968d68b14dc1a322fdda2
debian | x86_64 | parity-evm | a16da5032c77b66f782bb3b7e4887188
debian | x86_64 | parity_1.10.0_amd64.deb | f5d313ad9ea6b980feac2b9fe9837dcf
debian | x86_64 | parity | d820ef51b34f79a62abe46e224df4f33

Preferable on a system that has no custom libssl 1.0.x - thanks!

Ok was able to test this. It's working now. Next release will contain deb for Debian!

And CentOS

screenshot at 2018-01-17 16-48-41

Was this page helpful?
0 / 5 - 0 ratings

Related issues

vmenond picture vmenond  路  3Comments

jacogr picture jacogr  路  4Comments

bryaan picture bryaan  路  3Comments

retotrinkler picture retotrinkler  路  3Comments

uluhonolulu picture uluhonolulu  路  3Comments