Jump to content

How does KAV treat VST and other executable plugins?


Recommended Posts

I do some music production on my machine. In this area, everything revolves around a VST plugins. VST plugin is just a .dll, so it can, in theory, do anything. Editor application loads them during work and runs them.


So, here is a situation: a well-known, popular and trusted application with digital signatures from a respected developer regularly loads DLLs, that are untrusted, unsigned and are being downloaded from all over the Internet. Many of them use self-encryption in attempt to apply DRM to what can’t be.

  • Does KAV automatically extend the trust for the editor on the DLLs?
  • If yes, should I, maybe, explicitly set the editor itself and its modules as a low-trust applications? I tried to do it and got some functions blocked, but maybe I could investigate why if it is worth it.
  • Any other advise how to secure that system?


Link to comment
Share on other sites

  • 4 months later...


Before KAVKISKTS 2019 build, There is a function named ‘Trusted mode’ could be control dll load process. Any untrusted dll by KL could be blocked in order to avoid loading. But unfortunatly, This function has been removed.

My suggestion for system security is to download the program file from the official software website. The downloaded program needs to have a digital signature and verify it. Most software installation packages now have digital signatures, so this verification process is easy to implement. This is also the most secure software usage habit.


Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now

  • Create New...