ClamTk

Whitelist entries are ignored & are scanned anyway

Asked by J-jim

Upgraded recently from ClamTk 4.38 to ClamTk 5.19 (for legacy systems) as I'm running Ubuntu 12.04 LTS. The new version correctly found the whitelist directories that I had previously set up under 4.38, but when I recursively scan the /home directory the whitelisted directories get scanned also. So, I manually deleted the entries in the whitelist box and re-added them with the +add button, but the directories still get scanned. Here's an example of one of the entries in the whitelist box:

/home/jmg/csi March 2011

Any suggestions to how avoid scanning the whitelisted directories?

Question information

Language:
English Edit question
Status:
Expired
For:
ClamTk Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Dave M (dave-nerd) said : 		#1

Hi,

Does this still happen with 5.20?

I'll investigate a little more and see if I can spot an error.

respectfully
Dave M

Revision history for this message
J-jim (j-jim) said : 		#2

I installed 5.19 because it was indicated that I use the "clamtk_5.19-1.legacy_all.deb" for my Ubuntu 12.04LTS system.

When I attempted to install "clamtk_5.20-1_all.deb" I get the following error:

Dependency is not satisfiable:libgtk2-perl (>=2:1.241)

So, I'm unable to test whether the problem still occurs with 5.20 at this point.

Jim G

Revision history for this message
Dave M (dave-nerd) said : 		#3

Hi Jim,

If you're running 12.04, you need to install the "legacy" version. The one you tried to install is for newer Ubuntus.

Give me a little time to work with the whitelist issue - hopefully I can duplicate the issue.

respectfully
Dave M

Revision history for this message
Dave M (dave-nerd) said : 		#4

Hi Jim,

I cannot duplicate this yet. Do the directories have any special characters, spaces, anything at all that makes them stand out?

Also, can you run ClamTk from the command line? Let's see if there are any error messages that show up.
Open a terminal window and type "clamtk", and then run a scan which should include whitelisted directories. Post back with any text that pops up there - if any.

respectfully
Dave M

Revision history for this message
J-jim (j-jim) said : 		#5

Hello Dave,

Sorry to say, no luck yet with the whitelist entries. I actually changed the sub-directory names to something very simple, i.e., abc, def, ghi and ran the scan - the whitelisted directories were still scanned. Also tried running from the command line - no difference and no error messages.

Jim G

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.