LWN.net Logo

November CRYPTO-GRAM newsletter

From:  Bruce Schneier <schneier@counterpane.com>
To:  crypto-gram@chaparraltree.com
Subject:  CRYPTO-GRAM, November 15, 2003
Date:  Sat, 15 Nov 2003 10:53:17 -0600

                  CRYPTO-GRAM

               November 15, 2003

               by Bruce Schneier
                Founder and CTO
       Counterpane Internet Security, Inc.
            schneier@counterpane.com
            <http://www.schneier.com>
           <http://www.counterpane.com>


A free monthly newsletter providing summaries, analyses, insights, and 
commentaries on security: computer and otherwise.

Back issues are available at 
<http://www.schneier.com/crypto-gram.html>.  To subscribe, visit 
<http://www.schneier.com/crypto-gram.html> or send a blank message to 
crypto-gram-subscribe@chaparraltree.com.


** *** ***** ******* *********** *************

In this issue:
      Airplane Hackers
      The 9/11 Terrorists' Real Weapon
      Crypto-Gram Reprints
      News
      Counterpane News
      More Beyond Fear Reviews
      The Doghouse: SunnComm Technologies
      The Trojan Defense
      Comments from Readers


** *** ***** ******* *********** *************

               Airplane Hackers



Nathaniel Heatwole is a student at Guilford College.  Several times 
between February 7 and September 15 he tested airline security.  First 
he smuggled box cutters, clay simulating plastic explosives, and bleach 
simulating bomb-making chemicals through security.  Then he hid these 
things in the lavatories of airplanes, along with notes.  And finally, 
he sent an e-mail to the Transportation Security Administration (TSA) 
titled "Information Regarding 6 Recent Security Breaches."

The problem is that the TSA never asked him to test their security.

For years, computer networks have been plagued with hackers breaking 
into systems.  These people are not breaking into systems for 
profit.  They don't commit fraud.  They don't commit theft.  They're 
breaking into systems for the intellectual curiosity.  They're breaking 
into systems for the fun.  They're breaking into systems to see if they 
can.

A traditional and common defense by hackers is that they're breaking 
into systems in order to test their security.  The idea is that the 
only way to learn about computer and network security is to attack 
systems.  Never mind that these hackers don't own the systems they're 
breaking into; that's the excuse.

The Department of Homeland Security and the Transportation Security 
Administration have been attacked by their first hacker.  This wasn't a 
terrorist; he wasn't out to take over planes.  This wasn't even a 
criminal; he didn't try to extort money.  He was a hacker, plain and 
simple.  He wanted to test the efficacy of the security screeners.  He 
wanted to demonstrate that the security measures were, in his eyes, 
inadequate.  He wanted to hack airport security.

Point 1:  This is extraordinarily silly.  Every traveler I know has 
stories of knives being missed by airport security.  No one who flies 
regularly thinks that the TSA is doing a good job of keeping sharp 
objects off airplanes.  Even worse, no one who flies regularly thinks 
that keeping sharp objects off airplanes makes us all safer.  Most of 
what the TSA does is security theater -- window dressing.  It keeps up 
appearances, and maybe (hopefully) makes the terrorists a little less 
sure they can smuggle their weapons aboard airplanes.  Probably not.

Point 2:  This is, and should be treated as, a crime.  "I was only 
testing security" is not a valid defense.  For years, we in the 
computer security field have been hearing that excuse.  Because the 
hacker didn't intend harm, because he just broke into the system and 
just looked around, it wasn't a real crime.  Here's a thought 
experiment for you.  Imagine you return home and find the following 
note attached to your refrigerator: "I was testing the security of back 
doors in the neighborhood and found yours unlocked.  I just looked 
around.   I didn't take anything.  You should fix your lock."  Do you 
feel violated?  Of course you do.

