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

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!