I was running an MBAM scan when a couple popups occurred while scanning. I assumed they were OK, and I allowed. I was surprised by this, because I was sure MBAM is safe. ....
MBAM is secure, but if they dont sign their software parts then this application cant recognize them as being a part of MBAM.
Hi Tarnak, based on the screen shots, it may be caused by an untrusted file being scanned by MBAM. The file may not be created by MBAM but if we have the log, we will be able to tell which process has actually created this file. MBAM may be trying to check the property of the file and checking the property of any untrusted file will also trigger SecureAPlus' prompt. Therefore, it has nothing to do with MBAM at all. Basically, SecureAPlus just try to warn the user that there is an untrusted file, and it so happened that this untrusted file is being accessed by MBAM. Hope this helps. Cheers, sinlam
Hi Tarnak, from the screen shots, we noticed that you have installed Webroot. Did you install Webroot before or after installing SecureAPlus? Based on our testing, Webroot consumes a lot resources if it is installed before SecureAPlus. It is best to install Webroot only after SecureAPlus is installed.
I have uninstalled WSA, and reinstated normal Startup for SecureAplus. I have improved startup, somewhat. So, I can live with that.
Hi guys, We have released the latest SecureAPlus Version 2.0.22. In this release, we have fixed the service installation crash in some foreign languages other than English. Those users who are facing this problem may wish to give SecureAPlus another try. There are also other minor changes: - Obfuscate quarantined file to prevent it from being detected as virus by any antivirus. - Suppress antivirus installation warning in Windows XP. - Register as antivirus at the "Action Center" (or "Security Center" in Windows XP). You can view the latest release note on the changes at https://secureaplus.secureage.com/Main/release.php. If you have any feedback or comment, please feel free to post it here. Cheers, sinlam
I updated to v2.0.22, however I could not copy and paste the contents of the setup...apparently focus was stolen by the message to reboot the computer to complete install of updates.
Hi Tarnak, glad to hear that you have successfully updated to v.2.0.22 Is it possible to share with me why there is a need to copy and paste the setup content? This helps us to better understand some of the user's behaviour so that we can take note of it in our future UI design. Cheers, sinlam
Sinlam, I don't understand why I have no choice at installation but to trust all installed executables. Using the default settings of the whitelisting it would also be possible to build up the whitelist dynamically. I have removed certificates of the build in white list (kept only the ones which I have on my PC). I think it would be nice when a selection of the build in data base could be made (hold ctrl key) or select all, see pic. This gives (paranoid) users full control on what to whitelist (existing options: trust by OS, trust by publisher and trust by publisher and hash are sufficient) and offers you an option to push updates of build in whitelist to users on demand or by user consent. Regards Kees
My change request for V1 is still not implemented in V2 (this feature should not be restricted to power users), have added them again myself. Feature is to good to keep for insiders
This is a great suggestion Kees Having a list of default trusted publishers that can be added manually to the existing "Trusted Certificate" is a good idea. We will keep this in mind and add in as one of the future development pipeline. Cheers, sinlam
Hi Kees, thank you for your suggestion on adding more applications to the "Process Protector". Actually Process Protector will be more powerful if it is paired with our another solution, SecureData (Application Binding). Currently, we don't put it as an obvious feature to the users in SecureAPlus. We are extremely careful in adding new applications to the Process Protector. Before adding any new application, we will always do more testing first to ensure there is no unwanted side effects. Cheers, sinlam
It already works...finally Thanks sinlam for your patience to resolve my problem. I noticed that SecureA read whole area of my local disk to find all "possible" certificates and it takes a lot of time...so is it possible to add feature to exclude some areas from scanning? I have on non-system disk one large folder with my "apps archive" where are hundrets of installation file...I know that it could be useful to add every found certificates "just in case" but sometime it can be not needed and in built WL it can make some chaos what we currently are using. I see that it's something similar in Kees's suggestions and I think it would be reasonable and convinient to do so.
Hi ichito, actually we should thank you for your patience. Despite of the crashing problem that you were facing previously, you are still willing to give SecureAPlus another try now Thank you for your feedback and suggestion. This may be a good suggestion but SecureAPlus is catered to all kinds of users, including those with or without technical background. Giving users the option to exclude certain folders for initial whitelist may be quite challenging to some layman users. They may accidentally exclude some critical folders. As a result, they may face a lot of prompting from SecureAPlus once the initial whitelisting is completed. Too many promptings may deter them from using SecureAPlus. It also made them feel that SecureAPlus is not easy to use without knowing that it is actually due to the option that they have chosen. If you think that certain folder is not necessary to be included, you can simply untrust this folder. This will also automatically remove the corresponding certificates from the "Trusted Certificate" list. Please feel free to add more comments. Cheers, sinlam
Does this play nicely with sandboxie?......I've searched through the thread and couldn't find a clear answer (unless I missed it)
Hi clubhouse1, we had fixed SecureAPlus' conflict with Sandboxie in v2.0.18. You can read about it at https://www.wilderssecurity.com/showthread.php?p=2270501&highlight=sandboxie#post2270501, post #204, #212 and #213. Please feel free to ask if you need further clarification. Cheers, sinlam
Thank you very much, I consider this an essential software, and its always nice to see a developer who has the will to talk on a 'one to one' basis with its users....If you develop this to the point that it becomes share\payware I'll gladly buy it.
Hi clubhouse1, thank you for your compliment and we are happy to know that you are willing to buy the paid version of SecureAPlus Cheers, sinlam
Hi Sinlam... I want ask you about one strange thing...why is it that SecureA behaves differently on Vista and XP? On Vista it has 4 working processes with low resources consumption but on XP we have only 3 processes that use much more resources...SecureAPlus Service.exe is not presented in process manager And second observation: after initial scanning I have removed all certificates form "trusted list"...it's connected with my questions above... feature "Observation mode" have been enabled and I expected that during reboot all needed certificates from starting processes will be added to the list...but the list was empty. I have considered that apps which are launched during boot system will be initially scanned...am I wrong?
Hi ichito, thank you for your feedback If you are running SecureAPlus with no AV, there should be four processes running, namely saappsvc.exe, sanotifier.exe, SecureAPlus.exe and SecureAPlusService. Below is a screenshot of XP SP3 on our machine. Did you install SecureAPlus on a clean Windows XP or are there some other software installed on it? Based on our past experience, we found out that other software may at times interfere the memory usage. For example, if you have installed Webroot, it will increase the memory and CPU usage significantly. To resolve this problem, you have to uninstall Webroot first. Then, install SecureAPlus. After SecureAPlus' installation is completed, you can then reinstall Webroot. Regarding your second observation, SecureAPlus will add new certificate to the trusted certificate list when you have trusted a new software. If the software hashes are still trusted in the whitelist database, it will not extract the certificate anymore. It is more efficient to do it this way because retrieving certificate is a resource consuming task. So when you trust a new file, the certificate will be automatically appended to the "Trusted Certificate". Removing the certificate from the "Trusted Certificate" list will not automatically set the file as untrusted because the hashes are still trusted. To untrust a file, you have to do a right-mouse click on the file, click on "Trust Level" and then click on "Not Trusted". By doing so, it will be automatically removed from the "Trusted Certificate" list. Hope this answers your questions. If you need further clarification, please feel free to ask Cheers, sinlam
