SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hah. That's the problem of openssl and its solibs. You have too new openssl package but too old openssh package.
Download manually (without swaret) openssh, openssl, openssl-solibs from slackware-current, remove the old packages and install these new packages. There is installpkg command for installing packages.
Last edited by Alien_Hominid; 04-07-2006 at 10:07 AM.
I've encountered the same problem. On some mirrors there was not properly updated wrong build of openssh package. Change mirror, download the package again (it has a bit newer timestamp) and reinstall.
Coincidentally I also upgraded my whole system using swaret... And yes, I also stumbled upon the mismatch of ssh and ssl.
What I did was remove the latest packages and installed the ones that came on cd. It didnt nag about mismatches. But my connection to the internet is now gone. Has that to do with the older packages or hasnt it got anything to do with ssl/ssh packages??
When I run netconfig it complains about my system not having tcp/ip installed, though i could internet before the upgrade.
So my question is: Is compiling and installing the source for both ssh and ssl enough to resurrect my internet connection or are there are other problems?
I am asking this in advance before trying it out. I spent all day fixing problems and booting between Linux and windows...
Also worth mentioning if you download the upgrades from slackware for ssh you get 2 versions of sshd_config in /etc, one called sshd_config.new. The same for ssh_config. So I suppose you have to alter the .new files to your liking and then rename them without the .new extension. Don't know if this is relevant or not.
Well the renaming did the trick indeed. Thanks for the help. Swaret is an okey tool, though this afternoon I found 'Swear it' a more apropiate name for it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.