Determining libssl-dev version

NotionCommotion · 06-28-2017, 12:30 PM

I have two Raspberry Pi's with what I thought identical configuration. Only one of them complains, however, when compiling some software, so I guess they are not identical.

Code:

/home/client/gateway.cpp: In member function ‘void Gateway::initSslContext()’:
/home/client/gateway.cpp:327:14: warning: ‘const SSL_METHOD* TLSv1_2_client_method()’ is deprecated [-Wdeprecated-declarations]
     method = TLSv1_2_client_method();
              ^~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
                 from /usr/include/openssl/ssl.h:61,
                 from /home/client/gateway.h:11,
                 from /home/client/gateway.cpp:1:
/usr/include/openssl/ssl.h:1610:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_client_method(void)) /* TLSv1.2 */
 ^
/home/client/gateway.cpp:327:36: warning: ‘const SSL_METHOD* TLSv1_2_client_method()’ is deprecated [-Wdeprecated-declarations]
     method = TLSv1_2_client_method();
                                    ^
In file included from /usr/include/openssl/ct.h:13:0,
                 from /usr/include/openssl/ssl.h:61,
                 from /home/client/gateway.h:11,
                 from /home/client/gateway.cpp:1:
/usr/include/openssl/ssl.h:1610:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_client_method(void)) /* TLSv1.2 */
 ^

This one is the problem child:

Code:

michael@pi1:~/michaelclient/build $ sshd -V
unknown option -- V
OpenSSH_6.7p1 Raspbian-5+deb8u3, OpenSSL 1.0.1t  3 May 2016
usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file]
            [-E log_file] [-f config_file] [-g login_grace_time]
            [-h host_key_file] [-k key_gen_time] [-o option] [-p port]
            [-u len]
michael@pi1:~/michaelclient/build $ ssh -V
OpenSSH_6.7p1 Raspbian-5+deb8u3, OpenSSL 1.0.1t  3 May 2016
michael@pi1:~/michaelclient/build $ sudo apt-get -y install libssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl-dev is already the newest version (1.1.0e-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
michael@pi1:~/michaelclient/build $

And this one works fine:

Code:

michael@pi2:~/michaelclient/build $ sshd -V
unknown option -- V
OpenSSH_6.7p1 Raspbian-5+deb8u3, OpenSSL 1.0.1t  3 May 2016
usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file]
            [-E log_file] [-f config_file] [-g login_grace_time]
            [-h host_key_file] [-k key_gen_time] [-o option] [-p port]
            [-u len]
michael@pi2:~/michaelclient/build $ ssh -V
OpenSSH_6.7p1 Raspbian-5+deb8u3, OpenSSL 1.0.1t  3 May 2016
michael@pi2:~/michaelclient/build $ sudo apt-get -y install libssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
michael@pi2:~/michaelclient/build $

The only difference is the first one says it is at the newest libssl-dev version (1.1.0e-2) while the second doesn't include the (1.1.0e-2).

How can I tell the version of libssl-dev on both machines, and see if I can update it on the first pi?

Thanks

rtmistler · 06-28-2017, 01:00 PM

If you have it, you can use the dkpg(1) command with the -l option and pipe that to a grep command searching for libssl-dev.

However ... Raspberry Pi's are booted from SD cards. Why not dd the image from the one you consider to be your master and put it onto the other one? And then you know for sure they are identical.

NotionCommotion · 06-28-2017, 01:19 PM

Quote:

Originally Posted by rtmistler

If you have it, you can use the dkpg(1) command with the -l option and pipe that to a grep command searching for libssl-dev.

However ... Raspberry Pi's are booted from SD cards. Why not dd the image from the one you consider to be your master and put it onto the other one? And then you know for sure they are identical.

It is difficult to gain physical access to the device.

Also, I don't have dpkg. Can aptitude be used?

Thanks

rtmistler · 06-28-2017, 01:52 PM

Quote:

Originally Posted by NotionCommotion

It is difficult to gain physical access to the device.

Also, I don't have dpkg. Can aptitude be used?

Thanks

A general web search tells me that the package manager for Raspbian is aptitude. Therefore yes. Try apt-show-versions for that package name, however you may wish to double check my memory by performing a web search on how to determine library versions on linux using aptitude.

NotionCommotion · 06-28-2017, 02:14 PM

Thanks, I had been messing around with aptitude for the first time. I will continue.

I did remove libssl-dev, and reinstall it on the problem machine, and I no longer get the warning. I don't have apt-show-versions, but found a different means, and it shows it at the same version. Funny, though, sudo apt-get -y install libssl-dev still shows slighly different results. One is a Pi2b and the other a Pi3. Maybe the issue?

Code:

michael@pi1:~ $ apt-cache policy libssl-dev
libssl-dev:
  Installed: 1.0.1t-1+deb8u6
  Candidate: 1.0.1t-1+deb8u6
  Version table:
 *** 1.0.1t-1+deb8u6 500
        500 http://mirrordirector.raspbian.org/raspbian jessie/main armhf Packages
        100 /var/lib/dpkg/status
michael@pi1:~ $ sudo apt-get -y install libssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl-dev is already the newest version (1.0.1t-1+deb8u6).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
michael@pi1:~ $

Code:

michael@pi2:~ $ apt-cache policy libssl-dev
libssl-dev:
  Installed: 1.0.1t-1+deb8u6
  Candidate: 1.0.1t-1+deb8u6
  Version table:
 *** 1.0.1t-1+deb8u6 0
        500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
        100 /var/lib/dpkg/status
michael@pi2:~ $ sudo apt-get -y install libssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
michael@pi2:~ $

How I got here is with the following. I likely on one of the machines installed libssl-dev before using stretch. Maybe the culprit?

Code:

sudo apt-get -y update
sudo apt-get -y upgrade
sudo apt-get -y install git cmake libsqlite3-dev    #libssl-dev
#sudo apt-get -y remove libssl-dev
# Don't know if the following is required?
sudo apt-get -y install software-properties-common python-software-properties build-essential
sudo apt-get -y remove gcc && sudo apt-get -y autoremove gcc
sudo vi /etc/apt/sources.list    #Replace "jessie" with "stretch"

sudo apt-get -y install gcc-6 g++-6
sudo vi /etc/apt/sources.list    #Replace "stretch" with "jessie" and exit
sudo apt-get -y update
sudo apt-get -y install libssl-dev    #After gcc is installed!