We were recently asked to diagnose a networking problem: the customer has a group of boarding houses that are connected back to the main school network through a microwave link. They were reporting that Windows logins worked fine at the school, but if they took a laptop to the boarding houses they were left waiting upwards of a minute to log in.
On November 2nd, Scottish internet and e-mail security firm Bloxx announced that they had been acquired by US based content delivery company Akamai. The company says that they will be honouring the ongoing contracts with their customers. But according to CEO Charles Sweeney "the current Bloxx product set will no longer be available for sale or refresh" and renewals will only be offered until the end of January.
Over the past few years, HTTPS interception has become extremely important. Without it, online safety systems are extremely limited in their ability to filter and record auditing data regarding secure websites. The way this works is relatively straight forward: the client asks the Iceni proxy to connect to a secure web site, Iceni negotiates a secure connection with the web server, copies the web server's certificate and uses it to negotiate the secure connection with the client.
Two days ago, Google announced a new Google Apps feature to allow administrators to control what YouTube content is accessible to their users. This is a replacement for the old YouTube for Schools service, which Google withdrew to new signups over a year ago.
As we've discussed before, we've been developing a few improvements to the Iceni's powerful hierarchical grouping system. You can read more about the existing group configuration system in the knowledgebase article. The group configuration system has proved extremely successful, but we wanted to extend its flexibility whilst keeping it very understandable.
Over the years, the Iceni's hierarchical grouping system has proved itself to be extremely flexible and easy to understand. You can read more about the group configuration system in the knowledgebase article. However, it has always been limited in how fine-grained the configuration can be - since the configuration is applied to whole groups, adjusting the configuration for a single user required a group to be created just for that user.
