I'm not embedding the video stream here, only because I have not requested permission from Fox. Clicking through the link below will take you to the 2-minute piece, however:
I have a couple issues with the segment, which caught my eye a few minutes ago:
Egad... Drinking the Kool-Aid? Who are these people in this blog post, anyway, and what on Earth do they know of data security?
I recently had the distasteful experience of having to tell a long-time client to find someone else to handle his IT consulting. We had (I thought) become friends over the years, though recently, tensions surrounding some server trouble over here (I hosted his email) led to difficulties in our relationship.
NettiCat has graciously granted me permission to modify (slightly) his BetterPrivacy extension to allow for installation and use under SeaMonkey. The current version (1.68.m, as of the date of this post) should install under SeaMonkey 2.0a1 and above.
For those not familiar with this extension, it goes beyond the built-in sanitizing functionality of Firefox and SeaMonkey to include clearing the Flash cookies, which may be stored for an otherwise indefinite period of time. For more on the actual feature set of BetterPrivacy, I would suggest reading the information available on the official home.
Download & Installation
Ultimately, BetterPrivacy for SeaMonkey 1.68.m (and later) should be available for download from the Modified Firefox Extensions page of the xSidebar project site. You may also download it from the Rosenthal & Rosenthal FTP site via anonymous transfer.
Please feel free to post comments here for support. I can't guarantee that I'll respond quickly to such requests, but any SeaMonkey-specific issues should be directed here and not to the official support page.
Changes from the official 1.68 release, specific to SeaMonkey
- Installation is enabled for SeaMonkey 2.0a1 and above.
- Changes per NettiCat's requirements.
- Option to auto-delete Flash LSOs on exit is available on preferences panel.
- References to "Firefox" in dialogs (in the en-US locale) have been changed to "browser" for a more consistent feel.
- Some en-US language enhanced.
Localization support is welcome. There are a number of languages currently enabled, and I can't adequately translate all of them (I am passable at a handful, but native speakers are encouraged to participate).
First, my heartfelt condolences to everyone who was impacted personally or financially by yesterday's DDoS attack against GoDaddy. That includes customers and employees, and as an admin, I know firsthand what it's like when the systems grind to a halt under one of these things, when all that's left is simply to put something else on the front line to check for traffic and wait it out (or request new address blocks all the way around). This, of course, does not take place in a vacuum: when these things hit, we are always surrounded by The Suits who have no clue as to why we can't do anything more (or faster), constantly complaining of our inadequacies (we should have known better; we should have predicted; we should have been better prepared; etc.).
As a consultant, I look at computers and operating systems from a "best tool for the job" perspective. Some systems are better suited to some things than others. I wouldn't expect to play modern computer games, written for Win32 or Win64 on Linux or OS/2, no matter how far advanced Wine or Odin was/were. Likewise, I wouldn't consider running a web server on the Win32 or Win64 platform vs Linux or OS/2.
Along with other suitability considerations, I factor in my own (or the client's own) comfortability factor with a particular environment. The Mac object oriented desktop is quite nice, though it's not my environment of choice. On Linux, I prefer KDE to Gnome, but neither of those nor the Mac desktop nor Windows Explorer approaches the level of comfort, familiarity, or ease-of-use which I experience using the Workplace Shell, which is - for me, at least - the main reason I stick with eCS.
Stability concerns? These affect all platforms at one time or another. Unless the problems are inherent to the overall system design (Windows' weak security model and the dangers of the single registry paradigm), such things need to be considered in the course of business. that is to say, they happen. Cars break down, too, but I'm not quite ready to go back to a horse and cart (and carts break - ever change a wagon wheel?).
Ah, into the land of (broken) Windows we go...
I despise Windows. Have I said that before? Here, in case I haven't, I'll say it again. I despise Windows. That feels better. It's good to get such things off one's chest. What a hopelessly broken operating paradigm. Oh, well. It's gotten better, I guess. that is to say, it used to be even worse.
I've been spending much time of late working between zypper and yum on various flavors of Linux and now, eComStation, which has its own port of yum. Of the two, I prefer zypper, though either is head and shoulders beyond the inane Windows patching system. However, when in Rome...
There is a lot of malicious junk floating about the net.I know; that's not a real surprise. Under normal circumstances, a good (standalone) firewall will keep one reasonably safe from the worst of it. However for those of us who travel, it's a constant challenge to keep up with personal firewall tweaking and such, and still, unless one is really running the kinds of stuff typically found in a UTM (Unified Threat Management) solution, just tweaking some firewall rules just isn't going to cut it.
So, what can one do while traveling? Trust the hotel firewall? I think not. Here are three quick tips to help keep your system clean from would-be spoofers and such:
A quick edit of your hosts file to loop back known bad sites to localhost (127.0.0.1) is a good start. To get started, have a look at the list compiled here. This will make some web pages look rather ugly, as the browser brings up the dreaded "cannot access..." in various iFrames and such, but it will speed browsing and keep that excess junk from cluttering the screen.
Squid proxy settings
Squid is great. You can do a lot of things with Squid, such as block entire IP ranges from getting in (or going out to them), which improves performance considerably. I'll post more on Squid configuration in a later article. For now, suffice it to say that Squid can be used as a pseudo-firewall (you just have to not defeat it by turning it off, but this is true of software firewalls, as well).
Another type of proxy is a privacy screen. Enter Privoxy to the scene. One of the annoying characteristics of most web surfing from modern browsers (and ancient ones) is that we tend to leave behind more than we take with us. To truly surf anonymously requires some type of anonymizer, and Privoxy is a good choice (this way, your travels don't follow you home, when you finally do get behind your warm and cozy hardware firewall). A couple interesting guides for chaining Squid to Privoxy (or vice-versa) may be found here and here. Again, I'll post more on this in a subsequent piece, but for now, suffice it to say that this is an excellent addition to your arsenal.
These are but three fairly quick and simple (well, they can be less complicated than others, at least) ways to browse more safely, and are of particular usefulness when away from home (or the office), where the bastion server is unknown and likely not to be trusted. In time, I'll flesh in more details and tips for configuring each of these solutioins.
As I sit here at Panera Bread, catching up on some tech news, an article caught my eye concerning Mozilla's new approach to updates and, tangentially, the (revised) 2011 Firefox release schedule. This started my own wheels turning, as this has been a bit of an annoyance for me, so I thought I'd just jot down a few ideas...
Concerning Firefox's 2011 release schedule:
We (I say "we" because I do/have contribute(d) from time to time) have some bugs in Bugzilla which date back several years (some to the Netscape Communicator days, inherited by the Mozilla project - no kidding!). These have yet to be quashed, and all the while new "releases" just keep coming down the pike, bringing with them their own share of new insectoids. Wouldn't it make more sense to stay at a reasonable "release" level, and just fix it before adding new features (and after all, isn't the purpose of a new "release" to introduce new features)? We already have a mechanism in place for extending the functionality of the browser through plugins and extensions, anyway, so what's the point? (If Mozilla wants to emulate Redmond, then they should consider that under the hood, Windows 7 is NT 6.1, anyway, and Microsoft got a head start with NT growing out of OS/2 - NT started at version 3.)