Monthly Archive for June, 2010

Squidwolf > Blog > 2010 > June

We are introducing a new project titled Squidwolf WiFi Blueprints. Basically if you would like to deploy your own Squidwolf WiFi network at a location of your choosing, you can now do so.

You can purchase one blueprint for $100 CAD or three blueprints for $230 CAD.

Anyone interested in updating their ALPHA accounts to BETA accounts early can do so by paying a one-time fee of $30 CAD which will last for the duration of the Private ALPHA test.

Welcome to Squidwolf Dev Blog. This is your first post. Edit or delete it, then start blogging!

Many of the mail scams we have seen rely on the fact that someone that is making a a connection through a proxy but isn’t protected by SSL. We used to have a large penalty for anyone caught doing that, but members complained about this since it required accepting an unsigned certificate as we don’t allow the use of our official SSL certificates over an unverified proxy connection.

To correct this we have introduced a new level 2 certificate that is signed by RAGE Hackerboard.

It turned out that there were more code errors in the last patch than you could shake an empty bottle of wine at, so we were up until all hours (at least in the UK) fixing this shit.

Now that I have received the logs from last night, which include logs from 04:30-11:00 I see that group-based security protocols were blocking the new code from being used, this has now been fixed.

So the low-level fix is holding and we’ll deploy a high level fix in tomorrow’s downtime, oh the fun of being a sysadmin.

Spent this week on a Parkour adventure with my friends from Wales. The whole of North Wales is just a huge playground for Parkour and at one point I didn’t want to come home. But as welsh people are accustomed to sticking to their ways, parkour somehow went on as usual, and with the good help of Adara and Lexi we somehow managed to avoid getting arrested and the Parkour went on at Conwy Castle. Drank some budweiser, ate McDonalds and met with a lot of great traceurs there. This has absolutely nothing to do with developing Squidwolf Syndicate but since I haven’t been focusing much on that over the past week I thought you should know what I have actually been doing with my time.

The reason for the Browser Crashes that have the following symptoms:

User comes into our network via a strange link and locks up. Only fix is to petition for a PH move.

I will now attempt to explain how the crash occurred.
Our network is composed of several small centralised servers. Depending where you are located on the planet, you are tied to a specific server. However, your server may not be responsible for some of the services you use on our network which is where the ‘SquidPassport’ system comes in.

When you attempt to access or use a service which your home server does not provide, your login is rerouted internally on our network to the destination server and then the service is transmitted back to you via your home server.

If your server is experiencing a high volume of traffic or the destination server is, this can in some cases cause a connection timeout somewhere along the delivery line which causes these crashes.

We have now fixed it so the traffic will be rerouted to another server on the network if such events occur and then on to the home server.

We need one more day to close down some issues raised in our internal testing and on the Patch Review board. This also gives us time to slap on Spam protection on invites, which makes invites to someone that doesn’t trust you limited and also makes it possible for us to track invite spam to confirm such allegations.

We have made changes to the member areas on our file server. Your ‘disk’ will now reflect the folder structures both on Mac OS X and on some Linux distributions such as Ubuntu. The folders are named as such and have the same permissions. Web files are now located in the ‘Sites’ folder and you can share files with other members through the use of the ‘Public’ folder.

We have automated login scanners at all areas of our network now. This means if we notice suspicious activity coming from the location where you logged in, network admins will be notified to check stuff out.

This part of our two-tier approach to protecting both you and us.