[pacman-dev] [PATCH 2/3] Use OpenSSL MD5 crypto functions if available

Thomas Bächler thomas at archlinux.org
Mon Sep 6 11:03:11 EDT 2010

Am 06.09.2010 16:42, schrieb Dan McGee:
> The only thing that should break here is "everything else" on your
> system. E.g. if you are prompted to upgrade pacman first because it is
> in SyncFirst, and it pulls in an so-bump OpenSSL, then anything else
> on your system that links that library won't work until you complete a
> full -Syu. However, as I pointed out above, this was already happening
> as far as I can see before.

Not exactly: Last time, pacman upgraded itself without upgrading
libarchive and libfetch, and the next update pulled the openssl upgrade
with the rest of the libraries.

And we still had lots of problems with users who broke their system. I
am thinking we might consider using dlopen() on libssl with a fallback
to the builtin code.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20100906/82502cca/attachment-0001.bin>

More information about the pacman-dev mailing list