AppGuard 3.x 32/64 Bit

After a blocked launch has occurred with the protection level set to Locked Down, and the tray icon has been clicked to stop it blinking, the tray icon displays the green checkmark overlay instead of the padlock. The GUI is still correctly displaying the protection level as Locked Down. This is a bug in the tray icon display.

 

Thanks Pegr! I missed that one! I operated in High Mode mostly with AG version 3 so I missed a few of the bugs that only occurred when AG was in lock-down mode when we were testing that last release of version 3. I still really like that last build of 3 that was released! It works great for me! Too bad it did not support unicode. I believe Barb said that Medium level in version 4 is the closest equivalent of what high was in version 3. I got somewhat of a late start testing this time, but so far i've been using AG 50/50 percent of the time between Medium, and lock-down mode. I think it's best I do that for testing at least. I always find that you are very knowledgeable with AG. Keep up the great work! AG has become one hell of a product over the years because of users like yourself giving great feedback. Well, I got to get back to testing myself. I have a few things I would like to try with AG that I have not done yet.

 

Good suggestion. We are going to be focusing on "Install" related issues in 4.1. I will pass your suggestion on.

 

Adobe is a trusted publisher. Perhaps that's the difference?

 

Done. I hope we caught them all.

 

Thanks for the update! As I've mentioned we are going to be focusing on the install and update operations in the next release. All the feedback we can get regarding these types of issues will be helpful.

 

I may have commented on this previously - forgive me if I'm repeating myself. Right now the publisher list is not inherited and yes, if one of the exe files that an installer launches from user-space is unsigned, AppGuard may interfere. Anyway, we are considering implementing inheritance for trusted publishers in 4.1.

 

There is a *hidden* "Restore to Default" button on the Configuration UI. Go to the Advanced Tab and check the "Priviledged Mode" box. Click on Apply and the "Reset all settings to Default" button will appear. The developer responsible for this, felt that the button needed to be safe guarded - didn't want someone to click on it accidentally and lose all of their policy tweaks. I've been thinking about requesting that this be made visible at all times with an "Are you sure?" warning when it is clicked.

 

Sorry again if this has already been addressed. Apparently Opera now installs into a sub-directory based on the Version Number. AppGuard isn't recognizing this. We will address in 4.x, but for now you have to add manually add Opera to your Guard List.

 

Someone already probably responded to this question, but when you reduce the level to install (or off), a "Re-enable protection" check box will appear on the main GUI. Just un-check the check box. Remember to re-enable protection after your installation is complete.

 

Medium is the *new* High. It really should be as effective as the old High. We've actually increased security in one respect and slightly (very slightly) reduced it.

We've made the default policy for Medium to MemoryWrite and MemoryRead protect all Guarded Applications in Medium Mode (this is still configurable on the Guarded Apps tab though and if you're upgrading, your current settings with MemoryRead disabled will probably be honored - I'm sure our QA department knows exactly what happens, but sorry I don't right now).

We've only slightly relaxed the MG rules as follows: Guarded Apps are restricted such that they cannot read and write the memory of any other application (UnGuarded and Guarded alike), but AppGuard does not restrict UnGuarded applications from accessing the memory of any other application. Previous versions of AppGuard also protected Guarded Application's memory by preventing any application (even unguarded applications from accessing guarded applications memory). This eliminates the need for MemoryGuard exceptions. It also reduces the number of MG events (consider the case when one Guarded App access another Guarded App's memory - in that case we would get two events for the one operation).

 

I agree about the icons and we'll improve them with 4.1 (I hope). The jury is still out though about the persistent disable of the suspension timeout. We've had a couple comments about this and I *think* the consensus is that we will revert back to allowing this to be persistent. Again, it will have to wait till 4.1. I think that we'll allow the timeout value to be changed on the main GUI in the next version too. You would think this logic would be simple to change, but it hasn't been.

 

Definitely a bug and fixed in the release (which I hope hope hope will be out officially on Monday).

 

All fixed in the final release (except every time you reduce the protection level to Install or Off, you will have to un-check the re-enable button if you don't want to automatically re-enable).

 

Just got word - we will be offering a discount to those who purchased before 2013. More to come on this.

 

Now we are scheduling for 10/28.

 

Thanks! We're really proud of AppGuard and think that if it was more widely adopted that you wouldn't see so many headlines about successful cyber-security attacks. I can tell you that none of our enterprise customers have ever been mentioned in those headlines. Blue Ridge has been protecting many corporations and government customers over the past 16 years without a single breach! Commercial over.

 

Whew! That will teach me not to stay away so long. I think that I've caught up with all the posts and I don't believe that there has been anything new found in the beta that we haven't fixed (or elected not to - sorry) in the current release candidate.

We are scheduled for a soft launch on Friday (to those of you who have purchased AppGuard in 2013) and the official launch on Monday. I do know that our QA team found a fairly serious issue today that has already been addressed and I hope will not delay the launch (it was a bug introduced in a recent build - so we just backed the change out). Anyway, the head of our QA department is very meticulous so he may ask for more time (which is probably a good thing, but can be very aggravating as well). In the long run, it is for the best with respect to product support.

For the soft launch, if you purchased AppGuard in 2013 you will get an email sometime on Friday with your new license code and a link to download the product. I will also request that we update the beta link with the latest version so those that beta tested can upgrade to 4.0.17 (I hope hope hope that is the last build for 4.0). For those that have the beta already installed, I recommend that you uninstall first and re-install. Our QA department tests upgrades from previously released versions only. Since the beta wasn't an official release that upgrade probably wasn't tested. Also if you already activated your license, make sure that you are online when you uninstall. That way you can re-activate when you install the official release.

 

Wow, my name just turned red and I'm now a "Developer". How did that happen? Sure hope this means a raise for me at Blue Ridge

 

barb turn orange

 

I am actually wondering why your name is not orange. And now it is.

 

What does it mean that I'm orange now? Does it mean that I can't be trusted?