Jumat, 31 Desember 2004

Thank You for a Strong Year

The image above comes from my Sitemeter blog statistics page. I'd like to thank all of my readers for making the TaoSecurity Blog part of their Internet experience. We've had about 337 posts this year, on a range of subjects. Our two year anniversary will happen January 8th.

I'd also like to thank those of you who have been reading my Amazon.com book reviews and voting them "useful." I receive no monetary compensation for any book reviews done at Amazon.com or here, but I do like seeing positive feedback on my reviews.

I hope to keep blogging and reviewing as I begin work on my next book, tentatively titled Extrusion Detection: Network Security Monitoring for Internal Intrusions. I'll post information on Extrusion Detection once I have an ISBN, but I expect it to hit bookshelves in the fall. My collaboration with Keith Jones and Curtis Rose called Real Digital Forensics should appear on bookshelves in the summer.

2004 has been a great year, especially with my wife delivering our first child last month. We're looking forward to an excellent 2005, so happy new year everyone.

Kamis, 30 Desember 2004

Review of Building Firewalls with OpenBSD and PF Posted

Amazon.com just posted my five star review of Building Firewalls with OpenBSD and PF. From the review:
I was an early buyer of the first edition of 'Building Firewalls with OpenBSD and PF' (BFWOAP), but I am confident my opinion applies to the second edition as well. BFWOAP is the perfect book for anyone looking to build an firewall with Pf. Since Pf is now part of FreeBSD, NetBSD, and DragonFly BSD, this book will be helpful to anyone looking to use Pf on those platforms...

The author's blog indicates he is working on a new firewall book that expands beyond OpenBSD and Pf. I hope he is working with an established publisher to ensure his next book has a wider audience."

Rabu, 29 Desember 2004

Today's ISC Handler's Diary Is Partially Right, and Then Completely Wrong

I read the following in today's Internet Storm Center Handler's Diary:

"Pay attention, you’re about to read something vitally important: COMPUTERS ARE NOT APPLIANCES. THEY ARE TOOLS. Tools require that their user be skilled. Tools require education and training to use. Tools require a level of involvement beyond that of an appliance because 'tool use' carries with it an inherent danger...

[O]ver the past decade, the computer industry has deliberately ignored the nature of its product. It has attempted to grind off the sharp edges, to put padding on the corners, and to make a 'consumer safe' appliance from these inherently dangerous tools. The current state of security on the Internet is simply reaping the seeds we have sown...

We don’t allow untrained and inexperienced drivers onto our streets, but any yokel with $9.95 a month can get on the Internet...

The time has come for change. Users cannot continue to proxy the responsibility for their security to others. If they’re going to use this tool, they need to be trained or they need to pull the plug (or have the plug pulled for them).

What can you do? Teach.

Organize a community 'adult ed' class to teach people security basics. Sit Aunt Sophie down and make sure that she has (and, more importantly, understands why she needs) a firewall and virus scan. Check with your local School District and make sure that while they’re teaching the impressionable young ‘uns how to create a graph using Excel, that they’re also teaching them safe computing habits. Scout your neighborhood over the next week, looking for discarded Christmas computer boxes, and knock on the door and offer your services.

We’ll all be glad you did."

The correct part is the statement that "computers are not appliances." Everything else is completely unrealistic. I sympathize with the Incident Handler who posted this advice, but I disagree with his proposed remedies.

According to Internet World Stats, as of October 2004, the United States had almost 200 million Internet users -- over 2/3 of the population. If 97% of of those users were taught to behave "properly" or "safely" on the Internet, that would still leave 6 million "risks." Why did I choose 97%? That's the United States literacy rate. (Forget about those who are "functionally illiterate"; that makes the situation even grimmer.) If we can't even get every American to read, how can we teach everyone to be "safe" on the Internet?
The Incident Handler mentioned drivers in his report, so consider this angle. A mid-2003 story based on Bureau of Transportation Statistics data reports there were "204 million vehicles and 191 million drivers" in the United States. That's about the same population size as our Internet user base.

