Outpost Firewall Pro 2008 & OSS Pro Released


Recommended Posts

6lin0ac.gif

Outpost Security Suite Pro 2008 (build 6.0.2279.251.0482)

6kqkpd5.gif

Outpost Firewall Pro 2008 (build 6.0.2279.251.0482)

Release date: February 26, 2008

The following improvements are introduced:

  • Compatibility with Windows Vista SP1
  • Compatibility with Windows Server 2008
  • Ability to automatically create rules for applications signed by trusted vendors
  • Ability to disable content filtering for specific applications
  • Ability to block Flash banners and ads by GET request
  • Auto-Learn mode improvements

The following issues are resolved (only significant ones are listed):

Anti-Leak Control:

  • PC could freeze on Anti-Leak Control prompt if Punto Switcher was installed on the computer
  • Windows 2000 system could freeze on Anti-Leak Control learn dialog
  • FEEDBACK.EXE service issues (incl. Anti-Leak Control false positives, crash on system startup)
  • Anti-Leak Control false positives if processes write to their own memory on Vista32

Performance and stability:

  • Outpost could crash on downloading updates
  • Outpost could crash on displaying network activity
  • Outpost could crash on Vista x64
  • Slow start on Vista 64
  • CPU high load on deleting files to Recycle Bin on Vista 64
  • System slowed down while importing large list of advertisement keywords
  • Compatibility issues (McAfee Security Center 8.0, BitDefender 10.2, nProtect GameGuard, CA Anti-Virus 8.4.0.24)

Update and installation:

  • Error 101 while updating the product
  • Some folders were not deleted after installation over Outpost Security Suite 2007
  • Configuration was not imported correctly if installing over Outpost Security Suite 2007 or Outpost Firewall Pro 4.0
  • Windows Security Center integration issues
  • Service could not be unloaded if exiting the product while updating Outpost on Vista 32

Other:

  • Scan history was not preserved after switching to background scanning mode
  • Incorrect details of registry keys were displayed in quarantine
  • Web Control exclusions did not work
  • Issues while processing IMAP protocol traffic
  • Operation logic in case of "Allow Once" response to Rules Wizard prompt is changed
  • Files which size exceeded the specified value were checked irrespective of the corresponding setting
  • NAT Zone flag did not work correctly if LAN was marked as trusted
  • More minor fixes

Download.gifDownload: OSS & Outpost Pro v.2008

Could they actually be judged for calling that crap a FIREWALL?

I always thought a firewall is sth that protects a system from outside.

Using a "software firewall" (wtf?) is like putting a gate guard inside the castle.

D'oh.

to be protected from the outside is what a router is for

you use firewalls to stop outgoing connections

to be protected from the outside is what a router is for

A router is for routing, basically. Some routers, however, have the capability to block in- and outgoing connections. It is called firewall functionality then. You might want to read before you post.

you use firewalls to stop outgoing connections

OK, let's say we may call that crappy blinking software stuff some kind of a "firewall", too. How does that "firewall" protect then?

It mainly asks the user before anything is allowed, right? So where's the additional "security" aspect? I seriously doubt that potential malware will ask the user to allow bad_virus.exe or sth...

Malware, which doesn't use fake names or sth, often has an even better method to "kill" your "efficient" (rofl) "firewall" (even more rofl):

A software running under your account is having your rights and capabilities, too, right?

And you are able to perform a process kill, right?

And you are able to forward any ports, right?

I hope you get the point here.

Used to use it, hell my license is still valid but I've moved onto using Esets + My router has hardware. Basically I found this one too flaky when I moved to Vista and it wouldnt start up at times or would stop responding ect. That and as allured to before, its far far too paranoid even when you have settings set to be leanient. It was constantly nagging and I believe under my Vista install (not my XP one but) it was forgetting settings as I constantly got pestered over the same thing.

It's an 'ok' solution but when I initially tried it on Vista I was less than impressed. On XP it was a bit more mature but you do get the nagging. Bit to hands on for my liking.

  • 4 months later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
    • not yet, because at the moment it is not a threat to MS, if and I mean if it did become a threat to MS Office, then it may be a different thing. MS don't like competition
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!