Readme for clamtk

This README was last checked or updated on 20240116.

Table of contents:

  1. About
  2. Contributing
  3. Installation
  4. Usage
  5. Plugins
  6. Troubleshooting
  7. Other
  8. Thank you
  9. Contact

About

clamtk is a frontend for ClamAV (Clam Antivirus). It is intended to be an easy to use, light-weight, on-demand scanner for Linux systems.

Although its earliest incarnations date to 2003, clamtk was first uploaded for distribution in 2004 to a rootshell.be account and finally to Sourceforge.net in 2005. At the end of 2013, it was moved to a Google Code page, then to Github, Gitlab, and Bitbucket. It is now 2024 and for some reason development is still going. In fact, February 2024 marks 20 years of activity (of being publicly available, that is).

Contributing

  1. Report bugs or suggestions at the following:

    https://github.com/dave-theunsub/clamtk/issues
    https://gitlab.com/dave_m/clamtk/issues
    https://launchpad.net/clamtk

  2. Do you speak more than one language? See the Launchpad page.

  3. If you feel like it, "star" clamtk or its related projects at one or both of the following:

    https://github.com/dave-theunsub/clamtk/
    https://gitlab.com/dave_m/clamtk/

https://github.com/dave-theunsub/clamtk/
https://gitlab.com/dave_m/clamtk/wikis/home
https://gitlab.com/dave_m/clamtk/
https://launchpad.net/clamtk

ClamAV
Gtk2-Perl
Gtk3
Virustotal

Installation

RPMs

The easiest way to install clamtk is to use the rpms. The commands dnf and yum will pull in requirements.

First, start with the official repositories.

sudo yum install clamtk or sudo dnf install clamtk.

If this does not work, download the file from the official site. You should be able to just double click the file for installation or upgrade.

For these examples, we will use version 6.17. The name of the file may differ based on your distribution.

To install using a terminal window:

sudo yum install clamtk-6.17-1.el9.noarch.rpm or sudo dnf install clamtk-6.17-1.fc39.noarch.rpm

To remove clamtk:

sudo yum erase clamtk or sudo dnf erase clamtk.

Source

Warning: Don't do this. It's much easier to just double click a .deb or .rpm. Really, put down the source.

The tarball contains all the sources. One way to do this, as tested on Fedora, is to run the following commands:

