You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, some annoying antivirus software forcibly injects their dynamic link library into every process. Thankfully, MP can stop this. But at the same time, the protected applications don't work properly. I tried to sign my antivirus with a user certificate, but due to its protection mechanism, I couldn't copy any files into the directory where it was installed. In this regard, I hope that MP can implement a "special case whitelist" by adding both the file path and the file hash to the MP configuration data
The text was updated successfully, but these errors were encountered:
Oh that's an interesting edge case, will need to look into it...
I think here the most expedient implementation would be to have a user signed database of whitelisted hashes, with or without a path restriction.
Blanked whitelisting of a path without hashing would be not secure.
Also I'm looking into adding the ability to add trusted certificates such that you only would need to whitelist the antivirus software vendors certificate to allow all its files.
In the next build under C:\ProgramData\Xanasoft\MajorPrivacy
will be the folder mpsig
containing suo bolders with file names of the signed files in which will be SHA_HASH.mpsig files where the filename is the full hash of the file
So no path whitelisting but the ability to have the mpsig files collected separately from the signed exes and dlls
also the *.sig files will be renamed to *.mpsig to no longer confligt with otehr *.sig file usages
Sometimes, some annoying antivirus software forcibly injects their dynamic link library into every process. Thankfully, MP can stop this. But at the same time, the protected applications don't work properly. I tried to sign my antivirus with a user certificate, but due to its protection mechanism, I couldn't copy any files into the directory where it was installed. In this regard, I hope that MP can implement a "special case whitelist" by adding both the file path and the file hash to the MP configuration data
The text was updated successfully, but these errors were encountered: