How to set up a nod32 update server on linux with minimal tools?

Question

linux

Hello, now I use eset update server for windows on the local network. Clients download updates from a public directory on the local network. The update server, like clients, downloads updates to this public directory via http, while being authenticated on the upstream server. I want the same for linux. In a search engine, I found several options for linux with my own apache + php, some long scripts:
https://www.google.ru/?gfe_rd=cr&ei=mBlxVYqBMKKe4g...
But I don’t understand why I need my own web server? I just need to download the files via http and put them in a public directory. I think it's somewhere 2 lines on the shell + crowns.

cd /opt/eset_upd/
wget --user=user --password=password http://update

But wget doesn't download updates:

Connecting to update:80... connection established.
HTTP request sent. Waiting for response... 401 Unauthorized
Reusing connection with update:80.
HTTP request sent. Waiting for response... 403 Forbidden
2015-06-05 10:06:42 ERROR 403: Forbidden.

What is the command to download updates from the upstream server?

Answer 1

Weird people. The documentation for nod32 has a description of how to install and configure the update server on both Windows and Linux. I had it in Ubuntu. And no http (apache) server is needed, nod distributes itself.

Answer 2

NOD32 exposes its web server on port 2221 (it's off by default and this feature isn't even available in settings). First you need to activate it by changing the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info\
PackageFeatures
Its value is different for different versions of ESET (see here https://ftpn.ru/nod32-change-update-server/ )
After activating this option in the settings, it becomes possible to create an update mirror and in the same place - an HTTP server.
https://help.eset.com/era/53/ru-RU/ra_mirror_enabl...
However, according to the ESET documentation, no one bothers you to publish updates from the mirror on any other web server, such as IIS.
If you already distribute updates to Windows clients in this way, then Linux clients can receive updates in the same way from the same web server. You just need to set up authorization on it correctly.
NTLM is no longer suitable for Linux clients, you need to enable Basic authentication.
Your log shows that you have problems with authentication - the user is denied connection:
403 Forbidden