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)

Setting up your WAPT development and test environment

Prerequisites

Attention

  • it is required to be a Local Administrator of the machine to use WAPT’s integrated environment for developing WAPT packages;

  • we advise you to create/ edit packages in a fully controlled environment that is safe and disposable;

  • the usage of a disposable virtual machine (like Virtualbox) is recommended;

Make sure that you have your private key stored on the development computer

In the WAPT console, the fields private key and prefix must be filled.

Install the tis-pyscripter WAPT package

  • import the tis-pyscripter package in your local repository and install it on your development computer;

Recommendations regarding the test environment

The recommended method to correctly test your WAPT packages is to use a representative sample of machines in your inventory. So the more heterogeneous your installed base of machines, the larger your sample must be.

This method consists of testing the installation of the package on as many platforms and configurations as possible, so to improve its reliability, before the WAPT package is transferred to production repositories.

Testing method

Operating systems and architectures

  • Windows XP;

  • Windows 7;

  • Windows 10;

  • Windows Server 2008 R2;

  • Windows Server 2012 and R2;

  • x86;

  • x64;

  • Physical and virtual machines;

  • laptops;

Hint

When possible, RC and Beta version of Operating Systems should be tested (ex: Windows 10 Creators Update).

State of Windows Updates

  • Microsoft Windows machine without any Windows update installed: the objective is to detect Windows updates that are required for the software to work properly and to adapt the WAPT package accordingly;

  • Microsoft Windows machine with all the latest Windows updates: the objective is to detect Windows updates that break the package and to adapt the WAPT package accordingly;

State of software installations

  • Machines with many installed packages: the objective is to detect a possible dependency with an existing application;

  • Machines with many installed packages: the objective is to detect a possible conflict with an existing application;

  • Install older versions of the software: it is possible that the software installer does not support uninstalling a previous version of the software, in this case, the WAPT package will have to remove older versions of the software before installing the new version;