[SMS]

[Lars]

Due to some issues with ddclient 3.8.2 I wanted to build ddclient 3.8.3 using Slackbuilds
https://slackbuilds.org/repository/14.2/network/ddclient/
using ddclient-3.8.3.tar.bz2 from the Slackbuild site

When running the Slackbuild-script i immediately halted on

[gerasimos_h]

A "tar xvf" is enough, tar will recognize compression and untar it even if it's xz, without the J option...

I successfully untar the ddclient-3.8.3.tar.bz2 in SMS-2.0.9 even on a slackware-11 installation with tar-1.16...

Do you have a full SMS installation?

gerasimos_h

[Lars]

Dear gerasimos_h!

Yes, I have got a full SMS-2.0.9 installation! After extracting in SuSE and recompressing in SMS-2.0.9 which worked, I decided to investigate the source-code for ddclient which I downloaded from sourceforge.net in SMS-2.0.9, and found it was corrupt. When downloading the same sourcecode from SuSE there were no problem extracting it with
$ tar xvf in SMS-2.0.9 as You pointed out!

This problem is related to an underlying problem, and I wonder if I can bring it up here, without opening a new thread? -I just mention it very short here and wait for Your reply. If You want me to open a new thread I will, and add the information I've found so far.

My upgrade of ddclient and downloading problem in SMS-2.0.9 are both related to TLS v. 1.2. I've got openssl-1.0.2j-i486-1sms installed that should have a capacity to handle TLS 1.2.
But can SMS-2.0.9, that I recall is based on Slackware 14.0, as an OS handle TLS 1.2?

Best regards
Lars

[gerasimos_h]

I use wget without any problem
wget http://downloads.sourceforge.net/ddclient/ddclient-3.8.3.tar.bz2

and on old slackware-11 I had to ignore certificate check
wget --no-check-certificate http://downloads.sourceforge.net/ddclient/ddclient-3.8.3.tar.bz2

both downloads were fine and extracted correctly...

there is an update of openssl-1.0.2n you can install it with slapt-get

[Lars]

Well, Gerasimos!

You were right, in two ways:
1. I downloaded ddclient-3.8.3.tar.bz2 from sourceforge and ddclient.tar.gz from slackbuilds with wget. Checked the ddclient-3.8.3.tar.bz2 against the version I downloaded with SuSE. There were a slight difference when comparing md5. The tar.gz was identical. -So I decided to remove my previously built package, rebuilt it with the src and script downloaded with wget, installed it.

2. It made no difference to my initial problem.

Now this SSL/TLS materia is not a materia I'm aquainted or familiar with. The little I know I've learnt during the last two weeks trying to solve my ddclient issue. You may therefore excuse my amateurism when trying to describe my problem
I hope You also can stand my novel-like length of the problem decription!

