Domo

Great, thanks. One small note, tho. The file path in txt files should be pointed to current directory. Ie file=/download/win/v5/eea_nt32_enu.nup should be file=eea_nt32_enu.nup etc.

Thanks, Peter. While you at it, here's another related problem:

Hi. Does anyone know when 5.0.2271 PCUs gonna be available? The ones listed at hxxp://support.eset.com/kb3308/ are still for 5.0.2265... Thanks.

Here's a list generated with v5 mirror (hxxp://update.eset.com/eset_upd/v5/) by ESET Server security for Linux/BSD/Solaris 4.5.3 : https://drive.google.com/open?id=0B7C2H94GCV43M3lGekw2LXlkVnM Update options screen: hxxp://i.imgur.com/bkRocEF.png Still no PROTOSCAN module update listed. Client shows 1140 (20140806) and ofc ssl problem remains... *EDIT* Also, why v5 mirror provides 8.0.312.0 client PCUs instead of 5.0.95.0 in my update.ver list, is it normal? *Edit* 2016-04-04. After some weekend testing I can safely confirm that the whole SSL error is indeed due to outdated Protoscan module on client's side and since no one at eset cares to fix modules file list for their server solutions, here's another quick and dirty workaround for those who don't want to force update their whole zoo to latest 5.0.2260.1. 1. Download Protoscan module bits manually (I'm on FreeBSD so gonna use console commands as examples): cd /your/mirror/dir/ fetch hxxp://eset_username:eset_password@update.eset.com/v5-rel-sta/mod_019_protoscan_1309/em019_32_l0.nup fetch hxxp://eset_username:eset_password@update.eset.com/v5-rel-sta/mod_019_protoscan_1309/em019_32_l1.nup Open up your mirror's update.ver file with your fav text editor and insert the following text: [PROTOSCAN0] platform=x86 versionid=1226 type=protoscan version=1226 (20151005) group=protoscan date=05.10.2015 file=em019_32_l0.nup buildregname=ProtoscanBuild build=1267 level=0 base=268435456 size=278075 category=engine [PROTOSCAN1] platform=x86 versionid=1173 type=protoscan version=1173.15 (20160125) group=protoscan date=25.01.2016 file=em019_32_l1.nup buildregname=ProtoscanBuild build=1309 level=1 base=1267 size=63419 category=engine Save && close && update clients. Done.

Same problem Endpoint 5.0.2237.1. I think that the problem with outdated PROTOSCAN 1140 (20140806) module, unfortunately our mirror that is based on ESET Server security for Linux/BSD/Solaris 4.5.3 doesn't provide required module update and half of others new modules for some unknown reasons. Even with "Mirror PCU" option enabled. AFAIK the problem doesn't exist with PROTOSCAN 1173.15 (20160125). Local ESET tech support failed to help. Updating all machines to latest 5.0.2260.1 is not an option for me, so I'm waiting for an actual fix. ESET Log Collector logs: https://drive.google.com/open?id=0B7C2H94GCV43R0xFRDYzc0liY00