Tranquil IT Forum

Hmm, I've already done that... I've even done it several times, but I'm sticking with the previous version for the agent and the Wapt upgrade as well...

Hello,

same here: upgrading from 1.5.13 to 1.5.15, I ran the py script at the end and generated a new agent, but the result is still 1.5.13 for both Waptagent and the console.
Whereas for the previous upgrade (1.5.10 to 1.5.13, if I remember correctly), everything was fine.

Matthieu

Hello Matthiman and guigeek,

did you install the tis-waptsetup-xxxx.deb package along with the tis-waptserver-xxxx.deb package?

If you run `dpkg -l | grep wapt`, what version do you get?

Denis

then the command returns to me:
ii tis-waptrepo 1.5.1.15-tisdeb9-4514-329043f0 all WAPT Packages repository server based on nginx and additional scan packages / sign packages tools.
ii tis-waptserver 1.5.1.15-tisdeb9-4514-329043f0 amd64 WAPT Server for Windows machines software management.
ii tis-waptsetup 1.5.1.15-tisdeb9-4514-329043f0 all WAPT setup executable for Windows

And on my WAPT server interface:
WAPT Server Version: 1.5.1.15
WAPT Agent Version: 1.5.1.13
WAPT Setup Version: 1.5.1.13
WAPT Deploy Version: 1.5.1.14
Database Status: OK (1.5.1.15)

I think I see where the problem is. For now, you can run the following commands:

`rm -f /var/www/wapt/waptsetup-tis.exe`
and `apt-get install --reinstall tis-waptsetup`.

I'll fix it tomorrow. I thought this bug had already been fixed... sorry.

Denis

Reporting an issue with WAPT 1.5 installed on Debian 9.2:

During the installation of the administration console (and the WAPT client), our Trend Micro antivirus classifies the executable "waptconsole.exe" as Mal_Mlwr-13 (I hope this is a false positive...). Do you have a solution other than excluding the c:\wapt folder on the Trend server?

Does this executable contain code that would be considered harmful to workstations?

dcardon wrote: ↑Jan 16, 2018 - 6:32 PM I think I see where the problem is. For now, you can run the following commands:

`rm -f /var/www/wapt/
waptsetup-tis.exe` `apt-get install --reinstall tis-waptsetup`

I'll fix it tomorrow. I thought this bug was already fixed... sorry.

Denis

Okay, I'll test that on Thursday (I'm out of the office tomorrow)
No other commands to run? The py script or something else?

Good evening Joris,

joris.remandet wrote: ↑January 16, 2018 - 6:33 PM Reporting an issue with WAPT 1.5 installed on Debian 9.2:

During the installation of the administration console (and the WAPT client), our Trend Micro antivirus classifies the executable "waptconsole.exe" as Mal_Mlwr-13 (I hope this is a false positive...). Do you have a solution other than adding the c:\wapt folder to the exclusions list on the Trend server?

Does this executable contain code that would be considered harmful to workstations?

Antivirus programs aren't very intelligent to begin with... If the executable you have is properly signed by Tranquil IT Systems (right-click on the file, then go to the "Digital Signature" tab), it means it comes from our buildbot and there's no problem.
On VirusTotal, only Trend Micro, a Chinese antivirus without an English version (Rising), and another that doesn't even have a false positive reporting page (Cylance) flag the executable as malware...
As a side note, a few years ago the wapt-get.exe was flagged as a virus because the icon was the default one for the Lazarus development environment (the icon was a small cat paw, as if a cute kitten could be dangerous...).

We'll see about doing a false positive report to Trend and Rising.

Otherwise, I'm currently cleaning up the compilation page for the various WAPT components. You can recompile it yourself if needed [1].

Denis

[1] https://www.wapt.fr/fr/doc-1.5/Contribu ... _wapt.html

No worries there, it's definitely signed by Tranquil IT.

Our antivirus is truly awful (it even blocks our KoXo software on our servers that manage Active Directory...).

In Burgundy high schools, we use WAPT, and I find version 1.5 much more stable than the others (probably due to the replacement of Apache and MongoDB, which must have been cumbersome to manage, I imagine).

Hi,
Indeed, the commands are working, the Wapt setup has been updated to the correct version... I'm going to rebuild the agent!
THANKS !

dcardon wrote: ↑Jan 16, 2018 - 6:32 PM I think I see where the problem is. For now, you can run the following commands:

`rm -f /var/www/wapt/
waptsetup-tis.exe` `apt-get install --reinstall tis-waptsetup`

I'll fix it tomorrow. I thought this bug was already fixed... sorry.

Denis