I am one of those 191 million drivers, and I am not an automobile aficionado. I like to watch Pimp My Ride and Monster Garage, but I have zero interest in making any of those modifications myself. My car is transportation, period.

Consider how my vendor takes care of me, and the role I play in my car's operation. I receive recall notices from the manufacturer that entitle me to return the vehicle for free-of-charge repairs if my safety is affected. My only maintenance involves regular oil changes, fluid changes, and regular wear-and-tear part replacements (tires, belts, etc.) I take the car to the mechanic periodically and I pass my state emissions and safety inspections. For all intents and purposes, my car is an appliance, like my water heater, HVAC, and vacuum cleaner.

The problem with personal computers is that vendors and too many security pundits expect users to be experts. They expect users to have the same level of interest in their PC that an automobile enthusiast has in his or her car. Whose fault is that? I put the blame on the vendors and security pundits who propose "security awareness" and blame users for security problems.

Here's the real wake-up call: 90% or more of the population doesn't care at all about how their PC works. The vast majority treat their PCs like I treat my car. All they want is to check their email, browse the Web, pay their bills, order goodies from online vendors, and play games. A freakishly small proportion of Internet users mod their PC cases, run non-Windows operating systems, overclock and watercool their CPUs, and know what an IP address, port or protocol is.

The bottom line is simple: we can't expect people to care about their computers any more than they care about their cars, or TVs, or microwaves, or other appliances. We need vendors to sell more appliances (like thin clients connected to supportive ISPs) and less general purpose personal computers. The burden must be on the vendor and perhaps the ISP to provide a general-audience-safe appliance, not a ticking time bomb with a five minute fuse.

(Incidentally, I am a vehemently anti-socialist libertarian who believes people should take care of themselves. Using the Handler's "tool" analogy, I don't think vendors should be allowed to sell wood saws without guards, that shatter and disperse metal fragments from poorly-built blades, or that can only be used safely by master craftsmen with years of training.)
Consider a final angle. Why is TiVo so popular? TiVo puts a powerful capability into a simple package. You don't have to be a "TV expert" or receive "training" to record shows with your TiVo or pause and rewind live television. TiVo wins because it doesn't expect its users to go to the lengths necessary to support the personal computer. (Power users can still modify their TiVo if they like.)

I think vendors should take a closer look at the evolution of the automobile and the success of the TiVo, then reconsider the products they sell. Some smart ISP is going to make a lot of money renting or giving away thin client technology paired with subscription-based broadband Internet access. Add in centralized, anywhere-Web-accessible data storage, backed by local USB token storage, and you have an incredible, powerful, centrally-protected and managed computing platform for the 90% of the population that doesn't care. Appliances are the answer for the vast majority who doesn't want to tinker with their technology, and we need vendors to sell and support them.

Selasa, 28 Desember 2004

Review of The Unabridged Pentium 4 Posted

Amazon.com just published my four star review of The Unabridged Pentium 4 : IA32 Processor Genealogy. From the review:

"Page 1 of 'The Unabridged Pentium 4' (TUP4) claims 'there is real value in understanding how the architecture has grown over the years,' where the 'architecture' is the IA-32 register set, instruction set, and software exceptions. If you accept this premise, you will find TUP4 to be a valuable book. If you are looking for detail on the lowest-level of programming on IA-32, you should download Intel's free IA-32 Intel Architecture Software Developer's Manual.

Readers looking for information on IA-32 architecture can first turn to three free books Intel provides in .pdf format: Volume 1: Basic Architecture (448 pp); Volumes 2A (580 pp) & 2B (416 pp): Instruction Set Reference; and Volume 3: System Programming Guide (838 pp), for a total of 2282 pp. Volume 1 describes the basic architecture and programming environment of an IA-32 processor. Volumes 2A & 2B are aimed at application programmers and describe the instruction set of the processor and the opcode structure. Volume 3, for OS engineers and BIOS designers, describes the OS support environment of an IA-32 processor and IA-32 processor compatibility information."

