Monthly Archives: November 2003

something lost in translation

Posted by Julian Dunn on November 25, 2003
Internet Services, Networking / 2 Comments

Company name of the offender removed for their protection (they’re already in Chapter 11 – no need to help them along here)

Dear valued customer,


On the 25.November 2003, 11:35 we had a route leakage. Due to a mistake on the -------- backbone, we anounced to many routes.


For this reason many peering-sessions were closed automaticly. Issue is resolved. Situation is going normalized.

Regards

[deleted]

Heh. "Situation is going normalized" — I have to use that one in resolving RT tickets.

Blocking Opera Ads using Squid

Posted by Julian Dunn on November 02, 2003
Tools / No Comments

If you use Opera — like I do, on occasion — you’ll notice that it’s ad-sponsored software. Fortunately, since I use Squid as a proxy server (so that I can use Cameron Simpson’s very excellent adzapper to replace ads based on regular expressions), I just added ACLs for the Opera ad servers in order to stop the browser from downloading the ad database.

Add this ACL to your squid.conf:


# Opera browser spamvertisement access server
acl operaads dst 209.225.0.6
acl operaads-master dst 209.225.11.237

http_access deny operaads
http_access deny operaads-master

Then you can just squid -k reconfigure and away you go.

Incidentally I used this to block requests to Verisign’s much-maligned SiteFinder [dis]service:


# Trap and deny crock A records
acl sitefinder dst_as 30060

http_access deny sitefinder

SiteFinder has been suspended, but you might like to block that AS anyway in case they start it up again :-)

*LET* the Lawsuits Fly.

Posted by Julian Dunn on November 01, 2003
Culture, Windows / 1 Comment

Wow. It’s been a while since I last wrote. Happy Hallowe’en, by the way.

I now work for CBC.ca in the New Media Production & Operations department as a software developer. Primarily this involves Java development, but I also do a bit of Perl (as much as I hate to). I also weigh in on system administration matters quite a bit, since I think of myself as a half-time sysadmin, half-time programmer.

I just had to respond to this slightly brain-damaged article which appeared in eWeek recently. Now I know eWeek is one of these magazines for PHBs but I still like to flip through it (very briefly) to see what the PHBs are being told these days, and how I can counteract that. So this article — if you go and read it — basically says well, Microsoft has to make "Longhorn" really secure, and improve their security in general, or else legislatures will impose security warranties upon software developers, and this will impact all developers and not just Microsoft.

My reaction — as both a sysadmin and a developer — is: so what? Isn’t that a good thing? I’ve often railed about the fact that software is but one of the few industries where you can sell an expensive product to someone and not be held to any legal liability whatsoever. No warranty to speak of beyond the value of the actual compact disc that the software arrived on. In my mind, this is a bad thing. So when Brian Livingston says something like

Such an earthquake could emerge not just from legislatures but also from courts. All it would take would be a precedent-setting ruling that the “we’re-not-liable” language that’s commonplace in shrink-wrap licenses is “unconscionable and unenforceable.” The lawsuits would fly.

I think he’s bang on — but the lawsuits should fly, in fact, if the software is defective. This would certainly stop not only Microsoft from shipping poorly-tested products, but all software vendors.

On a lighter note — check this out. If you work for Allstate, you can submit your resignation online. No word on whether a security guard will be e-mailed to you to escort you out of the building, too. (Speaking of which — someone at work was joking about dressing up for Hallowe’en as a manager who was unceremoniously sacked some time ago. “I’ll just dress up two mannequins in security guard uniforms, put one under each arm, and I’ll be [name removed] being escorted out of the building!”)