- Don't pick a fight with an old man. If he is too old to fight, he'll just kill you.
- If you find yourself in a fair fight, your tactics suck.
- I carry a gun because a cop is too heavy.
- When seconds count, the cops are just minutes away.
- A reporter did a human-interest piece on the Texas Rangers. The reporter recognized the Colt Model 1911 the Ranger was carrying and asked him 'Why do you carry a 45?' The Ranger responded, 'Because they don't make a 46.'
- The old sheriff was attending an awards dinner when a lady commented on his wearing his sidearm 'Sheriff, I see you have your pistol. Are you expecting trouble?' 'No Ma'am. If I were expecting trouble, I would have brought my shotgun.'
- Beware the man who only carries one gun. HE PROBABLY KNOWS HOW TO USE IT!!!
Also this:
I was once asked by a lady visiting if I had a gun in the house. I said I did. She said 'Well I certainly hope it isn't loaded!' To which I said, of course it is loaded, it can't work without bullets!' She then asked, 'Are you that afraid of someone evil coming into your house?' My reply was, “No not at all I am not afraid of the house catching fire either, but I have fire extinguishers around, and they are all loaded too”.
Wednesday, July 28, 2010
Self Defense Wisdom...
Via my lovely wife (click to enlarge the photo at right and read the enscription on the end of the barrel):
Labels:
Humor
Uh Oh...
Another week, another Google Unemployment Index report. This really looks bad – the number of unemployment-related queries has almost doubled in the past few weeks. I'm still not entirely sure how this report correlates to our economy's health, but it's really hard to see any way for this to be good news...
Labels:
Economy,
Unemployment
Room-Temperature Superconductor?
If this pans out, it could enable another technological transformation of the world... Details.
Labels:
Science
One Ring to Rule Them All...
Update: Bruce Schneier weighs in.
Original post:
Several readers (and a colleague) wrote to ask me about this story (and the many others like it) that hit the web in the past few days. The stories don't have much detail beyond the fact that somehow seven people were chosen to hold the keys that it would take to “restart the Internet” in the event of a disaster. The more geekly folks out there know that the Internet is a highly distributed system with no central point of control, so the notion of restarting the Internet doesn't, on the face of it, make much sense. So what the hell is this story talking about?
Well, first of all, there's a bit of overdramatization in the story. Actually, a whole lot of overdramatization. But there's also a grain of truth to it.
To understand what's going on here, you first need to understand a tiny bit about the Domain Name System (DNS). Even though you may not realize it, you're probably using it every day. For example, if you typed “www.jamulblog.com” to read this blog, your web browser submits that name to DNS to look up the address (“74.125.47.121” in this case) of my blog's web server. Then your web browser contacts that web server to get the actual blog posts. So DNS is sort of like a phone book in which your web browser can look up names to find the address – which, like a phone number, it can use to contact a web server directly.
DNS has a trick that your phone book doesn't, however. If you ask for a name that your local DNS server (probably run by your Internet service provider) doesn't know, that DNS server will ask a “root server” for the address of the “authoritative” DNS server that will know that name. For example, if you typed in my blog's address and your local DNS server had never heard of it before, your local DNS server would ask a root DNS server for the address of the authoritative DNS server for “jamulblog.com”. Then it would ask that DNS server for the address of “www.jamulblog.com”. This is called a recursive query. I've glossed over all sorts of details, but the basic idea of a recursive query is key to understanding this “restart the Internet” story. With me?
Recently (July 15th) the root DNS servers implemented DNS Security Extensions (DNSSEC). These security extensions are a very complex, designed-by-gigantic-committee protocol designed to allow DNS clients (such as your web browser) to verify that the DNS responses it receives (those addresses) are, in fact, authorized (not forged) responses. Without these extensions, it's relatively easy for a program to forge DNS responses – so that you type in “www.bony.com” but instead of getting the Bank of New York, you get some site that looks like the BONY site but is actually just trying to capture your password. Forging DNS responses is bad, and DNSSEC is designed to prevent it. But (and this is where the hype comes in) DNSSEC is optional on the client (like your web browser). You can turn it off.
The way that DNS clients can verify that responses are authorized is to follow a chain of authority all the way back to the root DNS server. Ignoring the details of how this works, it all depends on a Secret Master Key (SMK) that's held on the root DNS servers. This SMK is just a (very) big number, with something like 1000 digits in it. Without the SMK, the root servers could not generate verifiably authentic responses, and neither could any other DNS servers. That means that without the SMK, no DNS clients (even your web browser) that have implemented DNSSEC could verify the responses. You'd type in my blog address and you'd get an error message instead of my blog. The internet would be broken!
Well, not quite. It's simple enough to turn off the DNS security on DNS clients. It's a bit more work for intermediate DNS servers (like the one your Internet service provider runs), but not really very much more work. In addition, even if DNSSEC was completely broken, there are plenty of DNS servers that don't participate in DNSSEC at all (such as Google's DNS servers, for example), and these would keep right on working. Nevertheless, if the SMK were lost, the result would be (temporary) service interruption for millions of systems. Plus it would be a really big pain in the patoot.
How could the SMK be lost? There are lots of scenarios, all of them involving disasters that wiped out all of the root DNS servers at the same time. Pick your poison: earthquake, meteorite strike, giant tornadoes, terrorists, nuclear war, coordinated copper-eating ants. None of these are very likely to wipe all the root DNS servers out, but theoretically it could happen.
So there's an SMK backup and a recovery procedure, part of the overall DNSSEC security procedures. The security requirements make backup tricky. You don't want to have a complete copy of the SMK available to any one person, because that one person could then do something bad, like sell the SMK to al Qaeda or the Russian Mafia. The backup needs to be really secure. So the approach they took (see diagram at right, and associated presentation for details) was to split up the SMK into 7 pieces, any 5 of which could be used to recreate the whole thing. These 7 pieces have been deposited into 7 safe deposit boxes. The 7 keys to the safe deposit boxes have been entrusted to 7 individual people (hopefully trustworthy folks!).
In the event of a successful coordinated copper-eating ant attack that wiped out all the root DNS servers, these seven people would be called. They'd first travel to their safe deposit box, use the key they've been entrusted with to open it, and grab their piece of the SMK. Then they'd travel to a secure location. When at least five of these folks had arrived at that secure location, technicians could piece together the SMK from the fragments each carried – and the root DNS servers would once again be able to authenticate their responses, your web browser would be happy, sunshine would break through the clouds, and there would be no more hunger. I made up the last bit...
Original post:
Several readers (and a colleague) wrote to ask me about this story (and the many others like it) that hit the web in the past few days. The stories don't have much detail beyond the fact that somehow seven people were chosen to hold the keys that it would take to “restart the Internet” in the event of a disaster. The more geekly folks out there know that the Internet is a highly distributed system with no central point of control, so the notion of restarting the Internet doesn't, on the face of it, make much sense. So what the hell is this story talking about?
Well, first of all, there's a bit of overdramatization in the story. Actually, a whole lot of overdramatization. But there's also a grain of truth to it.
To understand what's going on here, you first need to understand a tiny bit about the Domain Name System (DNS). Even though you may not realize it, you're probably using it every day. For example, if you typed “www.jamulblog.com” to read this blog, your web browser submits that name to DNS to look up the address (“74.125.47.121” in this case) of my blog's web server. Then your web browser contacts that web server to get the actual blog posts. So DNS is sort of like a phone book in which your web browser can look up names to find the address – which, like a phone number, it can use to contact a web server directly.
DNS has a trick that your phone book doesn't, however. If you ask for a name that your local DNS server (probably run by your Internet service provider) doesn't know, that DNS server will ask a “root server” for the address of the “authoritative” DNS server that will know that name. For example, if you typed in my blog's address and your local DNS server had never heard of it before, your local DNS server would ask a root DNS server for the address of the authoritative DNS server for “jamulblog.com”. Then it would ask that DNS server for the address of “www.jamulblog.com”. This is called a recursive query. I've glossed over all sorts of details, but the basic idea of a recursive query is key to understanding this “restart the Internet” story. With me?
Recently (July 15th) the root DNS servers implemented DNS Security Extensions (DNSSEC). These security extensions are a very complex, designed-by-gigantic-committee protocol designed to allow DNS clients (such as your web browser) to verify that the DNS responses it receives (those addresses) are, in fact, authorized (not forged) responses. Without these extensions, it's relatively easy for a program to forge DNS responses – so that you type in “www.bony.com” but instead of getting the Bank of New York, you get some site that looks like the BONY site but is actually just trying to capture your password. Forging DNS responses is bad, and DNSSEC is designed to prevent it. But (and this is where the hype comes in) DNSSEC is optional on the client (like your web browser). You can turn it off.
The way that DNS clients can verify that responses are authorized is to follow a chain of authority all the way back to the root DNS server. Ignoring the details of how this works, it all depends on a Secret Master Key (SMK) that's held on the root DNS servers. This SMK is just a (very) big number, with something like 1000 digits in it. Without the SMK, the root servers could not generate verifiably authentic responses, and neither could any other DNS servers. That means that without the SMK, no DNS clients (even your web browser) that have implemented DNSSEC could verify the responses. You'd type in my blog address and you'd get an error message instead of my blog. The internet would be broken!
Well, not quite. It's simple enough to turn off the DNS security on DNS clients. It's a bit more work for intermediate DNS servers (like the one your Internet service provider runs), but not really very much more work. In addition, even if DNSSEC was completely broken, there are plenty of DNS servers that don't participate in DNSSEC at all (such as Google's DNS servers, for example), and these would keep right on working. Nevertheless, if the SMK were lost, the result would be (temporary) service interruption for millions of systems. Plus it would be a really big pain in the patoot.
How could the SMK be lost? There are lots of scenarios, all of them involving disasters that wiped out all of the root DNS servers at the same time. Pick your poison: earthquake, meteorite strike, giant tornadoes, terrorists, nuclear war, coordinated copper-eating ants. None of these are very likely to wipe all the root DNS servers out, but theoretically it could happen.
So there's an SMK backup and a recovery procedure, part of the overall DNSSEC security procedures. The security requirements make backup tricky. You don't want to have a complete copy of the SMK available to any one person, because that one person could then do something bad, like sell the SMK to al Qaeda or the Russian Mafia. The backup needs to be really secure. So the approach they took (see diagram at right, and associated presentation for details) was to split up the SMK into 7 pieces, any 5 of which could be used to recreate the whole thing. These 7 pieces have been deposited into 7 safe deposit boxes. The 7 keys to the safe deposit boxes have been entrusted to 7 individual people (hopefully trustworthy folks!).
In the event of a successful coordinated copper-eating ant attack that wiped out all the root DNS servers, these seven people would be called. They'd first travel to their safe deposit box, use the key they've been entrusted with to open it, and grab their piece of the SMK. Then they'd travel to a secure location. When at least five of these folks had arrived at that secure location, technicians could piece together the SMK from the fragments each carried – and the root DNS servers would once again be able to authenticate their responses, your web browser would be happy, sunshine would break through the clouds, and there would be no more hunger. I made up the last bit...
Labels:
Internet,
Technology
Tuesday, July 27, 2010
Holy Meteorite, Batman!
The world is a really big place. Just north of the Egyptian border with Sudan, researches recently discovered a 100 foot diameter meteor crater with 10 foot high walls. They think it's been there for roughly 1000 years, which is very, very young for such a large crater. So young, in fact, that the ejecta rays are still visible on the Google Earth photo (erosion and other forces usually wipe these out quite quickly).

