Blogger, Layered Security, And You

One of the problems with getting Blogger Engineering to fix the many problems with Blogger, is that each problem involves code that is provided by Blogger on their computers - but run by us, on our computers.

Whether a problem involves Blogger / Google logins, commenting, Stats, Template Designer, or the Dynamic Templates, Blogger writes the code, and we run the code - when we allow the code to run.

If we want our computers to remain under our control, and not become part of one or more worldwide collection of computers controlled by hackers, we have to be selective about what code we allow to run on our computers. In the computer security world, this is called "Deny by default, allow by exception."

We are protected by filters, which block both cookies and scripts, in various places.

• On our networks.
• In applications, on our computers.
• In our browsers.

Long ago, this was called "layered security", and was a good thing, since it helped us to keep our computers under our control. Each layer backs up the other layer, in preventing malware from being installed, or from running, on a protected computer.

Layered security is still a good thing, in general. With Blogger becoming both easier to use, and more full of features, Blogger code is more susceptible to damage from filtering, by layered security. Cookies and scripts, to be useful, must be properly permitted by all layers of the security strategy.

When we have a problem with using Blogger

• We can't login to Blogger, or stay logged in to access and maintain our blogs.
• We can't post comments to our blogs.
• We can't view Stats for our blogs - or can't view Stats with the desired detail.
• We can't customize our blogs, in Template Designer.
• We see only endlessly turning gears, instead of blog content.

These are all problems with Blogger, possibly caused by layered security, improperly implemented on our computers or our networks. And most of these problems are ones that we need to fix, by learning how to control the filtering.

Similar to problems with filtered cookies or scripts is the decision that some blog owners make, to clear cookies / scripts when restarting the browser. Whether the cookies were never created, or deleted when the browser was closed - if the cookies don't exist when needed, or can't be accessed when needed, an application like Stats or Template Designer won't work properly.

Every layer in the security strategy must be properly configured, to work with the other layers. Both cookies and scripts must be carefully considered, in the settings for each layer.

• Browser native filters. If you use Internet Explorer, be aware of the IE zone defense.
• Browser add-ons and plug-ins.
• Anti-virus and firewall suites, on the computer.
• Modems and NAT routers, on the network.

And as you install add-ons, and change various settings, keep track of what you change. Don't become tempted to sacrifice an elephant, to make your Blogger application work, later.

>> Top