CAVS - initial observations and comments

As before, suggestions in bold.

Uninstalled CAVS and installed today on both the work test system and the home test system.


CAVS Config : Only change to CAVS default config was to turn on HIPS dialogue for blocked apps and turn off HIPS dialogue for allowed apps. uninstalled very cleanly. - Well done, guys. on the work system was great. requires 15 “allows” for the same network-sourced executable when logging in on a Novell LAN workstation. The path for this executable shows only a single backslash at the beginning of the path, rather than a double backslash.

HIPS reacts very slowly when an executable is loaded from a mapped drive. The executable loads promptly after clicking allow, but the HIPS dialogue takes far longer than I expected to appear.

Safelist creation takes a long, long time if Novell mapped drives are mapped via the Windows context menu, as opposed to being remapped on login by a script.

Pausing the safelist creation is not particularly responsive if safelist is scanning files on a mapped drive when pause is clicked.

File submission is very, very intrusive.

File submission sometimes hangs when submitting a largish file.

File submission sometimes gets a connection reset by server error (possibly due to local lan congestion, or possibly due to overloaded server at your end.)

HIPS doesn’t remember executable loaded off a network if the path is declared in UNC format.


CAVS Config : Only change to CAVS default config was to turn on HIPS dialogue for blocked apps and turn off HIPS dialogue for allowed apps. takes a bit longer to rebuild the safelist than

File submission sometimes gets a connection reset by server error (extremely unlikely to be caused by local lan congestion)


Is it just me or does everyone else think its a bit silly that CAVS doesn’t class some of its own files as known or safe, and puts them in the submission list?

Shouldn’t CPF receive an update about the executables in CAVS so it automatically knows about them? This would prevent a compromised download being installed, as the cryptographic signature would be different.

Is it possible for the file submission process to use resumable uploads? This would allow the process to be interrupted by the user and resumed where it left off, rather than having to start a submission again.

Is it possible for the submission process to be tied to a certain level of system inactivity? This could reduce the operational lag. One idea wouldbe to tie it to the screensaver process, like SETI.

Remember the things I tell it to. UNC file paths are not remembered.

The Mozilla Thunderbird email app shows in the submission list as “thunde~1.exe” and the path name similarly shows truncated LFN path.

The file "thunde~1.exe has been submitted four times from the same system so far.It never drops off the list, even after watching the upload occure, via the CPF ACTIVITY - CONNECTIONS screen.

“Select All” behaviour in the submission window is erratic.

Other than that, Mrs.Lincoln, how was the play? LOL

None of these are showstoppers, and the system had run very smoothly (other than LAN induced delays), with no discernible lag since installing

Looking good!

Ewen :slight_smile:


On a third system, I still have CAVS running and just noticed that in the files submission window, it has a progress bar!!?!

Why doesn’t the submission window in CAVS 2 have the progress bar?

ewen :slight_smile:


Command line scanner is very effective and very quick. Easily setup on removable media.

Give me DOS or give me death!!!

ewen :slight_smile:

Didn’t I feel like a goose when I found that ALL submission windows have the progress bar!

Then again, since the two most important action events in the window are “What is being sent?” and “Has it been sent yet?”, how come we have to scroll to see the progress meter?

As a suggestion, why not relocate the progress meter to be the left most column. It also doesn’t have to be an actual progress bar. It could be as compact as the percentage. This would place the most pertinent info in front of the client and give them an idea of what is happening and when.

Just a thought.

Ewen :slight_smile:

Goodday Panic,

I have taken the bugs reported by you for fixing. You can see the fixes in next release.
Your suggestion have been considered. You will see its implementation in upcomoing releases…
The CAV file detection bug is fixed and will come in next release.


Excellent!! Please pass on our collective thanks to the dev team for their work on this.

Ewen :slight_smile: