[SOLVED] I just broke my system by downgrading openssl -- how to fix?

pgoetz · 2017-05-17 15:24:07

I did an upgrade this morning which broke my imapd server. Suspecting that the culprit was openssl, I downgraded from openssl-1.1.0.e-1-x86_64.pkg.tar.xz to openssl-1.0.2.k-1-x86_64.pkg.tar.xz to see if this resolved the imapd issue. Big mistake. Now pacman, curl, etc. are all nonfunctional, and of course without pacman I can't restore openssl-1.1.0.e-1-x86_64.pkg.tar.xz.

Just checking to see if the only solution is to boot from a distribution USB/CD, mount the root partition, and then run

pacman --root /mnt  -S openssl

The server is at a remote location, which means I need to travel to boot from USB.

Last edited by pgoetz (2017-05-18 09:08:04)

ayekat · 2017-05-17 15:28:42

You can unpack the library files from /var/cache/pacman/pkg/openssl-1.1.0.e-1-x86_64.pkg.tar.xz and put them into their respective locations under /usr/lib as a temporary workaround.

Also, what imapd server are you using? If it is properly maintained (and you didn't do a partial upgrade), it should now depend on the `openssl-1.0` package (or simply be rebuilt agains OpenSSL 1.1).

Last edited by ayekat (2017-05-17 15:29:57)

pgoetz · 2017-05-17 15:56:20

ayekat wrote:

Also, what imapd server are you using? If it is properly maintained (and you didn't do a partial upgrade), it should now depend on the `openssl-1.0` package (or simply be rebuilt agains OpenSSL 1.1).

Thanks for the tip on upacking the package!

I'm using Cyrus imapd from the AUR. I've used both Dovecot and Cyrus for years, and with the developer effort from Fastmail, cyrus seems to be a better tool. The problem is the AUR package maintainer has allowed the package to get wildly out of date, so the version in AUR (2.5.10) apparently doesn't work with OpenSSL 1.1.

Scimmia · 2017-05-17 15:57:09

Instead of putting them in /usr, just unpack it to a temp dir and set LD_LIBRARY_PATH to point to the dir the libs are in. That should let you update the system again.

Last edited by Scimmia (2017-05-17 15:57:33)

ayekat · 2017-05-17 16:00:33

pgoetz wrote:

The problem is the AUR package maintainer has allowed the package to get wildly out of date, so the version in AUR (2.5.10) apparently doesn't work with OpenSSL 1.1.

So have you tried installing the openssl-1.0 package to see if it makes cyrus-imapd work again? If that works, you could notify the maintainer to add it as a dependency.

--edit--
@Scimmia, ah yes, that seems more elegant. I was thinking about using --force, so...

Last edited by ayekat (2017-05-17 16:01:54)

jasonwryan · 2017-05-17 16:19:13

Not a Pacman issue, moving to NC...

pgoetz · 2017-05-17 18:04:04

ayekat wrote:

So have you tried installing the openssl-1.0 package to see if it makes cyrus-imapd work again? If that works, you could notify the maintainer to add it as a dependency.

Of course I didn't think to check if openssl-1.0 had been packaged up to help out with old shared library dependencies.

You just saved me several hours of work today. I installed openssl-1.0, remade the cyrus-imapd AUR package on another server where openssl hasn't been upgraded yet, and now everything is working again until such time as I have time to build a package of cyrus 3.0.1.

The cyrus-imapd package maintainer has been incommunicado for at least 3 months, so I'm guessing the package has been abandoned. I was ready to take it over a year and half ago when the last maintainer quit (cyrus is of critical importance to me), so now will go through the steps of orphaning and picking up the package.

Thanks to everyone for the many helpful comments posted here and I can't believe I got relegated to NC; how embarrassing.

Alad · 2017-05-17 19:24:20

Thanks to everyone for the many helpful comments posted here and I can't believe I got relegated to NC; how embarrassing.

Not sure what's so bad about NC, I post there all the time... Dustbin is a different matter.

Please mark your post as [solved] by editing the title in the first post.

ayekat · 2017-05-17 19:26:31

For building packages against OpenSSL 1.0 (even on a system that has OpenSSL 1.1 installed), you can tell the compiler (and the linker?) to add /usr/include/openssl-1.0 to the list of includepaths, although I'm not 100% sure how you could do that with cyrus-imapd's configure script (probably something like CFLAGS=-I/usr/include/openssl-1.0 configure ...).

Anyway, glad to know it worked! ~~Please don't forget to mark your thread as solved~~

Last edited by ayekat (2017-05-17 19:27:17)

Arch Linux

#1 2017-05-17 15:24:07

[SOLVED] I just broke my system by downgrading openssl -- how to fix?

#2 2017-05-17 15:28:42

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#3 2017-05-17 15:56:20

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#4 2017-05-17 15:57:09

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#5 2017-05-17 16:00:33

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#6 2017-05-17 16:19:13

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#7 2017-05-17 18:04:04

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#8 2017-05-17 19:24:20

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

#9 2017-05-17 19:26:31

Re: [SOLVED] I just broke my system by downgrading openssl -- how to fix?

Board footer