in

eEye Digital Security

The endpoint to vulnerability starts here.

 

apiex.ini

Last post 03-25-2008 10:17 AM by Spunner. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 03-21-2008 1:51 AM

    apiex.ini

    In the event logs I found the following message: If you believe this application is not malicious, you can add it to a list of approved applications in the Config\apiex.ini file using this format 'FilePath;[Optional MD5];WriteProcessMemory;0' .         If I follow this file path C:\Programme\eEye Digital Security\Blink\Config, I find 2 apiex files. One is a DAT, the other is an editor. None says "ini". Which one should I choose?

    I do also have a system protection wizard in Blink Personal. Could I achieve the same result by creating a system protection rule? What is the difference?

  • 03-23-2008 1:51 PM In reply to

    Re: apiex.ini

    Hello lalulofi,

         The one that you should be able to modify is the editor file.  If I remember correctly it looks like the text file format.  Modifying this file will exclude a particular file, or application from being protected under Blink's Application Protection Engine (known as "Kevlar").  This is best used when you know a program is ligitament, that you want to run, but because the program's behavior is suspicious to Blink, it is giving you that warning.  There are a few other things you can read about the "apiex.ini" file in and how to modify it.  One of these posts I made (when Blink Personal Edition was first introduced to the public) is located at: 

    http://forums.eeye.com/forums/p/54/140.aspx#140


         The system protection wizard, if I remember correctly, is used to create explicit rules for things you want to protect your system from.  Hence you know the exact thing that will "trigger" or set off the rule, what it affects on your system, and how you want Blink to react to protect you from it, etc.

         I hope all this makes sense, if not I am sure one of the eEye folks here will pick up on your post and assist if necessary. 

  • 03-25-2008 10:17 AM In reply to

    Re: apiex.ini

    If you go and look at those files again, click "Tools"  "Folder Options"  "View"  and uncheck  "Hide extensions for registered file types" (or however they're wording it these days)  then you will all of a sudden see that the one you thought was an editor, was really apiex.ini   

Page 1 of 1 (3 items)
© 1995 - 2009 eEye Incorporated