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)

Configuring the WAPT console¶

We will now properly configure the WAPT console.

Go to console configuration settings: Tools ‣ Preferences.

WAPT console preferences¶

Here we will set the prefix.

Attention

It is not trivial to change the prefix later as it would require re-signing all packages in all repositories, so choose your prefix well the first time!

The path to the private key has been automatically entered when we generated the private key in the previous step.

If you already have a key (ex: from a previous installation), you’ll have to fill your old key here.

If you want to learn more on setting up the WAPT console, you may visit the documentation on configuring the WAPT console.

You may now go on to create the WAPT agent!!