Point 3:  While it is a crime, it isn't a terribly serious 
crime.  Heatwole's stunt was embarrassing, and cost a whole lot of 
money to investigate and clean up.  It could have disrupted the travel 
schedules of lots of people.  But he's not a terrorist.  He didn't do 
this to feed security information to al Qaeda.  His actions didn't 
endanger anyone's lives.  There's a tendency to want to throw the book 
at him because he  embarrassed important government officials, but 
that's not a good enough reason.  We need to discourage this behavior, 
but the punishment needs to fit the crime.  Treat Heatwole as a 
criminal, but not a serious criminal.

Welcome to our world, Department of Homeland Security.  Welcome, 
TSA.  We've been fighting these sorts of people for years.  You're 
going to have better luck prosecuting them, but don't let your anger 
get in the way of reason.


A version of this essay appeared in IEEE Security & Privacy
<http://www.computer.org/security/>

News:
<http://www.cnn.com/2003/US/10/18/airline.scare/index.html>
<http://www.nytimes.com/aponline/national/AP-Planes-Searched.html>
<http://www.salon.com/news/wire/2003/10/20/box_cutters2/>

Other opinions:
<http://www.securityfocus.com/columnists/194>
<http://www.salon.com/tech/col/smith/2003/11/07/askthepilot63/index_np.h 
tml>

Another box cutter was found on an airplane.  No one knows who planted 
this one.
<http://www.cnn.com/2003/US/10/28/airline.boxcutter/index.html>


** *** ***** ******* *********** *************

        The 9/11 Terrorists' Real Weapon



We all know that the new airline security procedures are 
silly.  Baggage screeners taking away pocket knives and box cutters 
doesn't improve airline security, even after 9/11.

People who think otherwise don't understand what allowed the terrorists 
to take over four planes two years ago.  It wasn't a small knife.  It 
wasn't a box cutter.  The critical weapon that the terrorists had was 
surprise.  With surprise they could have taken the planes over with 
their bare hands.  Without surprise they couldn't have taken the planes 
over, even if they had guns.

And surprise has been confiscated on all flights since 9/11.  It 
doesn't matter what weapons any potential new hijackers have; the 
passengers will no longer allow them to take over airplanes.  I don't 
believe that airplane hijacking is a thing of the past, but when the 
next plane gets taken over it will be because a group of hijackers 
figured out a clever new weapon that we haven't thought of, and not 
because they snuck some small pointy objects through security.


** *** ***** ******* *********** *************

              Crypto-Gram Reprints



Crypto-Gram is currently in its sixth year of publication. Back issues 
cover a variety of security-related topics, and can all be found on 
<http://www.schneier.com/crypto-gram.html>. These are a selection of 
articles that appeared in this calendar month in other years.

Full Disclosure:
<http://www.schneier.com/crypto-gram-0111.html#1>

Why Digital Signatures are Not Signatures
<http://www.schneier.com/crypto-gram-0011.html#1>

Programming Satan's Computer:  Why Computers Are Insecure
<http://www.schneier.com/crypto-gram-9911.html#WhyComputersareInsecure>

Elliptic Curve Public-Key Cryptography
<http://www.schneier.com/crypto-gram-9911.html#EllipticCurvePublic-KeyCr 
yptography>

The Future of Fraud:  Three reasons why electronic commerce is different
<http://www.schneier.com/crypto-gram-9811.html#commerce>

Software Copy Protection: Why copy protection does not work
<http://www.schneier.com/crypto-gram-9811.html#copy>


** *** ***** ******* *********** *************

                      News



Paper: "How to Find Hidden Cameras"  Really interesting reading.
<http://www.tentacle.franken.de/papers/hiddencams.pdf>

Good essay on @Stake and the integrity of their actions in firing Dan Geer:
<http://www.eweek.com/article2/0,4149,1335621,00.asp>

