"Important Topics" section, and then some of the postings in the main body of the forum. You'll find some relevant stuff in there.
From a quick scan of the info, it looks like some changes were made in the recent update to version 5 of CIS. Which perhaps haven't worked out too well.
thank you for that, while i didnt find any answers there it did lead me to an apparant work around. and while not ideal it appears to be working.
1. open comodo.
2. click defense+.
3. click trusted files.
4. click "file path" at the top to sort by file path, it makes this next part easier.
5. check the box on the left of every instance of boinc and click "remove" on the right.
6. click close.
7. click Computer Security Policy.
8. click the "Defense+ Rules" if it is not already selected.
9. click add.
10. click "select" if boinc is running search by process, if it is not browse for it. your after the "boincmgr.exe" file.
11. after selecting "boincmgr.exe" select "use a predefined policy"
12. select "installer or updater" from the drop down.
13. click apply.
14. close out comodo and reboot.
NOTE: this allows boincmgr.exe to run ANY file it desires and comdo will allow it. this is why i say this is not exactly "ideal" but it appears to be working.
NOTE 2: you apparently have to remove each instance from the "trusted files" list for this to work. because if i understand what ive read on the comodo forums correctly when a file is on the trusted files list any policy for the file is "ignored".
ive opted to do it this way because when einstein does an update the file name does not stay the same, thus one would have to define a new policy for each einstein app.
i may be getting client vs app mixed up, i can never keep them straight in my head for some reason lol
As long as it works for you and makes sense too you, then it is okay. The making sense too you part is so you can then edit it later on if necessary without having to re-invent the wheel!
I am glad it is working now!!!
> NOTE: this allows boincmgr.exe to run ANY file it desires and comdo will allow
> it. this is why i say this is not exactly "ideal" but it appears to be working.
This is actually opening up a security hole! Why doesn't Einstien@Home just SIGN the damn exe's and fix the problem. This is professional work, not script kiddies...
> NOTE: this allows boincmgr.exe to run ANY file it desires and comdo will allow
> it. this is why i say this is not exactly "ideal" but it appears to be working.
This is actually opening up a security hole! Why doesn't Einstien@Home just SIGN the damn exe's and fix the problem. This is professional work, not script kiddies...
DaveW.
Self signed executables are utterly meaningless from an anti-malware standpoint; and buying a signing certificate from one of the major vendors is a decent chunk of money ($430-500/year from Verisign) that can't be put to use for something productive.
RE: RE: Hi Phil, Take a
)
As long as it works for you and makes sense too you, then it is okay. The making sense too you part is so you can then edit it later on if necessary without having to re-invent the wheel!
I am glad it is working now!!!
Good news Paul. Glad I was
)
Good news Paul. Glad I was useful, even if it was only to point you in the right direction.
Mike
RE: Good news Paul. Glad I
)
i would never have thought to set a policy rule if it wasnt for you pointing me to that forum. so thank you :)
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
a small observation, this
)
a small observation, this workaround apparently does not work for windows xp. the standard "add to trusted files" procedure works for xp.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
RE: 11. after selecting
)
Use boinc.exe instead
[pre] [/pre]
> NOTE: this allows
)
> NOTE: this allows boincmgr.exe to run ANY file it desires and comdo will allow
> it. this is why i say this is not exactly "ideal" but it appears to be working.
This is actually opening up a security hole! Why doesn't Einstien@Home just SIGN the damn exe's and fix the problem. This is professional work, not script kiddies...
DaveW.
RE: > NOTE: this allows
)
Self signed executables are utterly meaningless from an anti-malware standpoint; and buying a signing certificate from one of the major vendors is a decent chunk of money ($430-500/year from Verisign) that can't be put to use for something productive.