LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Can't update openssh on new Slackware 14.1 install with Slackpkg (http://www.linuxquestions.org/questions/slackware-14/cant-update-openssh-on-new-slackware-14-1-install-with-slackpkg-4175502741/)

enine 04-23-2014 03:18 PM

Can't update openssh on new Slackware 14.1 install with Slackpkg
 
I just did a new Slackware 14.1 install and am unable to update openssh, isn't this the fix for heartbleed?

Code:

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:                     

openssh-6.6p1-i486-2_slack14.1.txz:    md5sum
openssh-6.6p1-i486-2_slack14.1.txz:    md5sum
openssh-6.6p1-i486-2_slack14.1.txz:    md5sum


ruario 04-23-2014 03:42 PM

The md5sum issue is probably due to a partial download. Re-download again, or don't because openssl is affected heartbleed, while openssh is not.

JohnB316 04-23-2014 04:08 PM

Quote:

Originally Posted by enine (Post 5157961)
I just did a new Slackware 14.1 install and am unable to update openssh, isn't this the fix for heartbleed?

Code:

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:                     

openssh-6.6p1-i486-2_slack14.1.txz:    md5sum
openssh-6.6p1-i486-2_slack14.1.txz:    md5sum
openssh-6.6p1-i486-2_slack14.1.txz:    md5sum


No. Per the Slack-current ChangeLog.txt, here is the reason for the update to openssh:

Code:

n/openssh-6.6p1-x86_64-2.txz:  Rebuilt.
  Fixed a bug with curve25519-sha256 that caused a key exchange failure in
  about 1 in 512 connection attempts.

Though I quoted from the Slackware64-current ChangeLog, the same reason applies to 32-bit Slackware. With that said, chances are very good that the openssh package was updated on your box. All you need to do to verify this is to type the following in a terminal window:

Code:

$ ls /var/log/packages/openssh*
If you see that the version on your box is 6.6p1, then you should be in good shape, the slackpkg error notwithstanding.

Hope this helps.

Smokey_justme 04-23-2014 04:43 PM

Quote:

Originally Posted by enine (Post 5157961)
I just did a new Slackware 14.1 install and am unable to update openssh, isn't this the fix for heartbleed?

The fix for heartbleed is openssl (not openssh), but it's good that you're updating openssh anyway..

enine 04-23-2014 08:45 PM

I was updating all except samba (OwnCloud client breaks if I update Samba) since its a new build.
I keep trying to update and it keeps failing so I don't think its a partial download.

linuxtinker 04-24-2014 12:12 AM

did you try updating your gpg keys ?


ex: slackpkg update gpg

lems 04-24-2014 12:21 AM

Quote:

Originally Posted by enine (Post 5157961)
Code:

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:                     

openssh-6.6p1-i486-2_slack14.1.txz:    md5sum
openssh-6.6p1-i486-2_slack14.1.txz:    md5sum
openssh-6.6p1-i486-2_slack14.1.txz:    md5sum


But isn't the new version in 14.1 openssh-6.6p1-i486-3_slack14.1.txz (3, not 2)? Did you update your package cache/lists? It looks like it's trying to download an old package that isn't there anymore, at least on my mirror. I would try to run slackpkg update, and then try again.

edit: I just checked: I have openssh-6.6p1-i486-3_slack14.1 installed, not -2. And the 14.1 ChangeLog mentions this package as well. In -current it seems to be -2. I think this is because there was a problem with the rc script on 14.1. I hope I'm not missing something, otherwise please ignore this post.

Smokey_justme 04-24-2014 04:00 AM

Hmm, actually, lems might have a point.. Could you try changing your mirror?

enine 04-24-2014 06:03 AM

hmm, I wonder if its replication between the mirrors. I'm using the top one on the list where it says it will choose a mirror.. And yes I did slackpkg update first then slackpkg upgrade-all

arsivci0 04-26-2014 12:23 PM

There really is something wrong with this (openssh-6.6p1-i486-3_slack14.1.txz), probably misnamed by Pat. I can't download this from packages.slackware.com (404, not found), either.

Didier Spaier 04-26-2014 02:06 PM

Hmm, there could be a problem with the package browser, or at least a discrepancy between it and Mirror Brain: searching in it for openssh for Slackware 14.1 including the patches set leads to the package openssh-6.6p1-i486-3_slack14.1.txz in /patches that is not found, but going directly to the right place in the Slackware File Tree leads to openssh-6.6p1-i486-2_slack14.1.txz that is found.

I will inform Robby Workman as I believe that he is in charge of maintaining http://packages.slackware.com/

rworkman 04-26-2014 10:53 PM

The problem should be fixed now - it was a problem on mirrors.slackware.com (which is what packages.slackware.com uses). Sometimes my rsync cron jobs hang (no idea why), which leaves a stale lock file, so subsequent rsyncs exit due to the already-existing lock file.

Didier Spaier 04-27-2014 04:18 AM

Yes it is fixed, thanks Robby.

openssh-6.6p1-i486-3_slack14.1.txz is available through both channels at time of writing.

enine 04-27-2014 09:40 AM

Yep, working fine now. Thanks Robby.


All times are GMT -5. The time now is 05:44 AM.