GSS Alpha 1.2 Feedback

Blank Alert

While we are on this subject, I have gotten them during boot-up before getting to the XP welcome screen and entering my password. Initially I thought very little about it, but something in the last one got my attention. In the upper left of the alerts one will see an icon of which GSS program, AD or RD, triggered the alert. On my last alert sitting there as plain as day was the RD icon.

The only thing I can think of is, with the tighter integration and interaction between AD and RD that RD is not completely disabled in the current 1.200 Alpha. Maybe Jason will see this and give us an answer.

 

I tried to add a new application using the Browse feature in the Maintenance section of AppDefend. Everything was configured the way I wanted it, but when I went to start that application, it was not recognized by AppDefend, and it asked for permissions again.

The only thing different I saw is that the Browse feature adds applications using Mixed case, where it is all lowercase when detected by the AppDefend engine.

I removed the apps from the known list and tried again.

When I changed the path to lowercase after selecting the browse feature a second time, everything worked as expected.

Also, is there any way to have AppDefend ignore the SHA256 checksum on specific applications? I am a software developer, and everytime I recompile my application(s), I am forced to select an option to trust the application again.

Thanks for such a great product!

 

Hi disciple.
This comportment was also noted by me in the previous post.
It's indeed an rd alert... and we all imagine htere are reason why rd is ddisabled in this alpha ... it need a bit more tuning. So there's nothing to worry here.

-------------------------------------------------------------------------

On another note i have a couple configuration problem.

1) Each time i first reboot after a blank install of gss everything is ok.
I choose allow alwais to everything i see.

2) After the reboot, I'm stuck in front of a blank black screen with a white mouse... nothing more ... nothing left.

3) This happens in all consective reboot, not in safe mode.

4) In safe mode, i delete gss_ad.rul and reboot

return to 1: ok

So there is something that get badly configured while i choose allow alwais to all ??

Here's a screenshot of a badly corrupt ? application path

 

I finaly got rid of the problem.

It looks like appdefend is alergic to having a file:
LogFile.Etl at the root of the C:/ drive.

I can now reproduce ad noseam the "black screen freeze"
If that file is there, and gss_ad.rul is there ... stuck black.
If only one of the file is there ... ok.

LogFile.Etl is created using the WMI Global Logger.
I had this file after using BootLogXp from greatis software.


The strangest thing is:

WMI logger and appdefend cohabit nicely when logger is enabled.
However is logger is disabled but the Etl file is there, the problem arise.

 

When running the new GSS Alpha 1.2 on my Windows XP Pro machine, I'll let it sit for awhile causing the screen saver to activate. This in itself is not an issue, since I have chosen to allow the screen saver, however if some background processing from an unrelated and untrusted application begins after the screen saver starts, I will receive a warning from AppDefend that the application wants to begin. The AppDefend dialog appears on top of the screen saver, however when moving my mouse to click on a button to prevent the application from executing, instead the screen saver ends, the AppDefend dialog disappears, and AppDefend appears to execute the default action for the application.

I would hope that mouse and keyboard activity could be hooked and prevent the screen saver from closing the AppDefend dialog.

Looking forward to the next release!

 

Have any of you noticed multiple popups of the same process to allow or block even after clicking allows allow? I keep getting certain ones and have the same command line.

dja2k

 

Can you copy/paste some examples of what you are seeing? Not to doubt you but, are you absolutely sure the command lines are exactly the same? I ask this because I am getting alerts for the monthly Windows updates. The command line is similar but not exactly the same, and the wildcard feature is not implemented in the alpha release.