dpkg problem libssl post-installation

[Yu_Shu]

Hello,

I wanted to upgrade libssl and openssl on my debian server to patch for heartbleed.

This is what I got:

http://pastebin.com/TRGrXCr2



# apt-get install libssl1.0.0 openssl
...
Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u12) ...
dpkg: error processing libssl1.0.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 128


Please help me
/Yu

[slickymaster]

Moved to the Server Platforms sub-forum

[Vegan]

try using a regular update

su apt-get update
su apt-get upgrade

then see if the desired components are installing properly

[Yu_Shu]

Thanks for your answer

I get the same thing, same output

[slickymaster]

Please try, one at a time:
sudo apt-get -f install
sudo dpkg --configure -a

[Yu_Shu]

Thanks for the answer

This also just outputs the exact same thing as before

Is it something wrong with the post-installation script for libssl?


Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u12) ...
dpkg: error processing libssl1.0.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 128

All other packages fails because 'libssl is not configured yet'

[slickymaster]

Please try:
sudo apt-get install --reinstall libssl1.0.0:amd64and copy/paste all the output you get into the thread, using code tags (http://ubuntuforums.org/showthread.php?t=2171721&p=12776168&viewfull=1#post12776168) for the effect.

[ian-weisser]

Ah, version confusion.
Heartbleed and many other security patches have already been backported to previous versions of libssl1.0.0.

In other words, if you are downloading libssl from the upstream website, use 1.1.0 as they recommend.
If you are using Ubuntu, simply ensure your security updates are enabled. Even though the version says 1.0.1-4ubuntu5.17 (12.04/Precise) or 1.0.1f-1ubuntu2.5 (14.04/Trusty), the heartbleed -and many other fixes- are implemented.

You DON'T need to install a non-Ubuntu package to get security updates. If you have the ubuntu-security repositories enabled, you already are patched against heartbleed.

For more details, dig out the CVE number of the specific vulnerability you want to know about, then look up that CVE number at http://www.ubuntu.com/usn/

[Vegan]

openssl is in the standard Ubuntu program library, its a pretty standard for all distributions

[Yu_Shu]

Thanks for all the answer


@slickymaster
Thanks, here is the output


# apt-get install --reinstall libssl1.0.0:amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
26 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for libssl1.0.0:amd64

:o

@ian-weisser
I've downloaded the package from the website also, but it yield no difference from the one in the repo. Security channel is used and 1.0.0 is coming from there, I supposed that it was patched just as you said


@Vegan
I'm using the standard program library

[slickymaster]

Let's try another approach.

I'm assuming that you are on a Trusty box, if you aren't please don't run these commands:
sudo apt-get install --download-only libssl1.0.0:amd64
sudo dpkg -i /var/cache/apt/archives/libssl1.0.0_1.0.1f-1ubuntu2.5_amd64.deb
sudo apt-get update && sudo apt-get upgrade
sudo dpkg --auditAnd please copy/paste the output as done before.

[Yu_Shu]

Sorry I'm on debian.

I put a "exit 0" line in the begining of the post-installation script, to manually shedule a reboot and restart of services.

The bug may only exist on that debian-specific package.