tar xzf clamtk-6.17.tar.xz sudo mkdir -p /usr/share/perl5/vendor_perl/ClamTk sudo cp lib/*.pm /usr/share/perl5/vendor_perl/ClamTk sudo chmod +x clamtk sudo cp clamtk /usr/local/bin (or /usr/bin)

Examples:

perl clamtk

or

chmod +x /path/to/clamtk /path/to/clamtk

DEBs

You should be able to just double click the .deb file to install it. Your package manager should retrieve any necessary dependencies.

From the commandline, you can do this:

sudo apt install clamtk

If you downloaded the file, then use this:

sudo apt install clamtk_6.17-1_all.deb

To remove clamtk:

sudo dpkg --purge clamtk

Note that the Debian/Ubuntu builds are no longer gpg-signed.

Integrity

It is recommended you install clamtk from official repositories. Check your distribution first, and always install from trusted sources.

While the Debian/Ubuntu .debs used to be digitally signed, they are not anymore; the way I used to do that no longer works. The rpms are digitally signed. Here's how you can verify the rpms:

  1. Get and import the key in one step:
    rpm --import https://davem.fedorapeople.org/RPM-GPG-KEY-DaveM-20230506
  2. Verify the list of gpg keys installed in RPM DB:
    rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n'
  3. Check the signature of the rpm. For this example, we'll use version 6.17:
    rpm --checksig clamtk-6.17-1.fc39.noarch.rpm
  4. You should see something like this:
    /home/you/clamtk-6.17-1.fc39.noarch.rpm: rsa sha1 (md5) pgp md5 OK

You can also verify the tarball. Using 6.17 as the example version, ensure you have downloaded the tarball, its detached signature (.asc), and the key in step 1 above.

  1. Get the key (skip this step if you already have it):
    wget https://davem.fedorapeople.org/RPM-GPG-KEY-DaveM-20230506
  2. Import it (skip this step if you have done it already):
    gpg --import RPM-GPG-KEY-DaveM-20230506
  3. Verify like so:
    gpg2 --verify clamtk-6.17.tar.xz.asc clamtk-6.17.tar.gz or
    gpg --verify clamtk-6.17.tar.xz.asc clamtk-6.17.tar.xz
  4. You should see something like this:
    gpg: Signature made Sun 11 Sep 2016 06:29:41 AM CDT using RSA key ID (snipped for brevity).

You can now use minisign, too!
Minisign

First, you will need my public minisign key:
Public minisign key

Then you will need the minisig file for the program you are verifying.

A link to it will be with the rest of the downloads.

For this example:
https://github.com/dave-theunsub/clamtk/releases/download/v6.17/clamtk-6.17.tar.xz.minisig

Next, verify like so:

minisign -V -x clamtk-6.17.tar.xz.minisig -p davemminisign.pub -m clamtk-6.17.tar.xz

Usage

Running clamtk

Commandline

clamtk can run from the commandline, too:

clamtk file_to_be_scanned

or

clamtk directory_to_be_scanned

The main reason for the commandline option (however basic) is to allow for right-click scanning within your file manager (e.g., Files, Caja, or Dolphin). If you require more extensive commandline options, it is recommended that you use the clamscan executable itself. (Type man clamscan at the commandline.)

Afterwards

You can view and delete scan logs by selecting the "History" option.

You also have a few options with the files displayed. Click on the file scanned to select it, then right-click: you should have four options there.

Quarantine/Maintenance

If you've quarantined files for later examination, you have the option to restore them to their previous location (if known), or delete them.

Plugins

To add a right-click, context menu ability to send files and directories to the scanner, install the appropriate plugin. Links to the latest versions are available here:

https://github.com/dave-theunsub/clamtk/
https://gitlab.com/dave_m/clamtk/wikis/Downloads

Here are the specific pages. Note that these are mirrored on Github as well.

Gnome (Files file manager):
https://github.com/dave-theunsub/clamtk-gnome
https://gitlab.com/dave_m/clamtk-gnome

KDE (Dolphin file manager):
https://github.com/dave-theunsub/clamtk-kde
https://gitlab.com/dave_m/clamtk-kde

XFCE (Thunar file manager):
https://github.com/dave-theunsub/thunar-sendto-clamtk
https://gitlab.com/dave_m/thunar-sendto-clamtk

Mate (Nemo file manager):
https://github.com/dave-theunsub/nemo-sendto-clamtk
https://gitlab.com/dave_m/nemo-sendto-clamtk

Troubleshooting

Limitations/Bugs

Probably a lot. Let me know, please. Ranting on some bulletin board somewhere on one of dozens of Linux sites will not fix bugs or improve the program. See the section below for contact info.

Other

As of version 3.10, clamtk will not scan standard mail directories, such as .evolution, .mozilla or .thunderbird. This is due to parsing problems. If a smart way of doing that comes up, it will be added.

Also, please note that version numbers mean absolutely nothing. There is no rhyme or reason to odd or even numbers (i.e., an odd number does not mean "unstable"). A new version means it goes up 1 (or, rather, .01).

GUI

clamtk started out using the Tk libraries (thus its name). In 2005, this was changed to perl-Gtk2 (or Gtk2-perl, whatever). The Tk version is still available on sourceforge.net but has not been updated for some time now and should not be used.

The plan for the 5.xx series was to use Gtk3. Unfortunately, Debian and Ubuntu did not have a recent version of libgtk3-perl, and CentOS did not have perl-Gtk3. So, at the last second, the 5.00 version was rewritten to use Gtk2. Again.

Version 6.xx has been written to use Gtk3, as Gtk2 is deprecated. There's no new design this time, as this was an effort to ensure the Gtk3 version could be included in upcoming distribution releases (such as with Debian).

Version 7.xx will likely have a new design, and may be written in a different language as well.

And there's also a Gtk4 in the works.

Thank you

Many people have contributed their time, energy, opinions, recommendations, and expertise to this software. I cannot thank them enough. Their names are listed in the credits file.

Also a big thank you to:

Contact