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

    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
    • Bypassed Windows 11 shows surprising stability on ancient, completely unsupported hardware by Sayan Sen When Windows 11 was first released, one of the most complained-about issues with the new desktop Microsoft OS was its higher system requirements, which pushed many relatively modern and powerful processors and devices onto the officially unsupported list. Thankfully, they have not been updated again for the base OS, though systems require four times the memory and storage if they want to run AI-powered apps and features. As such, Windows 11 technically runs on 4GB of memory, and there is no imposed restriction on the generation of memory it supports. Speaking of memory, prices are extremely high nowadays for hardware, especially DDR5 and DDR4 kits due to the current silicon shortage, and there are also reports of it affecting DDR2 as well, and it might only be a matter of time before even DDR1 gets affected. Before that could happen, an enthusiast took an ancient DDR1-based system and decided to try out Windows 11 on it to see how well the modern OS would fare on such hardware. The system runs an outdated graphics card interface standard based on AGP, or Advanced Graphics Port, called AGP 3.0 or AGP8x. AGP was essentially succeeded by the modern PCI Express (PCIe) bus standard. The user behind the experiment is retro hardware enthusiast Omores, who built the system around an ASRock ConRoe865PE motherboard based on Intel's i865PE chipset from way back in 2003, around the time when AGP was still in fashion. What made this board special back in the day was its unusual support for newer Core 2 Duo and even Core 2 Quad processors while still retaining older DDR1 memory support and an AGP8X graphics slot, making it an ideal bridge or link between two vastly different generations. Powering the machine was Intel's Core 2 Quad Q6600 alongside 3GB of DDR1 RAM and an ATI Radeon HD 4650 AGP graphics card, one of the final and most capable GPUs released for the aging AGP interface. While installing Windows 11 itself was relatively easy by bypassing Microsoft's hardware checks, getting the graphics card fully functional proved to be some challenge. Microsoft had quietly dropped native AGP support after the earliest releases of Windows 10, meaning newer versions of Windows no longer include the necessary Graphics Address Remapping Table (GART) drivers required for proper AGP acceleration. Without them, AGP graphics cards typically boot up, though with limited functionality, and can often throw a Code 43 error in Device Manager. To work around the limitation, Omores extracted Intel's legacy AGP440 SYS driver from an early Windows 10 release and paired it with a modified INF file so Windows 11 would correctly recognize the chipset. Following this and combined with AMD's final 64-bit Catalyst AGP drivers from 2012, the Radeon HD 4650 was able to operate with full AGP 8X acceleration intact. The result was said to be surprisingly usable for hardware that is over two decades old. Hardware-accelerated H.264 video playback worked correctly and benefited apps like Firefox, while legacy applications and games ran without major graphical issues. The system also successfully completed the 3DMark 2001 benchmark, although performance naturally lagged behind what the same hardware achieves under Windows 7, which is significantly lighter than Windows 11. There was, however, one unavoidable limitation as Microsoft's Windows 11 version 24H2 introduces a mandatory SSE4.2 CPU instruction requirement that cannot be bypassed through installer modifications or registry tweaks. Since no AGP-era processor supports SSE4.2, Windows 11 version 23H2 effectively becomes the final release capable of running on such systems. Regardless, it is still a very cool feat and quite fascinating to see just how stable Windows 11 turned out to be on such unfamiliar hardware. Source: Omores (Patreon) via O_MORES (Reddit)
    • That will only really help other players that are also responsible for creating the problem.
    • Well, it's good to know that they have found a workaround to a problem that they helped create, I guess...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!