"PHP Web Security Monitor" is designed to protect Internet sites created with PHP from malicious queries from hackers and Web viruses. It filters common PHP variables via prepared security patterns and compares (unprotected) input variables against patterns of dangerous data, such as SQL injection, XSS injection, and PHP code compromising.
Collax Groupware Suite is a complete collaboration, e-mail, and messaging server with Outlook MAPI support. It offers enterprise email server functions, anti-spam and anti-virus filters, GUI management, a file server for SMB, NFS, FTP, and Apple shares, backup/restore server, IM server, and fax and SMS server. The groupware offers AJAX Web mail, calendar, team calendar, contacts, and tasks, and supports ActiveSync for mobile devices. It is free for private or commercial use of up to five users.
phpLogin is a user login and authentication module for the phpNova framework. It contains all user authentication-related tasks and UI. Dependencies include: phpSession, phpHash, and phpSQL. This module is part of the phpNova framework for PHP, which is currently in the alpha stages of development.
Collax Business Server is an all-in-one Linux server for small- and medium-sized businesses. It delivers all the important network services within a heterogeneous business environment for communication, infrastructure, compliance, groupware, and storage, all in a reliable and secure way which is easy to manage. It also provides essential security functions such as firewalling and virus and spam filtering, to protect against hacker attacks, viruses, and unsolicited email messages.
The Dynamic Router Lite II project is a router project by the Dutch national police agency that allows Web-based client-control over the next-hop router for the client. A Dynamic Router Lite II system is placed as a default gateway between one or more client networks and a router network with multiple gateway-routers on it. The Dynamic Router Lite II system does policy-based routing with policy-based DNS to match the routing policy. By default a client will have no active gateway, and any attempted HTTP traffic to any domain will lead the user to the router's Web interface, where the user can then pick an appropriate next-hop router. Once picked, all traffic for the client including DNS will be forwarded to the next-hop router the user picked.