Diladele Web Safety 3.3 Alpha 2 is Available

The alpha 2 of Diladele Web Safety 3.3 is available as of today for download at http://quintolabs.com/soon.php. The following new features and improvements are added in this version:

  • Web UI is improved, it is now based on Bootstrap 3 and partially on AngularJS, looks to some extent better and is not so ugly when viewed with Microsoft Internet Explorer.
  • Totally reimplemented Active Directory (LDAP) server integration and user matching in windows security groups. Hopefully this will make the task of using Active Directory groups as members of policies easier.
  • Added long awaited support for custom categories. The format is the same as in SquidGuard or Dansguardian. Hopefully simple copy of your custom made lists will be enough to use them in policies.
  • Advanced exclusions (like gray listing in terms of dansguardian). It is now possible for example to block file downloads from a web site and exclude it from other types of filtering at the same time.
  • A lot of small improvements and fixes.
  • Daemon configuration is now JSON based that will make it very easy to embed into your custom solution (i.e. in your our network filtering projects).

Please download and use this version. Direct all your ideas, issues and bug descriptions to support@diladele.com. We are now concentrating on fixing minor glitches in our code for pfSense/FreeBSD platform.

BTW anyone interested in native pfSense package for Diladele Web Safety?

Best regards,
Diladele Dev Team

About sichent

sichent
This entry was posted in Active Directory, Diladele and tagged , . Bookmark the permalink.

4 Responses to Diladele Web Safety 3.3 Alpha 2 is Available

  1. ryan says:

    I get this error on some https sites and some sites like google.com bing.com https filtering is working good. can you tell me what i am doing worng?

    The following error was encountered while trying to retrieve the URL: https://sichent.wordpress.com/*

    Failed to establish a secure connection to 192.0.81.250

    The system returned:

    (54) Connection reset by peer (TLS code: SQUID_ERR_SSL_HANDSHAKE)

    Handshake with SSL server failed: [No Error]

    This proxy and the remote host failed to negotiate a mutually acceptable security settings for handling your request. It is possible that the remote host does not support secure connections, or the proxy is not satisfied with the host security credentials.

    Your cache administrator is admin@localhost.

    Generated Wed, 04 Jun 2014 16:23:51 GMT by localhost (squid/3.3.10)

    • sichent says:

      Well squid could not establish connection to HTTPS site – I cannot say anything else, may be squid logs tells why? Please update your OS to be sure you have latest OpenSSL just in case…

  2. CoreDuo says:

    +1 for native pfSense package since the manual instructions can be error prone and cumbersome.

  3. RRG says:

    +1 for native pfSense package too,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s