WSS Block executables into zip file

I need a solution

Hello everyone

I need you help, in my portal of WSS I do a rule to block all executable files *.exe, according this KB

https://support.symantec.com/en_US/article.TECH245091.html

The rule work fine, but if the file *.exe is compress in file *.zip don´t work

Any idea of ​​why it does not work like that?

regards

Andres Garcia

0

Related:

  • No Related Posts

7021278: EXTRA! Developer Tools: API Code Samples and Manuals

This technical note is organized into the following sections:

API Reference Manuals

The following documentation is available for EXTRA! APIs.

API
Reference Information
OLE Automation (COM)
See the EXTRA! Macro Editor component help (EPC_OLE.HLP installed with product), or http://docs.attachmate.com/extra/x-treme/apis/com/
WinHLLAPI
WinHLLAPI Language Reference

http://docs.attachmate.com/extra/x-treme/apis/whllapi.pdf
EHLLAPI
EHLLAPI Language Reference

http://docs.attachmate.com/extra/x-treme/apis/ehllapi.pdf
Attachmate HLLAPI
HLLAPI Language Reference

http://docs.attachmate.com/extra/x-treme/apis/hllapi.pdf
EAL
Enterprise Access Library Language Reference

http://docs.attachmate.com/extra/x-treme/apis/eal.pdf
PCSHLL
PCSHLL Language Reference (IBM PCOMM 4.01 EHLLAPI)

http://docs.attachmate.com/extra/x-treme/apis/pcshll.pdf
WD_API
Wall Data (RUMBA) WD_API Language Reference

http://docs.attachmate.com/extra/x-treme/apis/wd_api.pdf

EXTRA! Basic Code Samples

A collection of over 20 EXTRA! Basic macros is available for download. These educational samples demonstrate:

– displaying Windows dialogs,

– checking the host 3270 OIA status line,

– transferring a file at a regular interval,

– calling Win32 API functions (e.g., modify Windows registry),

– copying host screen text to a Microsoft Excel spreadsheet,

– and more.

Download eb-samples.zip and see the enclosed _ReadMe.txt file for more information.

Test Tool Code Samples

The following additional test tool code samples are available for older APIs and IDEs.


VB 5.0 / 6.0
VC++ 5.0 / 6.0
WinHLLAPI
hllvb32w.exe
hlltes32.exe
EHLLAPI
hllvb32e.exe
hlltes32.exe
HLLAPI

hlldem32.exe
EAL
atmapi32.exe
ealtutor.exe
PCSHLL

pcshll32.exe

By default, EXTRA! X-treme is configured to use 32-bit Enhanced Transport for HLLAPI. You can confirm the HLLAPI Transport Type selection by clicking Options > Global Preferences > Advanced.

For information on tracing API calls for debugging purposes, see Technical Note 2249.

Related:

  • No Related Posts

inject64.exe constantly crashing

I need a solution

Hi,

i have an issue with Blue Coat ProxyClient 3.4.4.6.

Application event log shows that inject64.exe is crashing every 5 seconds and writing dmp files in the Windows Crash folder.

The event is:

<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event>
<System>
  <Provider Name=”Application Error />
  <EventID Qualifiers=”0>1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime=”2018-02-16T07:12:08.560971800Z />
  <EventRecordID>439522</EventRecordID>
  <Channel>Application</Channel>
  <Computer>LAPTOP-S65370G7</Computer>
  <Security />
  </System>
<EventData>
  <Data>inject64.exe</Data>
  <Data>3.4.4.6</Data>
  <Data>51d31f94</Data>
  <Data>inject64.exe</Data>
  <Data>3.4.4.6</Data>
  <Data>51d31f94</Data>
  <Data>c0000005</Data>
  <Data>0000000000005cb4</Data>
  <Data>21dc</Data>
  <Data>01d3a6f57479ccc2</Data>
  <Data>C:Program Files (x86)Blue CoatProxyClientinject64.exe</Data>
  <Data>C:Program Files (x86)Blue CoatProxyClientinject64.exe</Data>
  <Data>02aadb51-1dd4-4e99-be8b-0a9c7aad0b6f</Data>
  <Data />
  <Data />
  </EventData>
  </Event>
 
Any idea how what is causing this and how it can be fixed ?
 
thx&rgds, Enrico
0

Related:

  • No Related Posts

Trying to deploy Windows Update 1607 or 1703

I need a solution

This is the first i’ve tried to deploy these massive updates via Patch Management and hopefully someone can point me in the right direction. Deploying generates an ugly set of errors referencing files that don’t exist.  See full script text below attempting to execute the file manually to find out what is going on.

The server name has been replaced to protect the innocent.  🙂

Any help would be greatly appreciated!

c:>\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}Windows10x64Enterprise1607.bat
'\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}'
CMD does not support UNC paths as current directories.
'swuenv.bat' is not recognized as an internal or external command,
operable program or batch file.
Installation tools are located in '' directory
dagentmsi.log
The file cannot be copied onto itself.
0 file(s) copied.
Could Not Find c:deploy-status.txt
Starting patch installation
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}CL5.exe"' is not recognized as an internal or external command,
operable program or batch file.
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}CL5.exe"' is not recognized as an internal or external command,
operable program or batch file.
A subdirectory or file C:STscriptDeployment already exists.
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}cl5.exe"' is not recognized as an internal or external command,
operable program or batch file.
Mount-Diskimage : The system cannot find the file specified.
At line:1 char:1
+ Mount-Diskimage '\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5z ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (MSFT_DiskImage:ROOT/Microsoft/.../MSFT_DiskImage) [Mount-DiskImage], Ci
mException
+ FullyQualifiedErrorId : HRESULT 0x80070002,Mount-DiskImage

