Monday, February 07, 2005

Port Blocking

It started with locking any ports that would be used by instant message clients. They didn’t really say they would be locking the ports; it came by way of an “update”. Though it was inconvenient, it allowed me to get a lot more done. They also came up with an internal message system that works very well for all users internally. Not quite as featured as other clients, but it works.

Three months later, we get another set of updates, and I notice that FTP is gone. I decided that I could live without FTP, as I have a flash drive that I can carry with me.

Today, I tried to set up outlook so that I could check my school email from work. Guess what? Those ports are also locked. I tried to SSH to the school server to see if perhaps I could check my email using pine… locked as well.

What does that leave? The web.

I suppose I could forward all of the mail from the school account to Comcast, or Gmail. I can still get at both of those via the web. Maybe we will be loosing that soon as well though forwarding out of the school account defeats the purpose of having an IMAP email account.

Oh well. At least I have a job. It is probably a good thing that they care to make sure that we are as productive as possible. From a security point of view, it makes a lot of sense to make sure that information can’t leave the system via any un-approved channels. It is annoying though.

I am done blogging from work. I don't want to be part of the reason that they would want to restrict employees from the web as well.

No comments: