Archive for November 2011

HOSTS file.

November 17, 2011

Whenever I am asked to work on a PC, the first thing I do – every time – is install a HOSTS file. It’s one of the simplest security measures you can take – just a text file in a folder – and the least well known. Everybody knows about virus scanners, many users know about malware scanners, but very few people know about the HOSTS file.

So let’s start with what a HOSTS file is.

You may already know what a DNS is: for our purposes here, it’s a map that points a domain name to the address of a computer somewhere on the internet. For instance, “google.com” maps to 173.194.64.104. That number, or “i.p. address”, refers to a specific end-point, or node, on the internet. Tables of DNS records are stored on special servers, so when you type “google.com” in your browser, a request is sent out, the i.p.address is returned, the connection is made, and the computer Out There and your computer Right Here begin sharing information, in this example, a web page.

The HOSTS file is the first stop on your browser’s trip. You’ve got one on your computer now: if you have a Windows PC, go to c:\windows\system32\drivers\etc. Open the file in Notepad. What you’ll see – after all the #comments at the beginning – is an i.p.address and domain name, probably this:

127.0.0.1     localhost

Another way that us computer guys say 127.0.0.1 is “home”. (It also goes by the term, “loopback.”)

In short, it’s the i.p.address that your computer uses internally to refer to itself. Your computer’s way of saying, “me.”

What this means is that if you type http://localhost into your browser’s address bar, your browser looks to the local computer for that content. (Unless you have a web server installed, it won’t find anything, but you’re welcome to try.)

Here’s the important part:

Because you provided an i.p.address for the domain, the browser stops looking. It doesn’t go to the internet for the content because the HOSTS file says it’s local. Because there’s nothing there, the request dies.

So?

Let’s pretend, instead of an innocent internet user, you’re a piece of malware, and you need to send the information you’ve collected back to the lair of the evil mastermind. You’re programmed to look for myEvilOverlord.com, which is, unfortunately for you, an entry in our hosts file. You can’t phone home.

Let’s pretend, instead of a piece of malware, you’re a browser add-on, and your job is to pop open advertising windows. You do this by connecting to the server of your Evil Mastermind to determine which gambling or porn sites you’re supposed to load. Unfortunately, again for you, myEvilOverlord.com is blocked. No windows open because you can’t get your instructions and if you do open any, they will be blank.

Isn’t that awesome?

So, that’s all?

That’s all? We’ve blocked malware from transmitting your credit card number and prevented your mother-in-law – who’s checking her email while you’re fixing yourself a stiff drink – from getting a dozen pop-ups for Asian scat and bondage porn, and you say, “that’s all?”

No, as it happens, that’s not all.

You can be a jerk about it.

Go to one of your co-worker’s PCs and put this entry into the HOSTS file:

127.0.0.1     www.facebook.com

I’m sure you could find an interesting i.p.address to plug in. You can repoint a website to ANY i.p.address, though you should note that just because you type in the i.p.address of some objectionable site, doesn’t mean that the site will load. Many times, the domain and the i.p.address are linked on the host: you’ll connect to the server, but it won’t show you anything worthwhile. Might be fun to experiment, though.

But seriously…

Your browsing experience will be, just generally, different. Cleaner for one. Take this LiveJournal blog, for instance:

Those ugly purple blocks are ads. This poor user is browsing the internet without a HOSTS file. Tsk tsk tsk.
This is the same blog, viewed on a PC with a HOSTS file. Look ma, no ads!

Now, there are two warnings I need to offer here.

First, you won’t see ads and much content in the margins of your browsing experience, so you might forward a web page you think is hysterical and get an angry email from your best friend complaining about the porn ads on the page. (Use that as an opportunity to set her up with a HOSTS file.)

Two, many websites track button clicks through ad hosting/tracking services that a full HOSTS file blocks, and if that’s the case you’ll get on the site but won’t be able to navigate. HowStuffWorks.com is that way: if I want to browse the site, I have to disable my HOSTS file. The “sponsored” links in yellow at the top of your Google search? Blocked.

Those are minor issues, though. It’s very worth it for better, faster, and most importantly, safer browsing.

OK, so where do I get one?

Here.

Advertisements

First Wedding Video

November 6, 2011

Several weeks ago I videotaped a wedding. My friend Lezlie referred the couple to me, and I accepted. I’ve always said no to that sort of thing because I’ve heard horror stories about bridezillas, but even moreso because it matters: I don’t want to be the guy that people point at and say, “That’s him…that’s the man that fucked up the record of the most important day of my life.”

There is a man named Mark with whom I have kept a casual friendship for a few years. My brother knows him: they both work for Entercom Radio/Media. We’ve met once in person, and stayed in touch through Facebook, and I knew through that venue that he’d recently purchased a set of studio lights. I sent him a message, asking if that was true. He wrote back, “Yes, why?”

I don’t know why I did it, but it was an inspired choice to contact him. My initial thought was to just ask if I could rent his lights. The question was typed and sent before my brain registered the action: “Want to help me shoot a wedding?”

I didn’t even know he had a video camera – as it turns out he has two. Between the two of us, we ended up with four cameras to shoot the wedding: bride-cam (static), groom-cam (static), Mark-cam (mobile), Me-cam (mobile). The plan ended up being to let the two front cameras capture the entire service from different angles at a fixed point of view; that would be the foundation. Then, Mark and I with our two cameras moved from place to place, capturing whatever looked interesting: reaction shots from the congregation; the ring bearer (cute but precocious kid) handing the ring to the best man; the scripture readings; things like that.

A year ago, I might have called a couple of old friends to help me with this, and I would have been nervous the entire time, wondering if they were capturing what I needed. They’re really good behind a camera, if they have very strong direction, but if you just point them in a direction and push to get them started, they will eventually wander. Their idea of “good enough” is nowhere near mine.

I finally saw his footage after finally getting a card reader and downloading it, and my impression from watching him at the service was correct: he paid attention – very close attention – and captured everything I needed him to. It was like dancing: we each just moved with the “music” of the service and reception in a loose step, me leading, him following from across the room. He even caught some moments I didn’t expect, but were absolutely beautiful choices: a close-up of the organist’s hands for instance.

Adobe Premiere Multi-Camera Monitor

The groom said to us at the reception: “Man, you guys were everywhere and nowhere.” That was the best compliment he could have given us. The priest even thanked us for our discretion at staying unobtrusive.

I learned through this process that Adobe Premiere has a multi-camera feature, where it will place four separate tracks of video into an interface where you can watch them simultaneously and pick and choose your shots on the fly. It saved me hours of time I’m sure.

I’ve nearly done editing. The finished product looks amazing.