A California man's hacking conviction has been overturned on 
appeal.   Another is that it's appalling that it ever happened, 
considering that the victim served over a year of jail time.  It's a 
win for the good guys, but it took far too long.
<http://news.com.com/2100-7348-5092697.html>
<http://www.securityfocus.com/news/7202>

"Identity and Economics" presentation from DefCon:
<http://www.homeport.org/~adam/shostack-bh-vegas-03-final.ppt>

A terrorism operations manual, believed to be used by al Quaeda
<http://www.thesmokinggun.com/archive/jihadmanual.html>
Some interesting parts: Recommended communications are almost all
low-tech.  No support for all those speculations about 
steganography.  The codes and ciphers recommended are very simple 
manual systems.  They're probably not high security.

Turns out that many automobiles have master keys.  Criminals are using 
them to steal cars.
<http://www.philly.com/mld/inquirer/classifieds/automotive/6876246.htm>

Interesting article on casino security.  (Be careful about believing 
details in articles like this.  Most of these stories are planted by 
the casinos to convince the public how good security is at catching 
cheats.  It's actually not nearly that good.)
<http://www.csoonline.com/read/100103/kind.html>

Listening in on terrorist communications.  The problem isn't data 
collection; it's data analysis:
<http://www.msnbc.com/news/982235.asp?cp1=1>

The SANS Top 20 computer security vulnerabilities:
<http://www.sans.org/top20/>

There seems to be no effect from California's security-breach 
disclosure law:
<http://www.securityfocus.com/news/7311>

Excellent analysis of the security of Windows vs. Linux:
<http://www.groklaw.net/article.php?story=20031022014413296>

Turns out that many U.S. driver's license numbers aren't random at all, 
but contain embedded information about your name, etc.  This is an 
interesting site about these numbers.  Vital reading if you're planning 
on getting a fake ID.
<http://www.highprogrammer.com/alan/numbers/>

Bruce Tognazzini on computer security interfaces:
<http://www.asktog.com/columns/058SecurityD'ohlts.html>

Australia seems to be trying to do e-voting properly:
<http://www.wired.com/news/ebiz/0,1272,61045,00.html>

New risks to privacy.  An outsourced medical transcription worker in 
Pakistan (through three levels of contractors) threatened to post 
confidential medical records on the net because she hadn't been paid.
<http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2003/ 
10/22/MNGCO2FN8G1.DTL> or <http://tinyurl.com/rxo2>

Marcus Ranum has a new book: "The Myth of Homeland Security."  Good 
companion volume to my own "Beyond Fear":
<http://www.ranum.com/myth-large-ad.html>

Interesting article on the mind of a suicide terrorist:
<http://www.csmonitor.com/2003/1030/p11s01-legn.html>

Someone deliberately inserted a back door into the Linux kernel.  It 
was discovered and removed before release.  This story shows both the 
security dangers and the benefits of open source software.
<http://www.securityfocus.com/news/7388>

Robert Cringely on identity theft:
<http://www.pbs.org/cringely/pulpit/pulpit20030911.html>
<http://www.pbs.org/cringely/pulpit/pulpit20030918.html>

In a pretty clever PR move, Microsoft is offering a bounty for 
information leading to the arrest and conviction of malware writers.
<http://news.com.com/2102-7355_3-5102110.html>
<http://www.computerworld.com/newsletter/0,4902,86869,00.html>

Good article on cyberincident response planning:
<http://www.csoonline.com/read/050103/bad.html>

Rebuttal to our monoculture paper.  A good essay; these points are 
worth debating:
<http://infosecuritymag.techtarget.com/ss/0,295796,sid6_iss205_art449,00 
.html> or <http://tinyurl.com/v4m2>

Fun with electronic voting.  The MicroVote machines registered 144,000 
votes from 19,000 registered voters.  After much panicking and tracking 
down the bug, the actual number of votes turned out as 5,352. Or maybe 
not; you can't prove it one way or the other.
<http://www.indystar.com/articles/6/091021-1006-009.html>


** *** ***** ******* *********** *************

                Counterpane News




Bruce Schneier will speak at Comdex in Las Vegas this month.  He's 
giving a talk about "Following the Money: Why Security Decisions are so 
Rarely About Security" on Tuesday, 18 November, at 2:00. He will also 
participate in panels on "How much security is enough?" (Mon. 11/17, 
11:00) and "Where Hardware Security Meets Software Security: Weak 
Points and Real Attacks" (Tue. 11/18, 3:30).
<http://www.comdex.com/lasvegas2003/>

Bruce Schneier will be interviewed on WGN Radio Chicago on 25 November 
2003, from 9:00 PM - 11:00 PM.  The show is called "Extension 720."
<http://wgnradio.com/shows/ex720/list.htm>

Counterpane has announced a partnership with Network Associates.
<http://www.counterpane.com/pr-20031020.html>

Counterpane will be exhibiting at the Inaugural European Forum On Cyber
Security in the Financial Services Sector Executive Summit
December 15-16, 2003 at the ExCel Conference Centre, London, UK.
<http://www.imn.org/a560/cpw>


** *** ***** ******* *********** *************

            More "Beyond Fear" Reviews



My latest book continues to get great reviews.  I'm especially pleased 
to see the book reviewed in non-computer publications like "The 
Economist."  To those who have purchased the book already, thank you 
very much for helping make it a success.  I hope that I am having some 
effect on the sorry state of security these days.


"[Schneier] is one of the world's leading experts on computer security, 
and arguably the most articulate.... Surprisingly entertaining, with 
many examples of security systems, both good and bad, drawn from the 
natural world, military history and other fields.... Beyond Fear 
deserves to be widely read."
      --The Economist

Economist review:
<http://www.economist.com/books/displayStory.cfm?story_id=2137411>
You can also find the review here:
<http://groups.google.com/groups?selm=2jgvqv09mhle5bjq1453an0c4tadmn2d49 
%404ax.com> or <http://tinyurl.com/v4ly>

Other reviews:
<http://seattletimes.nwsource.com/html/books/2001762147_security12.html>
<http://www.infowarrior.org/rants/101403.txt>
<http://www.techsoc.com/beyondfear.htm>

Book's website:
<http://www.schneier.com/bf.html>


** *** ***** ******* *********** *************

      The Doghouse: SunnComm Technologies



The home page of this company says "lightyears beyond 
encryption."  Actually, it's an anti-copying technology for music 
CDs.  This technology is being used to protect the new CD by BMG soul 
artist Anthony Hamilton.

It's actually not worth fighting the pop-ups and the Flash and the 
annoying website to learn about how the system works or how you can 
purchase it.  It turns out you can defeat this system by holding down 
the shift key when you insert a music CD into your computer.  This 
disables autorun, so the SunnComm software never gets executed.

Unfortunately, SunnComm has some more tricks up its sleeve.  They're 
suing John Halderman, the Princeton PhD student who first noticed 
this.  That'll make the system secure again; of course it will.

Website:
<http://www.sunncomm.com/>

News articles:
<http://news.com.com/2100-1025-5087875.html>
<http://www.msnbc.com/news/978433.asp?0bl=-0>


** *** ***** ******* *********** *************

              The Trojan Defense



Aaron Caffrey is a UK teenager accused of launching a distributed 
denial-of-service attack against an independent contractor for the Port 
of Houston, Texas.  Last month he was acquitted on all charges in a UK 
court.  Caffrey's defense was that while the attack did come from 
Caffrey's computer, it was the work of someone who had installed a 
Trojan horse program on the machine and altered his computer's log files.

I have read several opinions on this case.  Some believe that the 
"Trojan defense" sets a dangerous precedent, and that computer 
criminals will claim it every time.   I believe that it sets a very 
good precedent, and will force prosecutors to do more than show that a 
particular computer was involved in a crime.

The hardest part of computer security is the piece between the computer 
and the user.  The hardest part of encryption is maintaining the 
security of the data when it's being entered into the keyboard and when 
it's being displayed on the screen.  The hardest part of digital 
signatures is proving that the text signed is the same text that the 
user viewed.  And the hardest part of computer forensics is knowing who 
is sitting in front of a particular computer at any time.

Just because a particular computer was involved in an attack doesn't 
mean that the computer's owner was involved.  Maybe, as Aaron Caffrey 
alleged, the computer was being controlled by someone else.  We know 
that many hackers control a series of computers in an attempt to 
disguise their tracks.  Maybe, as is being alleged in another case, the 
computer was in a public space and someone else used it to commit the 
crime.  Maybe the user was duped into pushing certain keys or clicking 
on certain mouse buttons, and had no idea what he was really doing.

Also in the U.K., two men accused of downloading child pornography 
convinced the court that a Trojan on their computer did it and not them.

This defense makes it harder for the prosecution, but that's not a bad 
thing.  The barrier should be high to convict someone of a crime.  If 
the prosecutor can prove that a particular computer was involved but 
can't prove that a particular person was involved, that sounds like 
insufficient evidence to convict.  I want the prosecutor to be able to 
prove that the person committed the crime.

By allowing this defense we're permitting some guilty people to go 
free, but we're also protecting the innocent.  I don't think society 
would be well-served by denying this defense and thus offering people a 
sure-fire way to frame someone for a computer crime.


<http://www.forbes.com/markets/newswire/2003/10/27/rtr1124430.html>
<http://news.com.com/2102-7349_3-5092781.html >
<http://news.bbc.co.uk/1/hi/technology/3202116.stm>
<http://www.theregister.co.uk/content/55/33460.html>
<http://www.theregister.co.uk/content/55/33636.html>


** *** ***** ******* *********** *************

               Comments from Readers



From: Russell Nelson <nelson@crynwr.com>
Subject: Re: Hats in Banks

 > A New York detective was once asked whether pickpockets in
 > Manhattan dressed in suits and ties to facilitate their crimes
 > subsequent escape.  He responded by saying that in twenty years
 > he had never arrested even one pickpocket in a tie.

Do you mean this as evidence to bolster your point or to counter 
it?  It seems to me that if he never arrested even one pickpocket in a 
tie, that would be very good evidence that pickpockets wearing ties 
escape arrest.



From: Troy Davis <troy@nack.net>
Subject: Identity Theft and On-line Brokerage Accounts

 > A 19-year-old used a fake website to lure victims into downloading
 > his Trojaned software, and then captured their stock account
 > information and traded stocks in their name.
 >
 > The scary thing is how effective this attack could be. This guy
 > was pretty stupid, but imagine for a minute what the results would
 > be if a smart attacker planned his attack better. He could make
 >  millions and be out of the country before anyone knew.

Though online brokerage users are obvious targets, the grand finale is 
customers of more traditional banks who have intentionally enabled 
Internet access to one account for online trading.  Enabling one 
account often automatically allows Internet transactions for all 
accounts held at the same bank, via the same single password.

As a result, full Internet access to all bank accounts is frighteningly 
common even among casual users.  Does Joe Average need the ability to 
move $50,000 without a phone call, let alone a visit to the bank?  Not 
only do I not need the ability, I don't want it.

Pros wouldn't bother with Trojan horses or the Internet.  Select mid- 
or late-career professionals with substantial salaries, basic end-user 
technology experience, and verifiable factors associated with active 
Internet use (school-age kids, job requiring telecommuting).

Pick one of a dozen legitimate physical access methods: law firm 
cleaning crew, downtown condo maintenance staff.  Retrieve the 
keystroke logger a few weeks later.

As you mention, the attacker would be out of the country or off the 
radar (open WAP), not only before anyone knew, but before the first 
transaction was initiated.  The online equivalent of ATM transaction 
velocity limits -- three $300 withdrawals in one day and your card is 
denied -- is rarer than we'd like to believe.


From: Ton van der Putte <Ton.vanderPutte@atosorigin.com>
Subject: Hacking Fingerprint Readers

Last year in the June issue of CRYPTO-GRAM you made a reference to our 
article "Don't get your fingers burned".  In the article we describe 
two methods to duplicate fingerprints.  One method assumes co-operation 
(somebody "lends" his finger to make a duplicate), while in the other 
method a lifted latent fingerprint is duplicated by means of a 
photo/chemical process.  With these dummy fingerprints we have been 
able to fool all fingerprint sensors we have tested in our lab and on 
exhibitions (about 20 different brands).  I started with these 
experiments in the early nineties, so more than 10 years ago.

Last week we were invited by the BBC to come to London for in interview 
about duplicating fingerprints.  The reason was that the British 
Administration intends to add biometrics to the new British identity 
card, one of the options is fingerprint biometrics.  The programme, 
"Kenyon Confronts" has aired on Wednesday October 29th and is (for a 
short period of time) available for on-line viewing at the BBC site.

Since my first experiments were dated ten years back, I decided to redo 
my experiments.  I knew it would be easier to duplicate fingerprints 
with all the materials and equipment available today, but the results 
even amazed me.  To give you an idea, ten years ago to make a duplicate 
of a fingerprint with co-operation took me 2 to 3 hours and for an 
optimum result I used materials used by dental technicians.  Nowadays I 
use materials you can buy in a do-it-yourself shop and the total 
material costs are about $10 (enough for about 20 dummy fingers).

The time it takes to make a perfect duplicate is about 15 minutes (with 
special material it can be reduced to less than 10 minutes).  To make a 
duplicate of a lifted fingerprint took me several days in 1992 and I 
had to do a lot of experiments to find the right 
process/technique.  Now it takes me half an hour and the material costs 
are $20 (also sufficient for about 20 duplicates), the only equipment 
you need is a digital camera and an UV lamp.  Not only do I now make 
the duplicates in a fraction of the time, but also the quality is better.

The reason for writing you all this is the following.  Although, most 
of the fingerprint manufacturers still ignore that there is a problem 
or claim to have solved it, some are willing to admit, but use the 
argument that it is very difficult and expensive to duplicate 
fingerprints and that it can only be done by highly skilled 
professionals.  In the first place I think this is not a very strong 
argument, second I admit I am a professional, but now the average 
do-it-yourselfer is able to achieve perfect results and requires only 
limited means and skills.

So it is our opinion, that as long as the manufacturers of fingerprint 
equipment do not solve the live detection problem (i.e. detect the 
difference between a live finger and a dummy), biometric fingerprint 
sensors should not be used in combination with identity cards, or in 
medium to high security applications.  In fact, we even believe that 
identity cards with fingerprint biometrics are in fact weaker than 
cards without it.  The following two examples may illustrate this 
statement.

1.  Suppose, because of the fingerprint check, there is no longer 
visual identification by an official or a controller.  When the 
fingerprint matches with the template in the card then access is 
granted if it is a valid card (not on the blacklist).  In that case 
someone who's own card is on the blacklist, can buy a valid identity 
card with matching dummy fingerprint (only 15 minutes work) and still 
get access without anyone noticing this.

2.  Another example: Suppose there still is visual identification and 
only in case of doubt--the look-alike problem with identity cards--the 
fingerprint will be checked.  When the photo on the identity card and 
the person do not really match and the official asks for fingerprint 
verification, most likely the positive result of the fingerprint scan 
will prevail.  That is, the "OK" from the technical fingerprint system 
will remove any (legitimate) doubt.

It is our opinion that especially the combination of identity cards and 
biometric fingerprint sensors results in risks of which not many people 
are aware.


** *** ***** ******* *********** *************

CRYPTO-GRAM is a free monthly newsletter providing summaries, analyses, 
insights, and commentaries on security: computer and otherwise.  Back 
issues are available on <http://www.schneier.com/crypto-gram.html>.

To subscribe, visit <http://www.schneier.com/crypto-gram.html> or send 
a blank message to crypto-gram-subscribe@chaparraltree.com.  To 
unsubscribe, visit <http://www.schneier.com/crypto-gram-faq.html>.

Comments on CRYPTO-GRAM should be sent to 
schneier@counterpane.com.  Permission to print comments is assumed 
unless otherwise stated.  Comments may be edited for length and clarity.

Please feel free to forward CRYPTO-GRAM to colleagues and friends who 
will find it valuable.  Permission is granted to reprint CRYPTO-GRAM, 
as long as it is reprinted in its entirety.

CRYPTO-GRAM is written by Bruce Schneier.  Schneier is the author of 
the best sellers "Beyond Fear," "Secrets and Lies," and "Applied 
Cryptography,"  and an inventor of the Blowfish, Twofish, 
algorithms.  He is founder and CTO of Counterpane Internet Security 
Inc., and is a member of the Advisory Board of the Electronic Privacy 
Information Center (EPIC).  He is a frequent writer and lecturer on 
security topics.  See <http://www.schneier.com>.

Counterpane Internet Security, Inc. is the world leader in Managed 
Security Monitoring.  Counterpane's expert security analysts protect 
networks for Fortune 1000 companies world-wide.  See 
<http://www.counterpane.com>.

Copyright (c) 2003 by Bruce Schneier.



(Log in to post comments)

pocket knives and box cutters : doesn't improve airline security, even after 9/11.

Posted Nov 16, 2003 17:17 UTC (Sun) by neoprene (guest, #8520) [Link]

"People who think otherwise don't understand what allowed the terrorists
to take over four planes two years ago. It wasn't a small knife. It
wasn't a box cutter. The critical weapon that the terrorists had was
surprise"


Surprise was clearly a _part_ of the recipe for taking Control of the Airplane.
Deadly force along with the commonly held beleif of the average Joe (that letting hijackers do want they want will lead to safety for the rest of the people and that hijackers won't use an Airplane like a Kamikaze missile) is what gave the hijackers Control of the Airplane. Once those notions were dismissed, the passengers on airplane no.4 took control back from the hijackers. As everyone should know by now the reason for plane no.4's "failure" was the willingness of the passengers to sacrifice their lifes to save others, likely a doctrinal surprise to the hijackers. The plane crashed perhaps because there were no pilots left to fly the plane or automatic systems to keep the plane flying. I bet a few people wished they'd brought parachutes. Timely media coverage together with use of cell phones was also part of why their plan failed on No.4.
Will hijackers learn from these mistakes? I should think so.
Airplanes full of passengers, cabin crews, and cell-phones would now be identified as obstacles. One could venture to guess future hijackers will avoid repeating those mistakes. And of whatever airport security is looking for, bring something/soembody they are not looking for. Perhaps avoid passenger airliners altogether.

The real reason for wars and conflicts are the clashing of ideas and financial/economical interests. Lack of understanding and respect for other people/nations could lead to repetition of history. Solving your "problems" with war is a very risky business and could lead to very undesirable consequences and should only be undertaken when other avenues have been exhausted, i.e. diplomacy, trade negociations, treaties, foregn aid, learning languages and cultures, propaganda, time and patience, et cetera have failed.

Winning the War is difficult, winning the Peace is much harder, maybe impossible.


Monoculture and security

Posted Nov 16, 2003 21:00 UTC (Sun) by dkite (subscriber, #4577) [Link]

Pete Lindstrom makes a good point, that if only half the desktops were Windows, then that
would bring the number of vulnerable desktops down to 300 million. And having government
control of the market wouldn't fix anything.

But what he misses are the costs of standardization. It is not so much a monoculture of
software, it is a monoculture of development process and focus. Security hasn't been an issue
for Microsoft until now. Unfortunately they own 95% of the desktop market. So all of us are
affected.

With a diverse culture of desktop (and other) software, each vendor would compete for
customers. The customers would be able to choose between any number of viable alternatives.
That is not the case at all right now, even within the Window's market. Is there a vibrant market
in email clients? Everyone needs one, there should be. When was the ILoveYou virus? Two,
three years ago? We all noted a stampede away from Microsoft products, umm, didn't we? To
what? Microsoft hasn't needed to respond to security threats because there was no
business threat. Three years ago, what else could someone use except Windows? Now there is
OSX, and the various linux desktops are very close to competitive. All of a sudden Microsoft's
focus is on security? Gee, what a coincidence.

To quote "To suggest that the risk is too great for a standard desktop is to suggest that the
20-year effort to standardize systems and support processes was a bad idea."

Yes it was a bad idea. Most of the issues in the article are worrying about software business
plans, rather than whether the stuff works or not. As Bruce Schneier makes clear again and
again, security is a state of mind rather than a bunch of hardware or software. Finally with some
competition in the marketplace, the state of mind is changing. Compare the desktop market
with the server market. IIS is insecure? Use Apache, Microsoft rewrites IIS.

If anything, this article showed me that it is the whole industry, customers and vendors, that
created the problem. Most everyone chose to go with the winner, and inevitably, we all lose.

What is funny about this whole thing is that the competition, the more secure software, the
answer to the dangerous monoculture has come from a bunch of guys writing stuff that they
like. For free. Could it be that some of the strong reactions in this debate come partly from
humiliation?

Derek

Monoculture and security

Posted Nov 17, 2003 12:55 UTC (Mon) by rknop (guest, #66) [Link]

The boat that has been missed on a lot of standardization is that it is *protocols and formats* that should be standardized, not specific systems and pieces of software.

Once upon a time, this was understood on the Internet. That's why we had things like ASCII, TCP/IP, SMTP, FTP, and (at least the pure form of) HTML. Open standards which anybody could implement, and indeed which a large number of very different systems did implement, and even different packages on the same system. There was no worry about anybody being able to receive E-mail from anybody else, anybody being able to connect to the network, or anybody being able to view a given web page, because they were all open standard formats which anybody could implement, and which had been diversely implemented.

With the desktop, though, we got this idea at compatability required monoclulture. That havning a well-defined format or protocol which anybody who implemented correctly could play with wasn't good enough, but rather that everybody had to be running exactly Microsoft Word, or exactly Microsoft Internet Explorer. I suspect Microsoft understood this full well, because it's pretty obvious to them that "standard as product" rather than "standard as protocol" was hugely in favor of somebody who believed that they could come out as "the winner" (as Microsoft has). But all the rest of us suffer.

If we could really get back to the idea of standards as protocol rather than standards as packages--- which requies open standards rather than closed, proprietary standards!--- then the incentives forcing us towards monoculture would evaporate. Microsoft would suffer, but all the rest of us would benefit greatly, including those who are currently Microsoft's customers.

And, yeah, if a fundamental flaw is identified in the protocol, then we all suffer the security problems of a monoculture. But, except for SPAM, all of the most serious security problems we have faced have been problems with packages and specific implementations (which may happen to be dominantly widespread) rather than a fundamental flaw in the underpinning protocol.

-Rob

Monoculture and security

Posted Nov 18, 2003 1:03 UTC (Tue) by XERC (guest, #14626) [Link]

A small quote from Micro$oft's private survay:

OSS projects have been able to gain a foothold in many server applications because of the wide utility of highly commoditized, simple protocols. By extending these protocols and developing new protocols, we can deny OSS projects entry into the market.

It's part of the 1. Halloween document.

Copyright © 2003, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds