mrspooky wrote:Strange enough I am still allowed to update the so-called "definitions",
Because the underlying software/backend (ClamAV) is
freeware and (I think) always will be - it's licensed under the GNU GPL. And most of the definitions files are just the ClamAV definitions (although there are some ClamXav own definitions.. I actually don't have any idea if those continued to update after ClamXav went commercial).
ClamXav is just a GUI and a "Sentry", it comes with a custom Mac OS X build of ClamAV but IIRC it is theoretically possible to run it with *any* build of ClamAV (though I've never done that). So if your installed ClamXav works fine for you, then (if you don't want to buy the commercial version) I suggest, keep that as-is and if you want upgrade, get a newer ClamAV and point ClamXav to that instead of its own ClamAV.
mrspooky wrote:BTW, do you know if I can check for "sha256" in my already-installed clamxav?
You can check sha256 of a file with openssl, like so:
open Terminal.app, enter
where <file> is the actual file (you can drag it into Terminal.app to paste its full path).
The checksum I gave is only for the .dmg, so no it does not apply to your installed ClamXav, sorry.
(I don't know how to get checksum of an entire installation! Note that a .app is actually an entire folder, not a single file; and that the ClamAV is installed in the system as a package - which in this context basically means scattered about

.)