The researchers who found this crater actually used Google Earth photos to locate it. Then they went on an expedition to actually look at it in person. That must have been fun!
If you'd like to look at this yourself on Googe Earth, the coordinates are: 26º05′15″E 22º01′05″N.
Click to enlarge either of these images...

The researchers who found this crater actually used Google Earth photos to locate it. Then they went on an expedition to actually look at it in person. That must have been fun!
If you'd like to look at this yourself on Googe Earth, the coordinates are: 26º05′15″E 22º01′05″N.
Click to enlarge either of these images...
Monday, July 26, 2010
Cow Flop Fungi...
Cow flop fungi, officially (but less descriptively) known as Pilobolus crystalinus. Via Botany Photo of the Day. Click for a larger view...
Labels:
Botany
Vive la Changement!
Poster of the day, via my lovely wife. Click to enlarge. Put down your morning drink first, though...
Chaparral Morning...
Out with the dogs again at 3:30 am. A beautiful, perfect full moon was high in the southwestern sky. It's bright light lit up our whole valley; after my eyes accommodated, I could easily see color in my yard (including that red stripe on our house!), and details in the valley. To the west and northwest, the morning's marine layer created a fuzz on the horizon. Jupiter was high and bright in the east, and the Pleiades were just barely visible in the northeast (they were almost washed out by the bright moonlight).
The dogs were all noses down – we must have had a visitor again last night. A couple of them (couldn't tell which ones) let out the occasional grumpy growl. They were not happy about the intruders in their yard!
The dogs were all noses down – we must have had a visitor again last night. A couple of them (couldn't tell which ones) let out the occasional grumpy growl. They were not happy about the intruders in their yard!
Labels:
Home
Sunday, July 25, 2010
Life's Lessons...
My cousin Mike D. sends along this parable:
A mouse looked through the crack in the wall to see the farmer and his wife open a package. "What food might this contain?" the mouse wondered - but he was devastated to discover it was a mousetrap.
Retreating to the farmyard, the mouse proclaimed the warning: "There is a mousetrap in the house! There is a mousetrap in the house!"
The chicken clucked and scratched, raised her head and said, "Mr. Mouse, I can tell this is a grave concern to you, but it is of no consequence to me. I cannot be bothered by it."
The mouse turned to the pig and told him, "There is a mousetrap in the house! There is a mousetrap in the house!" The pig sympathized, but said, "I am so very sorry, Mr. Mouse, but there is nothing I can do about it but pray. Be assured you are in my prayers."
The mouse turned to the cow and said "There is a mousetrap in the house! There is a mousetrap in the house!" The cow said, "Wow, Mr. Mouse. I'm sorry for you, but it's no skin off my nose."
So, the mouse returned to the house, head down and dejected, to face the farmer's mousetrap alone. That very night a sound was heard throughout the house -- like the sound of a mousetrap catching its prey. The farmer's wife rushed to see what was caught. In the darkness, she did not see it was a venomous snake whose tail the trap had caught. The snake bit the farmer's wife. The farmer rushed her to the hospital, and she returned home with a fever.
Everyone knows you treat a fever with fresh chicken soup, so the farmer took his hatchet to the farmyard for the soup's main ingredient. But his wife's sickness continued, so friends and neighbors came to sit with her around the clock. To feed them, the farmer butchered the pig.
The farmer's wife did not get well; she died. So many people came for her funeral, the farmer had the cow slaughtered to provide enough meat for all of them.
The mouse looked upon it all from his crack in the wall with great sadness. So, the next time you hear someone is facing a problem and think it doesn't concern you, remember -- when one of us is threatened, we are all at risk. We are all involved in this journey called life. We must keep an eye out for one another and make an extra effort to encourage one another.
Labels:
Philosophy
Send In the Old Farts!
Via my lovely wife, who says she agrees with this 100%:
New Direction for any war: Send Service Vets over 60!My wife agrees with this? I'm going to be 60 in a few years. Hmmm...
I am over 60 and the Armed Forces thinks I'm too old to track down terrorists. You can't be older than 42 to join the military. They've got the whole thing ass-backwards. Instead of sending 18-year olds off to fight, they ought to take us old guys. You shouldn't be able to join a military unit until you're at least 35.
For starters, researchers say 18-year-olds think about sex every 10 seconds. Old guys only think about sex a couple of times a day, leaving us more than 28,000 additional seconds per day to concentrate on the enemy.
Young guys haven't lived long enough to be cranky, and a cranky soldier is a dangerous soldier. 'My back hurts! I can't sleep, I'm tired and hungry.' We are impatient and maybe letting us kill some asshole that desperately deserves it will make us feel better and shut us up for awhile..
An 18-year-old doesn't even like to get up before 10am. Old guys always get up early to pee, so what the hell. Besides, like I said, I'm tired and can't sleep and since I'm already up, I may as well be up killing some fanatical son-of-a-bitch.
If captured we couldn't spill the beans because we'd forget where we put them. In fact, name, rank, and serial number would be a real brainteaser.
Boot camp would be easier for old guys.. We're used to getting screamed and yelled at and we're used to soft food. We've also developed an appreciation for guns. We've been using them for years as an excuse to get out of the house, away from the screaming and yelling.
They could lighten up on the obstacle course however... I've been in combat and never saw a single 20-foot wall with rope hanging over the side, nor did I ever do any pushups after completing basic training.
Actually, the running part is kind of a waste of energy, too... I've never seen anyone outrun a bullet.
An 18-year-old has the whole world ahead of him. He's still learning to shave, to start a conversation with a pretty girl. He still hasn't figured out that a baseball cap has a brim to shade his eyes, not the back of his head.
These are all great reasons to keep our kids at home to learn a little more about life before sending them off into harm's way.
Let us old guys track down those dirty rotten coward terrorists. The last thing an enemy would want to see is a couple million pissed off old farts with attitudes and automatic weapons, who know that their best years are already behind them.
HEY!! How about recruiting Women over 50...in menopause!!! You think MEN have attitudes?? Oh my God!!! Put them on border patrol. They'll have it secured the first night!
Update: The New Roof...
The project is moving right along. Chris (the contractor) and his two boys were here yesterday (Saturday) to work on getting the roof in a waterproof condition. He's worried that we'll have some rain before he gets it “buttoned up”, but that seems pretty unlikely this time of year. At far right, in a carefully positioned shot, you can see what the red roof will look like when it's all done. The photo immediately to the right shows what the roof really looks like right now – covered with the high-tech underlayment that's making the roof waterproof now, and that provides a good base for the metal roof to lie on.The metal roofing parts are being made right now, at the roofing manufacturer. They're going to take between two and four weeks longer to be finished, so once the fascia, underlayment, and soffits are all installed there will be a hiatus in the project until the materials are fabricated.
This short video gives you a tour of our roof in its current condition. Pardon the low quality; it was shot with a Blackberry!
Los Zetas Captures Ranches in Texas...
The open-borders crowd has some thinking to do. Mexican nationals – members of the much-feared “Los Zetas” drug cartel – have captured at least two American ranches in Texas. The ranchers are ok; apparently they escaped.
Personally, I think our response should be carefully nuanced, using all the appropriate tools at our disposal. That would include Hellfire missiles, bunker-buster bombs, C-130 gunships, artillery, tanks, guns, U.S. Marines, and anything else we've got that will kill invading scum. We need to send a clear message: if you take or harm our citizens or their property, then you die. Quickly. Without hanky-twisting, prior notification, or preliminary negotiation.
Something tells me that this administration's response will somewhat less effective than a Marine detachment...
Update: I tried to get a bit more information on this report, and ran into some articles calling it a hoax. So...take this with a grain of salt until (and if) I can confirm it...
Personally, I think our response should be carefully nuanced, using all the appropriate tools at our disposal. That would include Hellfire missiles, bunker-buster bombs, C-130 gunships, artillery, tanks, guns, U.S. Marines, and anything else we've got that will kill invading scum. We need to send a clear message: if you take or harm our citizens or their property, then you die. Quickly. Without hanky-twisting, prior notification, or preliminary negotiation.
Something tells me that this administration's response will somewhat less effective than a Marine detachment...
Update: I tried to get a bit more information on this report, and ran into some articles calling it a hoax. So...take this with a grain of salt until (and if) I can confirm it...
Labels:
Border Control
Miniature Explosions...
The frames at right were captured on a 10,000 fps video camera with a macro lens aimed at a sphagnum moss just as it shot out its spores. The donut-shaped vortex allows the sphagnum to shoot its spores much further than would otherwise be possible for it...
Labels:
Botany
Google Go...
It's a new programming language from Google. I just ran across it for the first time, and I haven't had a chance to look at it carefully. From the docs and FAQs at their site, they've made some interesting design choices, especially in moving away from the formality of strongly-typed languages like Java and C++. I'd love to spend a few days just playing with it, but I don't have the time just now...
The World is a Funny Place Department...
Generally, most of the visitors to my little blog get here in one of two ways: either they are crazy enough to have bookmarked my blog, or they've searched for something that appears on my blog.
For the last few days, though, a third category of visitors has dominated: those who clicked on a link in an email to this post. Apparently it caught someone's fancy, they forwarded it in an email, and those people forwarded it, and it went on and on.
Leaving me to wonder...why this particular post? I have no idea...
For the last few days, though, a third category of visitors has dominated: those who clicked on a link in an email to this post. Apparently it caught someone's fancy, they forwarded it in an email, and those people forwarded it, and it went on and on.
Leaving me to wonder...why this particular post? I have no idea...
Labels:
Blog
Friday, July 23, 2010
The Roof Project: Update...
Well, we're a few days into the project now, and we're still very pleased with progress. The old roof is now entirely gone; we've got bare wood exposed to the elements. With the old roofing material gone, some problem areas were exposed (mainly some deteriorated wood toward the bottom of the roof), and these will need to be fixed. Some of the fascia boards are warped, and Chris (the roofing contractor) is going to fix those as well.
One piece of the red metal fascia cover is now in place – a bright red horizontal stripe that looks very colorful indeed, given the large area of surrounding white or dull colors. Debbie is very happy with the color. Let's hope that continues when the entire roof is covered.
I'm thinking that this red is so bright that we'll easily be able to spot our house when we fly into or out of San Diego (nearly all flights pass with 10 miles or so, high overhead). Our roof will look like a multi-megawatt beacon. It might even be visible from space!
One piece of the red metal fascia cover is now in place – a bright red horizontal stripe that looks very colorful indeed, given the large area of surrounding white or dull colors. Debbie is very happy with the color. Let's hope that continues when the entire roof is covered.
I'm thinking that this red is so bright that we'll easily be able to spot our house when we fly into or out of San Diego (nearly all flights pass with 10 miles or so, high overhead). Our roof will look like a multi-megawatt beacon. It might even be visible from space!
Labels:
Roof
Another View of the Manipulated Jobless Number...
This time from the WSJ. There's a lot of interesting material at the link, but to my point in a previous post:
If people without jobs become discouraged and stop seeking work, the unemployment rate will decline (other things being equal). On the other hand, if people become hopeful about future employment, job seeking will go up—as will the unemployment rate.Sounds right to me...
This way of measuring job availability is clearly flawed. One simple alternative would be to measure the labor force as the number of people with jobs. Unemployment would be determined based on increases or decreases in the number of people employed relative to historic job growth.
Labels:
Recession,
Statistics
Thursday, July 22, 2010
Clyde is the Man!
Via my cousin Mike D.:
A farmer named Clyde had a car accident. In court, the trucking company's fancy lawyer was questioning Clyde.Why, “I'm fine, officer!”, of course...
"Didn't you say, at the scene of the accident, 'I'm fine,'?" asked the lawyer.
Clyde responded, "Well, I'll tell you what happened. I had just loaded my favorite mule, Bessie..."
"I didn't ask for any details", the lawyer interrupted. "Just answer the question. Did you not say, at the scene of the accident, 'I'm fine!'?"
Clyde said, "Well, I had just got Bessie into the trailer and I was driving down the road..."
The lawyer interrupted again and said, "Judge, I am trying to establish the fact that, at the scene of the accident, this man told the Highway Patrolman on the scene that he was just fine. Now several weeks after the accident he is trying to sue my client. I believe he is a fraud. Please tell him to simply answer the question."
By this time, the Judge was fairly interested in Clyde's answer and said to the lawyer, "I'd like to hear what he has to say about his favorite mule, Bessie".
Clyde thanked the Judge and proceeded.
"Well as I was saying, I had just loaded Bessie, my favorite mule, into the trailer and was driving her down the highway when this huge semi-truck and trailer ran the stop sign and smacked my truck right in the side.
I was thrown into one ditch and Bessie was thrown into the other. I was hurting real bad and didn't want to move. However, I could hear ole Bessie moaning and groaning. I knew she was in terrible shape just by her groans.
Shortly after the accident a Highway Patrolman came on the scene. He could hear Bessie moaning and groaning so he went over to her.
After he looked at her, and saw her fatal condition, he took out his gun and shot her between the eyes.
Then the Patrolman came across the road, gun still in hand, looked at me and said, "How are you feeling?"
"Now what the hell would you say?"
Labels:
Humor
Subscribe to:
Posts (Atom)









