Attention : support for WAPT 1.8.2 ended on June the 30th 2022.

There are known vulnerabilities in WAPT dependencies in WAPT 1.8.2 branch. Please upgrade to the latest supported version. CVE listing (non exhaustive) :
  • * python engine : python 2.7 (CVE-2020-10735, CVE-2015-20107, CVE-2022-0391, CVE-2021-23336, CVE-2021-3177, CVE-2020-27619, CVE-2020-26116, CVE-2019-20907, CVE-2020-8492, etc.)
  • * cryptography : openssl : CVE-2022-2068, CVE-2022-1292, CVE-2022-0778, CVE-2021-4160, CVE-2021-3712, CVE-2021-23841, CVE-2021-23840, CVE-2021-23839, CVE-2020-1971, CVE-2020-1968, CVE-2019-1551
  • * python dependencies : cryptography (CVE-2020-36242, CVE-2020-25659), eventlet (CVE-2021-21419), jinja2 (CVE-2020-28493), psutil (CVE-2019-18874), waitress (CVE-2022-31015), lxml (CVE-2021-4381, CVE-2021-28957, CVE-2020-27783, CVE-2018-19787), ujson (CVE-2022-31117, CVE-2022-31116, CVE-2021-45958), python-ldap (CVE-2021-46823)

Upgrading WAPT from 1.3 to 1.6 on Windows

Attention

WAPT Server no longer installs on x86 versions of Windows.

Note

At the end of the post-configuration step, waptserver will detect that you are upgrading from WAPT 1.3.13 and will ask you to launch the migration of the database from MongoDB to PostgreSQL.

  • click on Yes;

  • launch the WAPT console

Note

If you come from a WAPT 1.3.13 version running with IIS, the WAPT listening ports must be changed. In that case, follow the documentation for changing the listening port.

You may now go to the next step to generate the necessary keys!!

Migrating WAPT 1.3 from a Windows OS to a Linux OS

The simplest method is to move over to a Linux based version of waptserver.

Note

A dump folder should have been created in the same directory as the mongodump.exe file.

  • backup the entire directory C:\wapt of the WAPT Server;

  • backup the folder C:\private;

  • install a fresh version 1.3.13 of WAPT on Linux (debian 8 x64) or CentOS7/ RedHat7 (x64);

Hint

To install a new Linux Debian 10 (Buster) on a physical or virtual machine without a graphical user interface, please visit the official documentation for Debian9.

  • if the WAPT agents point to an IP address, then the new Debian based WAPT Server must have the same IP address as the old Windows based WAPT Server.

  • if the WAPT agents point to a DNS CNAME, then you may point the DNS field srvwapt to the IP address of the new Linux server.

  • update the download sources;

apt update && apt upgrade -y

  • install the WAPT Server;

Note

The utilities tis-waptserver, tis-waptsetup et tis-waptrepo are signed; it is therefore necessary to recover the GPG key below to avoid warning messages when installing them.

apt install apt-transport-https lsb-release systemd-sysv systemd
wget -O - https://wapt.tranquil.it/debian/tiswapt-pub.gpg  | apt-key add -
echo  "deb  https://wapt.tranquil.it/debian/wapt-1.3/ $(lsb_release -c -s) main"  > /etc/apt/sources.list.d/wapt.list
apt update
apt install tis-waptserver tis-waptrepo tis-waptsetup

  • launch the configuration script;

/opt/wapt/waptserver/scripts/postconf.sh

Note

The password requested in step 4 is used to access the WAPT console.

  • configure the WAPT Server;

  • start the WAPT Server;

systemctl start waptserver

  • restore the WAPT packages on the Linux server;

    • upload the content of C:\waptwaptserver\repository\wapt in /var/www/wapt/;

    • upload the content of C:\waptwaptserver\repository\wapt-host in /var/www/wapt-host/;

    Hint

    You may upload the files on the Linux Server using the WinSCP utility.

    • then change the owner of the files to wapt:

      chown wapt:www-data /var/www/wapt*

  • restore the MongoDB database on the Linux server:

    • using WinSCP, upload the MongoDB dump folder in /root/;

    • restore the MongoDB dump on your Linux hosted MongoDB instance:

      mongorestore /root/dump

Your WAPT Server now works in 1.3.13 on Linux.

You may now install your waptagent on your Administrator management PC and restore the C:\private folder on your workstation.

Attention

You must not regenerate a private key, you must only point to your private key in the console. You must also refill the package prefix.

You may now follow the classic procedure to upgrade from 1.3.13 to 1.6!!