Discussion in 'other firewalls' started by glentrino2duo, Aug 1, 2006.
Jetico v2.0 BETA is released!
check this out: http://www.jetico.com/
Yes Stem and me are tesing it right know. It's a real Beta
how is it on resources? still light?
is it easier for newbies?
From what I read, they have made some big changes. Mind posting some screenshots?
Looks interesting, will have to check it out when it becomes "stable". Speaking of stability, how is it doing so far?
Its running o.k. on this system, well up to now.
By the way, i does seam that Jetico 2 won't be freeware anymore. During the setup process you will be asked for a external registration or you can install the one which comes with the installer. The internal one works till October i think. After that changes won't be saved anymore.
I tried Jetico v2.0 BETA on a quite clean Win 2K SP 4 and it didn't work. The service (jpfsrv.exe) was started but no tray icon, and at startup I got a message that said "MainDoc, CoCreateInstance hr = 0x80070005" and that firewall server couldn't be contacted (by jpf.exe). Application log stated something like that while firewall service was started, there were either some registry stuff or DLL message files missing and thus the local machine was unable to show messages sent by a remote machine. Uninstallation failed with "Error read log file, err code 0" and I decided to undo changes.
Same here, aslo on a clean WinXP SP2 System
bluedevil / Tommy,
You should e-mail Jetico about this problem. I Installed earlier, and not seeing such problems, only problem I have up to now is that the jump_to_rules doesnt seem to work correctly.
This version will also have a free edition...
That's good news! I wish the free edition would include application control...
BTW, I know that this 2.0 BETA was first posted in another thread. I just taught that a new separate thread would draw more attention to the new release, so more people will know about it.
If not, i am going to buy a licenz for this amazing FW.
Regarding to your and my Jetico Server/Service and uninstall problem i just got an answer from Jetico suport
Can you please send me your registry heave. I send it with my hive back to Jetico suport.
Please check your Hotmail, Tommy.
Installed v2 on a fairly clean XP SP2 in a VMWare. Installation was no problem, firewall is running fine.
Slightly more ressources needed: Jpffsvr.exe 7,3 MB and jpf.exe 14,4 MB working set size in sysinternals process explorer. For comparison v1 nedds 10 MB on my productive laptop.
The new rules seem only to accept XML files is there any way to import the old .bcf configuration? On the other hand, the rules seem to have changed a bit so I am not sure if it would be any help .
At the early stages of JPF2 project we created bcf->xml converter. Now it became a bit outdated. In addition, bcf is not identical to current xml: I mean hash handling and multiple root tables.
Currently it seems impossible to save or open configurations. Since the different configurations are currently held in one XML file would new configurations have to be saved in the same file, too? In this case I do not really understand the functionality of open since the XML file has to be specified in General/options However, is there a more conveniant way to backup configurations while testing, other than stopping the firewall and copying the xml file?
Please send it to my spam account: email@example.com.
Not at this stage.
It would be nice to see the ability to import/export rulesets, which will, at this stage, even once file->save works, mean exporting all policies (full xml file) for one ruleset.
I agree, this would be a very helpfull feature. Also for the people who had Jetico 1 with a large set of rule in order to import these in Jetico 2.
This would need a conversion program, as all rules are now within the xml file.(it was just the safe/block zone in the xml V1 file).
I did try out placing a large blocklist within JPF2, worked o.k. (just the memory use for jpfsrv.exe went up past 50mb )
Hm, lets see what i can do regarding that.
Separate names with a comma.