I'll admit to not reading every word of this 1600+ page book. I read a good deal of the non-table material, especially in the foundational 386 material.

I'd like to thank everyone who has voted my Amazon.com reviews "helpful." Since I last mentioned my vote count, almost exactly one year ago, I've added over 500 votes to surpass the 2000 helpful vote count. It's tough for me to "compete" with so-called "reviewers" who cannot possibly read all the books they review. (Some claim to "read" and "review" five technical books per day!) I hope the quality of my reviews and the lack of rambling about topics related to the book at hand demonstrate value to readers.

You can see what I plan to read next on me reading page and potential reading candidates on my Amazon.com Wish List. My reviewing pace will slow as I enter 2005, since I'll spend several months writing another book. Expect to see my review pace pick up again by mid-year.

Minggu, 26 Desember 2004

UNIX History in Detail

I just finished reading the primary two parts of an advocacy piece called Elements of Operating System and Internet History: A FreeBSD Rationale. It appears to be self-published by the author, Bruce Montague. Dru Lavigne made me aware of this work in her blog. The first 64 pages are divided between a 22 page "FreeBSD Executive Summary" and 42 pages on "Unix History, Open Source, and FreeBSD." The third section, which I plan to browse later, consists of 74 pages of various bits of UNIX and Internet trivia.

I found the sections describing UNIX history to be very informative and detailed. The author makes the point that the BSD license supports technological transfer of software from the university to the commercial space, while the GPL was explicitly designed to inhibit technology transfer (pp 14, 18). I was surprised to learn that early hardware vendors encouraged users to write their own software, and in many cases sold user-developed software. Even more shocking was the revelation that the US government, now infected by Microsoft, mandated UNIX for all federal OS purchases in 1986!

The first 64 pages form a coherent whole, but I stopped reading when they ended. The next pages are a collection of trivia. For example, the author claims that the UNIX 'dd' command is so named because its parameters (like 'if=/dev/zero') take the form of IBM JCL 'DD' commands (p 70). These and other tidbits are best read during free moments, perhaps waiting for something to compile on a slow machine.

I think this work could be expanded to a full book if the author explained FreeBSD history beyond the launch of 386BSD. At lot has happened since the 1991 Dr Dobb's Journal articles cited by Montague. I would welcome seeing him describe the launch of FreeBSD, NetBSD, and OpenBSD, as well as more recent innovations like Mac OS X, Darwin, and DragonFly. I would also like to see him analyze the publication of the The 1994 USL-Regents of UCal Settlement Agreement published by Groklaw.

Bruce Montague's work is available through Trifusil Publishing.

FreeBSD Foundation Exceeds Its Goals

I'd like to thank everyone who donated to the FreeBSD Foundation. In less than five days we raised almost $40,000! That's simply amazing. Check back in with the Foundation in January when their Web site is redesigned.

Sabtu, 25 Desember 2004

Review of Introduction to Microprocessors and Microcontrollers Posted

Amazon.com just posted my four star review of Introduction to Microprocessors and Microcontrollers. From the review:

"I reviewed the 1998 edition of this book, 'Introduction to Microprocessors,' (ITM) about a year ago. I gave that book five stars for bringing the internal workings of CPUs within the reach of the computer layman. This new 2004 edition, 'Introduction to Microprocessors and Microcontrollers,' (ITMAM) isn't quite the update I expected, but it's still a great book.

The major differences between ITM and ITMAM involve a few sections. First, material on the Alpha 21164 microprocessor is replaced by a discussion of the AMD Athlon XP. Second, two chapters on microcontrollers are added. Author John Crisp defines a microcontroller as essentially a microprocessor with some ROM and RAM on a single chip. Third, Crisp briefly discusses the innards of popular game consoles in ch 11. Finally, a short discussion of writing assembly language adds another layer to the new edition. "