POPULOUS The Third Coming The Unofficial FAQ v0.1a (16th July 1997 ::
[2.1.13] PLAGUES Your enemy's got far too many people in his towns for your liking. Infect a brave volunteer from your village with all manner of poxes and
http://www.gamesover.com/walkthroughs/populou3.txtHOME |
...the longer I use Outpost Pro 2.1 the more I tend to believe that it's better to uninstall it and buy a less buggy personal firewall. I'm absolutely fed up with all the errors/problems in V2.1.
(See posting http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=9565)
The product
- doesn't work correctly if you frequently lock your workstation (like most business users do; home users usually don't lock their system, I'd guess): message boxes just disappear => this can block your whole internet connection
- doesn't work correctly if you are logged in under a restricted account (it seems to have problems accessing the log files; I don't know... I didn't spend much time checking that)
- blocking rules are applied that don't exist (anymore)
- ads are still blocked although the plugin was stopped or certain websites were excluded from blocking (no, it's not a "JavaScript-disabled-problem")
&Fate of the Universe - Patch vom 11.12.2007 - Tabula Rasa - Artikel::
Today’s maintenance sees the implementation of V 1.3 onto the live servers with many bug fixes, festive items, new consumables and a brand new operation!
http://www.fateoftheuniverse.de/modules/news/article.php?storyid=31&com_id=31&com_rootid=30HOME |
wow 2.1 patch notes - Fires of Heaven Guild Message Board::
Fixed a bug where the Silence effect on Garrote was getting resisted too often. - Gouge: This ability will no longer trigger poisons (and thus break
http://www.fohguild.org/forums/mmorpg-general-discussion/28778-wow-2-1-patch-notes.htmlHOME |
- if you "allow/block always" certain actions in the "Active Content Filtering" (VBScript for example), there is no way to see/change what was always allowed/blocked
- for some applications Outpost infinitely displays "Defining the rule..." in the "allow/block reason" column -- what's that?
- IP ranges cannot be defined (only the network IP and mask, but by this you cannot define a range like 192.168.0.13 to 192.168.0.26 or so)
- even unter Windows 2000 Server Outpost sometimes reports that "Fast User Switching is enabled"... but this is only available in XP (no, I don't use Terminal Services and no, I never switch between user accounts)
- sometimes the log window cannot be closed (only by Alt-F4)... this is really pathetic
- and the list goes on, and on, and on...
I anticipacte that some may say now: "Hey, that's a problem of your system/drivers/installations..." But this is not true. I tested Outpost 2.1 on three different systems...
I'm very disappointed. Outpost 1.0 (free) worked fine for quite a while. I don't have the time to be an unpaid beta tester for Agnitum. That's not what I have paid for.
Just my 2 cents.
:mad:
Regards
Uwe
Actually I prefer it this way as it gives the user a lot more flexibility in their configuration of Outpost. Some users only use the firewall and no plug-ins, or in my case I use the firewall and only the plug-ins that suit my needs.
hi,
...and another one:
even when op is disabled, it blocks certain sites :(
http://members.lycos.co.uk/darkwavesforum/pics/op21.gif
DW
@MegaHertz
thx, good to know this ;) a bit irritating, isn´t it? i thought, the build-in plugins would stop working, too.
...a bit like using the brakes of your car without loosing speed ;)
dw
Okey dokey, let's take these one at a time...
- doesn't work correctly if you frequently lock your workstation (like most business users do; home users usually don't lock their system, I'd guess): message boxes just disappear => this can block your whole internet connectionRules Wizard/Component Control popups appear on the Logon screen so when you login, you need to Ctrl-Alt-Del back to the Logon to answer the prompts. This has been raised as a bug but can be worked around for most people (use Block Most mode and disable Component Control if you need to lock the workstation).- doesn't work correctly if you are logged in under a restricted account (it seems to have problems accessing the log files; I don't know... I didn't spend much time checking that)Uh, which versions of Windows did this happen with and which restricted user? Guest? User? Power User? Was Outpost running in Service Mode or not? More info is needed for this to be fixed.- blocking rules are applied that don't exist (anymore)Exactly which rules? Did you delete them or apply a new configuration without them? Did you configure 2.1 from scratch (always a safer option) or import a 1.0 configuration?- ads are still blocked although the plugin was stopped or certain websites were excluded from blocking (no, it's not a "JavaScript-disabled-problem")The "Trusted" sites list of the Ad-filter does not work - this has been raised as a bug. If ads are still appearing to be filtered when the plugin is disabled then this suggests that your browser is using cached data - did you try clearing the cache or forcing a page reload?- if you "allow/block always" certain actions in the "Active Content Filtering" (VBScript for example), there is no way to see/change what was always allowed/blockedDo you not get a specific entry for the URL in question in the Active Content Exclusions list?- for some applications Outpost infinitely displays "Defining the rule..." in the "allow/block reason" column -- what's that?Which applications? What rules did you have for them? The only time I have seen "Defining the rule..." is when Outpost is started on a PC with no network connections.- IP ranges cannot be defined (only the network IP and mask, but by this you cannot define a range like 192.168.0.13 to 192.168.0.26 or so)This has been a long-standing bug since Outpost 1.0 - yes, it should be fixed but people affected need to raise the issue with Agnitum directly. Posting here will do little to raise a bug's priority. David and I have already raised this several times with Agnitum (and I have mentioned it in the FAQ too).- even unter Windows 2000 Server Outpost sometimes reports that "Fast User Switching is enabled"... but this is only available in XP (no, I don't use Terminal Services and no, I never switch between user accounts)I encountered the opposite, this happened with Outpost 2.0 on Windows 2000 Pro and 2.1 fixed this for me. I suggest you report this.- sometimes the log window cannot be closed (only by Alt-F4)... this is really patheticNever seen or heard of this - does the viewer hang in Task Manager? Have you tried updating your MDAC drivers as suggested here (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=9600)?- and the list goes on, and on, and on...
#197040 - encryption not "illegal" in Iraq (sig) - Debian Bug ::
There are too many real bug reports on openssh to worry about keeping up to .. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=197040HOME |
I anticipacte that some may say now: "Hey, that's a problem of your system/drivers/installations..." But this is not true. I tested Outpost 2.1 on three different systems...That doesn't quite rule out software conflicts - if you are running the same program/driver X on all 3 which tries to tango with Outpost on a low-level then you can expect similar problems. You reported in your previous thread that you were unable to install 2.0 which further suggests a software issue (maybe you are running anti-virus software that prevents Outpost from installing properly - which could explain a few of your problems above). Are you running any low-level networking software/drivers on all three machines? (e.g. packet sniffers, port monitors, network diagnostic tools, VPN software).I'm very disappointed. Outpost 1.0 (free) worked fine for quite a while. I don't have the time to be an unpaid beta tester for Agnitum. That's not what I have paid for.That's a bit of a shame - if people don't take the time to report problems, then Agnitum can hardly be faulted for not fixing them! Also this forum would not exist without the volunteer, unpaid efforts of regular posters, beta testers and moderators/admins. I would certainly say that you should report bugs to Agnitum (www.agnitum.com/support/supportform.html) directly (with a little more info in some cases). Even when a bug has already been reported, multiple reports are still used to gauge the priority for the fix.
Having 3 setups on hand does mean that you can give Outpost a more thorough workout than most others - and as you have stated a business user will use their PC in different ways from a home user. I would suggest that you again consider applying for a beta-tester position since you can then check the status of bugs you raise and gain access to beta builds. On the other hand, if you simply want to use software with no known problems, you may wish to start on Windows itself...
Darkwave,
Running Outpost in Disabled mode does not stop the plugins from working. They operate independently of each other.
Originally posted by Dark Wave
@MegaHertz
thx, good to know this ;) a bit irritating, USN´t it? i thought, the build-in plugins would stop working, too.
...a bit like using the brakes of your car without loosing speed ;)
D
No, it's like hitting the brakes and expecting the windows to close. Plugins are built into the firewall but are separate components.
Just a note:
The IP range bug has already been reported and is in the 'To do' list.
Hi Paranoid2000,
Rules Wizard/Component Control popups appear on the Logon screen so when you login, you need to Ctrl-Alt-Del back to the Logon to answer the prompts. This has been raised as a bug but can be worked around for most people (use Block Most mode and disable Component Control if you need to lock the workstation).This is not correct. Sometimes the popups appear on the logon desktop, but not always. Most of the time they are simply gone after stopping the screensaver (blank screen standard windows screensaver) and logging in.Uh, which versions of Windows did this happen with and which restricted user? Guest? User? Power User? Was Outpost running in Service Mode or not? More info is needed for this to be fixedThis appears under Windows XP Professional using the "User" account. The dialog box (opened by Aupdrun.exe) is named (translated) "Product Update" and says "Cannot open protocol file". Yes, Outpost runs in server mode, standard installation.Exactly which rules? Did you delete them or apply a new configuration without them? Did you configure 2.1 from scratch (always a safer option) or import a 1.0 configuration?The rule "EXPLORER Rule #1" existed, yes. I deleted it and created new rules. After deletion or even renaming I expect Outpost not to show it anymore. But it did. I sent the screenshots to Agnitum support. It shouldn't matter how the rules were created - a rule that doesn't exist (anymore) should not be applied and should not appear in the log file. Period.
anti-spyware and networking Resources | TechRepublic::
No patches, many machines missing anti-virus or had outdated copies, no group policy Outpost Network Security 2.0.73 (Windows): Outpost Network Security
http://search.techrepublic.com.com/search/anti-spyware+and+networking.htmlHOME |
The "Trusted" sites list of the Ad-filter does not work - this has been raised as a bug. If ads are still appearing to be filtered when the plugin is disabled then this suggests that your browser is using cached data - did you try clearing the cache or forcing a page reload?
Of course I forced a page reload...Do you not get a specific entry for the URL in question in the Active Content Exclusions list?No. In this case, "VBScript" was set to "Prompt". When I visited a site that used VBScript, Outpost asked if the site should always be allowed to use VBScript. My response was "yes". BUT: Only for VBScript, not for ALL Active Content... Of course Outpost should not inculde this site to the general Active Content exclusions list... Even if it should have added it -- it wasn't added.Which applications? What rules did you have for them? The only time I have seen "Defining the rule..." is when Outpost is started on a PC with no network connections.Outpost says "Defining the Rule..." for: ntfrs.exe, dns.exe, ismserv.exe, tcpsvcs.exe and lsass.exe.Never seen or heard of this - does the viewer hang in Task Manager? Have you tried updating your MDAC drivers as suggested here?No, the viewer doesn't hang, the close option is just disabled. Update MDAC to close a window? Come on... this is ridiculous. I have MDAC 2.7 SP1. Outpost shouldn't need MDAC 2.8 to close a window...TYou reported in your previous thread that you were unable to install 2.0 which further suggests a software issue (maybe you are running anti-virus software that prevents Outpost from installing properly - which could explain a few of your problems above). Are you running any low-level networking software/drivers on all three machines? (e.g. packet sniffers, port monitors, network diagnostic tools, VPN software).
I haven't installed packet sniffers, port monitors, network diagnostic tools, VPN software etc... BTW, I couldn't install 2.0 although I killed every single unneeded process and stopped every single service that isn't essential to run Windows... That's a bit of a shame - if people don't take the time to report problems, then Agnitum can hardly be faulted for not fixing themWell, well... you may rest assured that I reported all problems to Agnitum (some postings here are just copied parts of my mails sent to them). Besides the installation problem (which is solved now) I haven't yet received any response to my support requests. The only thing they said was that the information was forwarded to the developers.
Don't misunderstand me, I appreciate the amount of effort that you and many others in this forum spend to help users. I'm very thankful for the support that is offered in this forum. But this is not my point. I simply do not have the time to deal with all the bugs and shortcomings of Outpost. I paid >46 EUR and I expect a product that works reliably, particulary if it's a security product. There are bugs in every software (in my own, too ;-), but some basic things should work. The problem of the "invisible dialog boxes" (potentially blocking every internet connection!) is such an error I cannot accept.
Regards
Uwe
 Get Smart About Monitoring Virtual Machines
 Microsoft Gets Ex-Streamly Cozy with U.K.'s MediaWave
|
Too Many Bugs In Outpost 2.1