Since last spring I haven't started up my SMS-2.0.9 server till now in february.
I rent a domain and DNS-service for my SMS-2.0.9 server from a swedish webhotel since 2013. (2017 I also rent UNIX-space for the most of my site. I didn't want to leave my home server on when I leave for vacation.) -Last spring 2018 the webhotel upgraded their servers to TLS1_2 strict, that is with no tolerance for TLS1_1. As a concequence I could no longer administer my rented hotel space from OS X 10.7. Found a way to deal with that without upgrading my OS X (I had too many expensive applications installed that I should loose after upgrading.)

When starting up SMS now in february I noticed 2 things, I had to upgrade tor, and that ddclient didn't manage to update my IP.
/tmp/ddclient.cache contained no IP
When examining /var/log/messages I found ddclient could not connect to my webhotels dns-server.
Apr 4 10:36:30 fserver ddclient[1471]: WARNING: cannot send to dyndns.loopia.se:443 (Bad file descriptor).
Apr 4 10:36:30 fserver ddclient[1471]: FAILED: updating lee-mactux.org,www.lee-mactux.org: Could not connect to dyndns.loopia.se.
This is after upgrading ddclient to 3.8.3 and having changed dns.server description i ddclient.conf to dyndns.loopia.se.
The logs looked the same in febrary when I had ddclient-3.8.2 installed and the server name was dns.loopia.se.

I've been in contact with Loopias 2nd line support since 1½ week, they've suggested different configurations, but none of them worked. The've so far failed to find an explanation to the log lines. File descriptor is correct, have added full path to the *.php file where ddclient should write, but fails. They have managed to follow my different trials in their logs.
Up to april last year Ive never had any problems with ddclient updating my IP through ssl (ssl=yes).

By this time I had come to wonder about their server upgrade to TLS1_2. Could it be so that my ddclient for some reason couldn't manage TLS1_2? Therefore the upgrade to 3.8.3. Without any success. I thought about my OpenSSL version:
I've got openssl-1.0.2j-i486-1sms in SMS-2.0.9.
As far as I can read it should be able to handle TLS1_2
https://stackoverflow.com/questions/27430158/list-supported-ssl-tls-versions-for-a-specific-openssl-build
I also studied https://www.openssl.org/news/changelog.html and found that the link above had written correctly
"Openssl versions till 1.0.0h supports SSLv2, SSLv3 and TLSv1.0. From Openssl 1.0.1 onward support for TLSv1.1 and TLSv1.2 is added."

From my experiences with the TLS problems in OS X, I had come to wonder if it perhaps could be so that upgrading the SSL/TLS-software (in SLackware OpenSSL) is not enough? That there are certain features in the Operation system that also is required when it comes to handle TLS1_2 connections?

And here comes my amateurish way of formulating the question:
Could it be so that -if I take the openssl version you suggested openssl-1.0.2n- that a Slackware-14.2 system with openssl-1.0.2n manages TLS1_2, but a
Slackware-14.0 system with openssl-1.0.2n doesn't?

-I hesitate upgrading openssl. I thankfully remember when You 2014 helped me to simulate an openssl upgrade in a virtual SMS-1.6.0! It worked, but it was not unproblematical. Besides my openssl-1.0.2j-i486-1sms should be capable of handling TLS1_2.

Best regards
Lars

PS. I've found a solution for ddclient, but not one I like. I can let it connect to my dns-server through port 80 (ssl=no). DS.

[Lars]

Some additional information,

Together with a Slackware friend I went through my installed packages in SMS-2.0.9 and compared the versions with Slackware 14.0 and his full Slackware 14.2:

Here is what we found
SMS/ 14.0/ 14.2
ddclient-3.8.3-noarch-1_SBo/ old, but the latest/
perl-io-socket-ssl-1.74-noarch-1sms/ - / 2.066 ! SBo
perl-net-libidn-0.12-i486-1sms/ -/ 0.12 SBo
perl-net-ssleay-1.48-i486-1sms/ n/a/ 1.81 ! - but
Net-SSLeay/ -/ 1.81 SBo is it equal?

gnutls-3.0.23-i486-1sms/ 3.3.26/ 3.6.7 !
openssl-1.0.2j-i486-1sms/ 1.0.1c/ 1.0.2h

I did at first not realize that gnutls was involved in SSL/TLS handling, but when I read gnutls.org it certainly seems so
Could it be an idea to upgrade gnutls? The difference in version number really sticks out.
Could it lead to problems with other packages in SMS? openssl, httpd, tor, et c?
That I have to rebuild ddclient I understand. If I upgrade gnutls, what version should I use? 3.3.26 is a patch for the version I've got. 3.6.7 is a similar patch for 14.2 version 3.4.13.

The other version differences that stick out are
perl-io-socket-ssl and perl-net-ssleay. The later perl-net-ssleay I could't find i Slackbuilds? Only Net-SSLeay; 1.55 for Slackware 14.0, 1.81 for Slackware 14.2.

This was just an idea from my side. Could my old per-io-socket-ssl, perl-net-ssleay and gnutls be an explanation to my TLS 1.2-problems? -Do You think the upgrades would affect many other functions in my SMS? I mostly use httpd, vsftpd, tor and ddclient.

Best regards
Lars

[gerasimos_h]

Sorry for the late reply, been busy with many stuff and forgot it..
GnuTLS should be no problem, as it supports tls-1.2 from version 2.x.

Since ddclient is a perl script you should try to upgrade perl modules that are affected e.g. with

[Lars]

Dear gerasimos_h!

Excuse me for returning to this thread after so long time!
My only reason is that I have had no time upgrading ddclient and dependencies before late october. With age I seem to have less time over than I had when still working .

I'll try to be as short as I can. My question is really concerning an eventual building error?
A short recall: After my DNS-service upgraded their server to TLS-1.2 this spring my ddclient (then 3.8.2) could not longer connect to their servers, get my current IP or update DNS when mismatching.
In my last post I listed the version of ddclient and its dependencies I'have got installed, and which versions of them I could build from SBo. Mostly versions for Slackware 14.2.

I didn't dare using Your suggested mcpan, because I'm not familiar with the perl world. I did the upgrading using Slackbuilds, that I had invented this spring. First checked if newer versions were available today but no. -So I rebuilt and "upgraded"/installed ddclient from the bottom dependencies and upwards.

Just to find that ddclient could still not connect to my DNS-service's servers using "ssl=yes"?

What I didn't notice when I rebuilt ddclient (in reversed dependency order) was that the previous dependecy versions were still installed in the system parallell to the newer dependencies, because the new ones had other names (that is Net-SSLeay instead of perl-net-ssleay and perl-IO-Socket-SSL instead of perl-io-socket-ssl). Could this have disturbed the Slackbuilds so it used the previous dependecy versions instead of the new built?

I attach a text-file, "upgrading_ddclient.txt", with a detailed description of how I made the upgrades -including this text- to avoid taking upp so much space here.

Best regards

Lars

PS. When searching the internet I find quite a lot of people reporting problems with ddclient and TLS-1.2 since 2018 and on. On different Linux and OS X (UNIX) systems. Problems that seem hard to solve. DS.

[Lars]

Dear gerasimos_h!

Well, I followed my assumptions, removed ddclient and it's previous dependencies, and rebuilt ddclient and it's dependencies from "bottom and up" with no improvement. ddclient still cannot connect to my DNS-server using ssl/tls-1.2.

Best regards
Lars