Questions of Threatfire

Thank you raven

 

Well, so far so good or as good as can be expected so far with testing the latest THREATFIRE Beta. It must been painstaking for PCTools to finally get the right S.M.A.R.T patterns integrated into the GUI to at least finally offer us an authentic "kill switch" LOL

I'm still experiencing some technical difficulties with some of the CUSTOM RULES as i'm not sure whether or not TF accepts *Wildcards in the rules or what they are exactly if they do in this Beta for this particular Behavioral Blocking Program, but i've discovered a marked improvement from before. Of that theres little doubt, although it's a matter of tweaking things for them now but who knows what the timetable will be for those.

 

any idea wen the beta will be over? if i remember correctly it was supposed to be like mid september...

 

The beta is over. ThreatFire 4.6.0.19 has been released.

 

o really? didnt see a post in here and didnt check their site, well im gunna give it another try then, thx.

for some reason im unable to connect to the threatfire page on the PCTools site... it just says server error, runtime error?

 

Give it a go now: http://www.threatfire.com/download/

 

same error.

 

Only when you are a forum member of PC tools you have access to betas

 

well im finally able to access the download page, no error anymore, guess some sort of site issue. gunna test it out today and hopefully all those beta bugs are gone.

 

Thanks guys for alerting to the latest release for us. I had no idea it was already there.

I'll install later today and watch for the improvements put into it.

EASTER

 

wow this is great, the release version is working flawlessly, love it, ALMOST as light as mamutu but a tiny bit heavier, but overall system still feels fast, great so far

FIRST working version of TF for me EVER. awesome

 

Is the problem with FireFox fixed in this new release?

 

for me it sure is.

 

I seem to be seeing something disturbing which better suited to post at PC Tools ThreatFire forums maybe, but with the latest ThreatFire release, my Process Guard 3.5 is blocking TF "trying to modify winlogon.exe, explorer.exe, and all other system and running processes in an endless loop that Process Guard refuses to allow.

Now why on earth would TF need to modify these critical system files in order to conduct it's so-called SMART Behavioral Blocking?

Mamutu doesn't.

 

ThreatFire injects an dll into each running program and some windows API hooks to monitor behaviour.

 

Thanks for that.

On a lighter note, on some systems i have the TF (Beta) installed and running to perfection with Custom Rules working as expected.

I'll have to try again with the last release and see if what i suspected was just some glitch, oversight, or actual problem or not.