'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}cl5.exe"' is not recognized as an internal or external command,
operable program or batch file.
Dismount-Diskimage : The system cannot find the file specified.
At line:1 char:1
+ Dismount-Diskimage -Imagepath '\XXX-SMP-XXX.campbell.comNSSWD_pkggrou ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (MSFT_DiskImage:ROOT/Microsoft/.../MSFT_DiskImage) [Dismount-DiskImage],
CimException
+ FullyQualifiedErrorId : HRESULT 0x80070002,Dismount-DiskImage

'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}cl5.exe"' is not recognized as an internal or external command,
operable program or batch file.
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}cl5.exe"' is not recognized as an internal or external command,
operable program or batch file.
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}CL5.exe"' is not recognized as an internal or external command,
operable program or batch file.
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}CL5.exe"' is not recognized as an internal or external command,
operable program or batch file.
Patch processed, last exit code 9009
'"\XXX-SMP-XXX.campbell.comNSSWD_pkggroup_w5e7yjp5ns5znr43k7hm4daihu3hlrih$SBSP-Windows10_1607{db9299c4-04a4-45e4-92d6-9f7738f42151}CL5.exe"' is not recognized as an internal or external command,
operable program or batch file.
0

Related:

Case sensitivity and flags in RegEx content filtering rules

I do not need a solution (just sharing information)

I upgraded Mail Security to 7.5.5 a few months ago and migrated my File Name Rule (which has a habit of erroneously identifying pdf files as containing javascript) to a content filtering rule set to scan container files using the same match list that I used for the File Name Rule. Everything works great, with one exception. When using the File Name Rule, the wildcards in a match list had to match the entire file name. When using the wildcard match list in a Attachment Name content filtering rule, it doesn’t (even when you specify “Whole Term” in the matching options). Since “*.com” is in that match list, any attachment that contains the name of a website from the .com tld (such as google.com) gets caught and quarantined, along with a couple of other miscelaneous files.

So, as an example, whenever I request a quote from one of our venders the quote file they send me contains their website and gets quarantined even though it’s not actually a .com file, it just happens to contain the website in it’s filename. So, I figured I would convert the wildcard match list over to a RegEx match, since it actually contains appropriate characters for specifying that a file name should end with .com. The issue that I’ve ran into with this is case sensitivity. There’s no way to disable case sensitivity in regular expressions, at least when filtering by attachment name. This means going through to each of my regular expressions and manually making them case insensitive. So… I have to convert “.*.COM$” into “.*.[cC][oO][mM]$”. That should work, however it’s clunky and there should be other ways to make something this simple function.

Ideally, we should have a way to specify flags for regular expressions. Baring that, the ability to make attachment name content filtering rules case insensitive when filtering with regular expressions would suffice.

Any other ideas for a workaround?

0

Related:

VNX2: Slot 2 has panicked – post panic logging complete: *** Invalid Opcode exception. Virt ADDRESS: 0x037c05e1ce *** (Dell EMC Correctable)

VNX Operating Environment

VNX OE for File

VNX OE for File 8.1.9.155

VNX/VNXe Family

VNX2 Series

Slot has panicked – post panic logging complete: *** Invalid Opcode exception. Virt ADDRESS: 0x037c05e1ce ***

DART panic/fault message:

*** Invalid Opcode exception. Virt ADDRESS: 0x037c05e1ce ***

Panicking Processor: 5

DART stack trace:

ef60: 0x115b930 _ZN7DskDump9checkdumpEPKc+0x7a

efa0: 0x115bb3e dump_return+0x4

efb0: 0x14597a _Z10systemDumpPKc+0xa6

efd0: 0x145ff7 fault_dump+0x89

eff0: 0x13dd4d handle_fault+0x1d

Other panic header seen:

*** Page Fault Interrupt. Virt ADDRESS: 0x00012b0c45 Err code: 0 Target addr: 0x02322cb54e **

*** GP exception. Virt ADDRESS: 0x011c30c007. Err code: 0 ***

Workaround:

The workaround for this issue is to set the following param in /nas/server/slot_x/param and reboot the DM (this returns the setting back to the default in 8.1.8 and earlier).

param cifs smb2.largeReadWriteSize=1048576.

For a detailed resolution please refer to DELL EMC Support Solution 493849https://support.emc.com/kb/493849

YOU MAY ALSO BE INTERESTED IN THE FOLLOWING CONTENTS FOR VNX:



Top Services Topics

Video Playlistp

Related:

Program filenames must end with .EXE.

Details
Product: Windows Operating System
Event ID: 3718
Source: System
Version: 5.0
Symbolic Name: APE_OnlyNetRunExes
Message: Program filenames must end with .EXE.
   
Explanation

This message should occur only on a workstation. Any action to correct the problem should be performed on that computer. The Netrun service runs only programs with the file name extension .EXE.

   
User Action

To use a program with a .COM extension, an administrator must rename it to an .EXE file.

Related:

An error occurred when attempting to run the service program.

Details
Product: Windows Operating System
Event ID: 3061
Source: System
Version: 5.0
Symbolic Name: SERVICE_UIC_EXEC
Message: An error occurred when attempting to run the service program.
   
Explanation

The service you specified could not start.

   
User Action

In the services section of your configuration file, find the name of the program file for this service. Be sure this file exists and is an executable file with a file name extension of .EXE or .COM. If the program file exists, it might be damaged. If possible, restore the file from a backup version. Otherwise, contact technical support.

Related: