Jump to content

mutez

Members
  • Content Count

    2
  • Joined

  • Last visited

About mutez

  • Rank
    Candidate
  1. Hi, In the previous versions the method in which you have used to implement inheritance in the policy is not standard the standard inheritance. From a programming point of view in inheritance where there a parent entity (e.g entity A ) and a child entity (e.g entity B ) if you use inheritance the child entity is (B) is supposed to inherit some characteristics of parent entity (A) and still retain some of its characteristics. The way inheritance works in the KES policy if let say you have a policy in the managed group and another policy in the a child group. If you enable inheritance in the policy of the child group whatever change you make to the policy in the child group is over written by the setting in the policy of the parent group. For example in web control if you want allow access to the internet to everyone but restrict some groups of users from accessing certain URLs and you add some urls to be blocked in a child group the URLs are overwritten by the rules specified in the parent group when inheritance is enabled. Could you kindly check on this.
  2. Hi, the option for blocking secure connection if the certificate is not trusted is a really great functionality. can you add an option for giving the user a warning if the i certificate is not trusted so that the user has the option to choose whether to proceed or not instead of just blocking without giving the user a chance to choose. Also can you add an option to scan TLS certificates (some connections use TLS) because i only saw the option for SSL certificaes.
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.