Package Details: libcurl-openssl-1.0 7.79.1-1

Git Clone URL: https://aur.archlinux.org/libcurl-openssl-1.0.git (read-only, click to copy)
Package Base: libcurl-openssl-1.0
Description: An URL retrieval library (without versioned symbols, built against openssl-1.0)
Upstream URL: https://curl.haxx.se
Keywords: broken deprecated eol ftbfs to-be-deleted unneeded unused-lib
Licenses: MIT
Provides: libcurl-openssl-1.0.so
Submitter: fmauNeko
Maintainer: None
Last Packager: xuanruiqi
Votes: 36
Popularity: 0.000013
First Submitted: 2017-06-23 09:22 (UTC)
Last Updated: 2021-11-09 21:10 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

tyrannis.hawk commented on 2018-01-25 20:58 (UTC)

Stil getting ==> Verifying source file signatures with gpg... curl-7.57.0.tar.gz ... FAILED (unknown public key 5CC908FDB71E12C2)

Running "gpg --recv-keys --keyserver hkp://18.9.60.141 5CC908FDB71E12C2" solved the issue for me.

treeshateorcs commented on 2017-12-25 17:17 (UTC) (edited on 2017-12-25 23:39 (UTC) by treeshateorcs)

So, I want to build a sample app from github.com/deezer, but the Deezer Native API is built against openssl-1.0. I installed openssl-1.0 package, and also this one. when I run ldd on the .so file that comes with this API, it tells me this

$ LD_PRELOAD=/usr/lib/libcurl-openssl-1.0/libcurl.so.4.4.0 ldd libdeezer.so

ldd: warning: you do not have execution permission for `./libdeezer.so'

./libdeezer.so: /usr/lib/libcurl-openssl-1.0/libcurl.so.4.4.0: no version information available (required by ./libdeezer.so)

linux-vdso.so.1 (0x00007ffeb47e4000)

/usr/lib/libcurl-openssl-1.0/libcurl.so.4.4.0 (0x00007f931e5ae000)

....

How do I fix this error?

UPDATE: As a workaround I built a docker container based on debian jessie, compiled the sample app in it, and now I can run it on my host using LD_PRELOAD

gustavolcorreia commented on 2017-12-19 20:35 (UTC)

Thanks @arifur solved for me too!

rahatzamancse commented on 2017-11-15 23:56 (UTC)

gpg --recv-keys --keyserver hkp://18.9.60.141 5CC908FDB71E12C2 As @RyanH said, this worked for me also. Running manjaro deepin. After the update for gitkraken, cant use it without this package. Wishing for a fix soon.

berserkingyadis commented on 2017-11-15 11:15 (UTC)

Got the same issue with the unknown public key. Solved the issue with the solution from the link of someDude gpg --recv-keys 5CC908FDB71E12C242. Can this package be modified (PKGBUILD) so this error does not happen anymore?

someDude42 commented on 2017-11-13 23:07 (UTC)

This solution is way easier than downgrading gpg: https://superuser.com/questions/1210758/error-one-or-more-pgp-signatures-could-not-be-verified-arch-linux#1210759

ajsantander commented on 2017-11-09 13:42 (UTC)

I found that I wasnt able to use the gpg command to trust the signature because of a known problem with gpg. See https://www.reddit.com/r/archlinux/comments/5jyxv8/gpg_keyserver_receive_failed_server_indicated_a/?st=j9sia13i&sh=6b98472e I downgraded gpg as explained in that post and was then able to use the commands exposed here. Gitkraken then installs fine.

arifur commented on 2017-11-05 21:09 (UTC)

gpg --recv-keys 5CC908FDB71E12C2 Solved my issues

RyanH commented on 2017-09-17 11:40 (UTC)

gpg --recv-keys --keyserver hkp://18.9.60.141 5CC908FDB71E12C2 Worked for me as of comment date on system running Manjaro KDE. Had been driving me crazy for a few weeks so even if this comment is misplaced I hope this is helpful to others.

« First ‹ Previous 1 2 3 4 5 Next › Last »