[From nobody Fri Apr 24 12:18:36 2009 Return-Path: <sentto-20686226-672-1240519206-clarej=hbci.com@returns.groups.yahoo.com> X-Original-To: clarej@hbci.com Delivered-To: clarej@hbci.com Received: from psmtp.com (chip2mx79.postini.com [64.18.13.126]) by mail.hbci.com (Postfix) with SMTP id 9C5192780D5 for <clarej@hbci.com>; Thu, 23 Apr 2009 15:40:07 -0500 (CDT) Received: from source ([69.147.64.215]) by chip2mx79.postini.com ([64.18.5.10]) with SMTP; Thu, 23 Apr 2009 16:40:08 EDT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoogroups.com; s=lima; t=1240519207; bh=E23UiEF5egRupb4K1U0PvGLtylOun8d5d7EYbfI+FrA=; h=Received:Received:X-Yahoo-Newman-Id:X-Sender:X-Apparently-To:X-Received:X-Received:X-Received:X-IronPort-Anti-Spam-Filtered:X-IronPort-Anti-Spam-Result:X-Received:X-Trace:X-Received:Message-ID:User-Agent:To:X-Virus-Scanned:X-Virus-Status:X-Originating-IP:X-eGroups-Msg-Info:From:X-Yahoo-Profile:Sender:MIME-Version:Mailing-List:Delivered-To:List-Id:Precedence:List-Unsubscribe:Date:Subject:Reply-To:X-Yahoo-Newman-Property:Content-Type; b=cfvWOmHwjaHfYrODKHc3dHYNghO/V72CraiLZ0kzHUdk0OkaLw763erin5p3w3FheJ2zykyfaoGD+m/amxrorgjDIdKCXlNxO5pTiVuyHq70vevgbKKjPXWZ1sYWc1eT DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lima; d=yahoogroups.com; b=Se4OzAq4g2nCt7OU0YxwBwbDl677Yz1guVJwpAuzI+CIQ6q0vu69+BMN9jZkfi+qWjE9t77rRUWvSaJoaItwq5/9BQp7K9x8V4B0lKbE1N18OkV20xp6ptHIqG2hrIPR; Received: from [69.147.65.150] by n18.bullet.sp1.yahoo.com with NNFMP; 23 Apr 2009 20:40:07 -0000 Received: from [98.137.34.37] by t7.bullet.mail.sp1.yahoo.com with NNFMP; 23 Apr 2009 20:40:07 -0000 X-Yahoo-Newman-Id: 20686226-m672 X-Sender: mrfarm@frontiernet.net X-Apparently-To: hfdec@yahoogroups.com X-Received: (qmail 24682 invoked from network); 23 Apr 2009 20:40:05 -0000 X-Received: from unknown (98.137.34.45) by m1.grp.sp2.yahoo.com with QMQP; 23 Apr 2009 20:40:05 -0000 X-Received: from unknown (HELO mx10.roch.ny.frontiernet.net) (66.133.183.227) by mta2.grp.sp2.yahoo.com with SMTP; 23 Apr 2009 20:40:04 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAP9u8EnAqAFl/2dsb2JhbAC+OoFZj2mCJgkBgUQFiAsB X-Received: from relay04.roch.ny.frontiernet.net ([66.133.182.167]) by mx10.roch.ny.frontiernet.net with ESMTP; 23 Apr 2009 20:40:03 +0000 X-Trace: 53616c7465645f5f1f604d4109049ba47c4809ce52e1d82fcd79c8dc52d91082148971914b71153cbbd016831eda176768b0f9f71053d2a16cea79d60e3b477c44cf137d0c59e2659988b057211de7315f7fca8885ad6f883bb507e0c8a7a3f4 X-Received: from [192.168.1.101] (74-45-94-222.dr01.virq.wi.frontiernet.net [74.45.94.222]) by relay04.roch.ny.frontiernet.net (Postfix) with ESMTPA id 7958418E0A9 for <hfdec@yahoogroups.com>; Thu, 23 Apr 2009 20:40:01 +0000 (UTC) Message-ID: <49F0D21E.4060902@frontiernet.net> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) To: hfdec@yahoogroups.com X-Virus-Scanned: ClamAV 0.94.2/9280/Thu Apr 23 18:37:01 2009 on relay04.roch.ny.frontiernet.net X-Virus-Status: Clean X-Originating-IP: 66.133.183.227 X-eGroups-Msg-Info: 1:12:0:0:0 From: Rick W <mrfarm@frontiernet.net> X-Yahoo-Profile: kv9u Sender: hfdec@yahoogroups.com MIME-Version: 1.0 Mailing-List: list hfdec@yahoogroups.com; contact hfdec-owner@yahoogroups.com Delivered-To: mailing list hfdec@yahoogroups.com List-Id: <hfdec.yahoogroups.com> Precedence: bulk List-Unsubscribe: <mailto:hfdec-unsubscribe@yahoogroups.com> Date: Thu, 23 Apr 2009 15:39:58 -0500 Subject: [hfdec] Recommended reading, if you have not seen Bruce Perens comments Reply-To: hfdec@yahoogroups.com X-Yahoo-Newman-Property: groups-email-ff-m Content-Type: multipart/alternative; boundary="xnERzH5YzOIIb2LxOBuBcq1c1NM4axnIvSYSY62" X-pstn-neptune: 0/0/0.00/0 X-pstn-levels: (S:60.30162/99.90000 CV: 5.4137 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:94.9308 C:98.6951 ) --xnERzH5YzOIIb2LxOBuBcq1c1NM4axnIvSYSY62 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit http://perens.com/works/articles/MorganHill/ A Cyber-Attack on an American City /Bruce Perens / Just after midnight on Thursday, April 9, unidentified attackers climbed down four manholes serving the Northern California city of Morgan Hill and cut eight fiber cables <http://www.mercurynews.com/localnewsheadlines/ci_12106300>in what appears to have been an organized attack on the electronic infrastructure of an American city. Its implications, though startling, have gone almost un-reported. That attack demonstrated a severe fault in American infrastructure: its centralization. The city of Morgan Hill and parts of three counties lost 911 service, cellular mobile telephone communications, land-line telephone, DSL internet and private networks, central station fire and burglar alarms, ATMs, credit card terminals, and monitoring of critical utilities. In addition, resources that should /not/ have failed, like the local hospital's /internal/ computer network, proved to be dependent on external resources, leaving the hospital with a "paper system" for the day. In technical terms, the area was /partitioned/ from the surrounding internet. What was the attackers goal? Nothing has been revealed. Robbery? With wires cut, silent alarms were useless. Manipulation of the stock market? Companies, brokerages, and investors in the very wealthy community were cut off. Mayhem, murder, terrorism? But nothing like that seems to have happened. Some theorize unhappy communications workers, given the apparent knowledge of the community's infrastructure necessary for this attack. Or did the attackers simply want to teach us a lesson? Although they are silent on the topic, I hope those responsible for emergency services, be they in business or government, /are/ learning the lessons of Morgan Hill. The first lesson is what stayed up: stand-alone radio systems and not much else. Cell phones failed. Cellular towers can not, in general, connect phone calls on their own, even if both phones are near the same tower. They communicate with a central switching computer to operate, and when that system doesn't respond, they're useless. But police and fire authorities still had internal communications via two-way radio. Realizing that they'd need more two-way radio, authorities dispatched police to wake up the emergency coordinator <http://www.arrl.org/news/stories/2009/04/15/10771/?nc=1>of the regional ham radio club, and escort him to the community hospital with his equipment. Area hams dispatched ambulances and doctors, arranged for essential supplies, and relayed emergency communications out of the area to those with working telephones. That the hospital's local network failed is evidence of over-dependence on centralized services. The development of the internet's communications protocols was sponsored by the U.S. Department of Defense, and they were designed to survive large failures. But it still takes local engineering skill to implement robust networking services. Most companies stop when something works, not considering whether or how it will work in an emergency. Institutional networks, even those of emergency services providers, are rarely tested for operation while disconnected from the outside world. Many such networks depend on outside services to match host names to network addresses, and thus stop operating the moment they are disconnected from the internet. Even when the internal network stays up, email is often hosted on some outside service, and thus becomes unavailable. Programs that depend on an internet connection for license verification will fail, and this feature is often found in server software. Commercial VoIP telephone systems will stay up for internal use if properly engineered to be independent of outside resources, but consumer VoIP equipment will fail. This should lead managers of critical services to reconsider their dependence on software-as-a-service rather than local servers. Having your email live at Google means you don't have to manage it, but you can count on it being unavailable if your facility loses its internet connection. The same is true for any web service. And that's not acceptable if you work at a hospital or other emergency services provider, and really shouldn't be accepted at any company that expects to provide services during an infrastructure failure. Email from others in your office should continue to operate. What to do? Local infrastructure is the key. The services that you depend on, all critical web applications and email, should be based at /your/ site. They need to be able to operate without access to databases elsewhere, and to resynchronize with the rest of your operation when the network comes back up. This takes professional IT engineering to implement, and will cost more to manage, but won't leave you sitting on your hands in an emergency. Communications will be a problem during any emergency. Two-way radios have, to a great extent, been replaced by cellular "walkie-talkie" services that can /not/ be relied upon to work during an infrastructure failure. /Real/ two-way radios, stand-alone pager systems, and radio repeaters that enable regional communications are still available to the governments and businesses that endure the expense of planning, acquiring, maintaining, and testing them. Corporate disaster planners should look into such facilities. Municipalities, regardless of their size, should not consider abandoning such resources in favor of the less-robust cellular services. Satellite telephones can be expected to keep operating, although they too depend on a land infrastructure. They are expensive, and they frequently fail in emergency situations simply because their users, administrative officials rather than technical staff, fail to keep them charged and have no back-up power resource once they are discharged. A big plus for Morgan Hill was that emergency services had an well-practiced partnership with the local hams. Since you can never budget for all of the communications technicians you'll need in an emergency, using these volunteers is a must for any civil authority. They come with their own equipment, they run their own emergency drills and thus are ready to serve, and they are tinkerers able to improvise the communications system needed to meet a particular emergency. Which brings us to the issue of testing. No disaster system can be expected to work without regular testing, not only of the physical infrastructure provided for an emergency but of the /people/ who are expected to use it, in its disaster mode. But such testing takes much time and work, and tends to trigger any lurking infrastructure problems, creating outages of its own. It's much better to work such things out as a result of testing than to meet them during a real disaster. We should also consider whether it might be necessary to harden some of the local infrastructure of our communities. The old Bell System used to arrange cables in a /ring/ around a city, so that a cut in any one location could be routed around. It's not clear how much modern telephone companies have continued that practice. It might not have helped in Morgan Hill, as the attackers apparently even disabled an unused cable that could have been used to recover from the broken connections. Surprisingly, manholes don't usually have locks. They rely on the weight of the cover and general revulsion to keep people out. They are more likely to provide alarms for flooding than intrusion. Utility poles are similarly accessible. Much of our infrastructure isn't protected by anything so tough as a manhole cover. Underground cables are easily accessible in surface posts and "tombstones", boxes often located in residential neighborhoods. These can be wrecked with a screwdriver. Most buried cable cuts are caused by operating a back-hoe without first using one of the "call before digging" services to mark out the location of all of the buried utilities. What's done accidentally can also be done deliberately, and the same services that help diggers avoid utilities might point them out to an attacker. The most surprising news from Morgan Hill is that they survived reasonably unscathed. That they did so is a result of emergency planning in place for California's four seasons: fire, floods, earthquakes, and riots. Most communities don't practice disaster plans as intensively. Will there be another Morgan Hill? Definitely. And the next time it might happen to a denser community that won't be so astonishingly able to sustain the trouble using its two-way radios and hams. The next time, it might be connected with some other event, be it crime or terrorism. Company and government officers take notice: the only way you'll fare well is if you start planning /now./ --xnERzH5YzOIIb2LxOBuBcq1c1NM4axnIvSYSY62 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> </head> <body style="background-color: #ffffff;"> <!--~-|**|PrettyHtmlStartT|**|-~--> <div id="ygrp-mlmsg" style="width:655px; position:relative;"> <div id="ygrp-msg" style="width: 470px; margin:0; padding:0 25px 0 0; float:left; z-index:1;"> <!--~-|**|PrettyHtmlEndT|**|-~--> <div id="ygrp-text" > <!--~-|**|PrettyHtmlStart|**|-~--> <br><br> <!--~-|**|PrettyHtmlEnd|**|-~--> <p><br> <a href="http://perens.com/works/articles/MorganHill/">http://perens.<wbr>com/works/<wbr>articles/<wbr>MorganHill/</a><br> <br> A Cyber-Attack on an American City<br> <br> /Bruce Perens /<br> Just after midnight on Thursday, April 9, unidentified attackers climbed <br> down four manholes serving the Northern California city of Morgan Hill <br> and cut eight fiber cables <br> &lt;<a href="http://www.mercurynews.com/localnewsheadlines/ci_12106300">http://www.mercuryn<wbr>ews.com/localnew<wbr>sheadlines/<wbr>ci_12106300</a>&gt;in what <br> appears to have been an organized attack on the electronic <br> infrastructure of an American city. Its implications, though startling, <br> have gone almost un-reported.<br> <br> That attack demonstrated a severe fault in American infrastructure: its <br> centralization. The city of Morgan Hill and parts of three counties lost <br> 911 service, cellular mobile telephone communications, land-line <br> telephone, DSL internet and private networks, central station fire and <br> burglar alarms, ATMs, credit card terminals, and monitoring of critical <br> utilities. In addition, resources that should /not/ have failed, like <br> the local hospital's /internal/ computer network, proved to be dependent <br> on external resources, leaving the hospital with a &quot;paper system&quot; for <br> the day.<br> <br> In technical terms, the area was /partitioned/ from the surrounding <br> internet. What was the attackers goal? Nothing has been revealed. <br> Robbery? With wires cut, silent alarms were useless. Manipulation of the <br> stock market? Companies, brokerages, and investors in the very wealthy <br> community were cut off. Mayhem, murder, terrorism? But nothing like that <br> seems to have happened. Some theorize unhappy communications workers, <br> given the apparent knowledge of the community's infrastructure necessary <br> for this attack. Or did the attackers simply want to teach us a lesson?<br> <br> Although they are silent on the topic, I hope those responsible for <br> emergency services, be they in business or government, /are/ learning <br> the lessons of Morgan Hill. The first lesson is what stayed up: <br> stand-alone radio systems and not much else. Cell phones failed. <br> Cellular towers can not, in general, connect phone calls on their own, <br> even if both phones are near the same tower. They communicate with a <br> central switching computer to operate, and when that system doesn't <br> respond, they're useless. But police and fire authorities still had <br> internal communications via two-way radio.<br> <br> Realizing that they'd need more two-way radio, authorities dispatched <br> police to wake up the emergency coordinator <br> &lt;<a href="http://www.arrl.org/news/stories/2009/04/15/10771/?nc=1">http://www.arrl.<wbr>org/news/<wbr>stories/2009/<wbr>04/15/10771/<wbr>?nc=1</a>&gt;of the regional <br> ham radio club, and escort him to the community hospital with his <br> equipment. Area hams dispatched ambulances and doctors, arranged for <br> essential supplies, and relayed emergency communications out of the area <br> to those with working telephones.<br> <br> That the hospital's local network failed is evidence of over-dependence <br> on centralized services. The development of the internet's <br> communications protocols was sponsored by the U.S. Department of <br> Defense, and they were designed to survive large failures. But it still <br> takes local engineering skill to implement robust networking services. <br> Most companies stop when something works, not considering whether or how <br> it will work in an emergency.<br> <br> Institutional networks, even those of emergency services providers, are <br> rarely tested for operation while disconnected from the outside world. <br> Many such networks depend on outside services to match host names to <br> network addresses, and thus stop operating the moment they are <br> disconnected from the internet. Even when the internal network stays up, <br> email is often hosted on some outside service, and thus becomes <br> unavailable. Programs that depend on an internet connection for license <br> verification will fail, and this feature is often found in server <br> software. Commercial VoIP telephone systems will stay up for internal <br> use if properly engineered to be independent of outside resources, but <br> consumer VoIP equipment will fail.<br> <br> This should lead managers of critical services to reconsider their <br> dependence on software-as-<wbr>a-service rather than local servers. Having <br> your email live at Google means you don't have to manage it, but you can <br> count on it being unavailable if your facility loses its internet <br> connection. The same is true for any web service. And that's not <br> acceptable if you work at a hospital or other emergency services <br> provider, and really shouldn't be accepted at any company that expects <br> to provide services during an infrastructure failure. Email from others <br> in your office should continue to operate.<br> <br> What to do? Local infrastructure is the key. The services that you <br> depend on, all critical web applications and email, should be based at <br> /your/ site. They need to be able to operate without access to databases <br> elsewhere, and to resynchronize with the rest of your operation when the <br> network comes back up. This takes professional IT engineering to <br> implement, and will cost more to manage, but won't leave you sitting on <br> your hands in an emergency.<br> <br> Communications will be a problem during any emergency. Two-way radios <br> have, to a great extent, been replaced by cellular &quot;walkie-talkie&quot; <br> services that can /not/ be relied upon to work during an infrastructure <br> failure. /Real/ two-way radios, stand-alone pager systems, and radio <br> repeaters that enable regional communications are still available to the <br> governments and businesses that endure the expense of planning, <br> acquiring, maintaining, and testing them. Corporate disaster planners <br> should look into such facilities. Municipalities, regardless of their <br> size, should not consider abandoning such resources in favor of the <br> less-robust cellular services.<br> <br> Satellite telephones can be expected to keep operating, although they <br> too depend on a land infrastructure. They are expensive, and they <br> frequently fail in emergency situations simply because their users, <br> administrative officials rather than technical staff, fail to keep them <br> charged and have no back-up power resource once they are discharged.<br> <br> A big plus for Morgan Hill was that emergency services had an <br> well-practiced partnership with the local hams. Since you can never <br> budget for all of the communications technicians you'll need in an <br> emergency, using these volunteers is a must for any civil authority. <br> They come with their own equipment, they run their own emergency drills <br> and thus are ready to serve, and they are tinkerers able to improvise <br> the communications system needed to meet a particular emergency.<br> <br> Which brings us to the issue of testing. No disaster system can be <br> expected to work without regular testing, not only of the physical <br> infrastructure provided for an emergency but of the /people/ who are <br> expected to use it, in its disaster mode. But such testing takes much <br> time and work, and tends to trigger any lurking infrastructure problems, <br> creating outages of its own. It's much better to work such things out as <br> a result of testing than to meet them during a real disaster.<br> <br> We should also consider whether it might be necessary to harden some of <br> the local infrastructure of our communities. The old Bell System used to <br> arrange cables in a /ring/ around a city, so that a cut in any one <br> location could be routed around. It's not clear how much modern <br> telephone companies have continued that practice. It might not have <br> helped in Morgan Hill, as the attackers apparently even disabled an <br> unused cable that could have been used to recover from the broken <br> connections.<br> <br> Surprisingly, manholes don't usually have locks. They rely on the weight <br> of the cover and general revulsion to keep people out. They are more <br> likely to provide alarms for flooding than intrusion. Utility poles are <br> similarly accessible. Much of our infrastructure isn't protected by <br> anything so tough as a manhole cover. Underground cables are easily <br> accessible in surface posts and &quot;tombstones&quot;<wbr>, boxes often located in <br> residential neighborhoods. These can be wrecked with a screwdriver.<br> <br> Most buried cable cuts are caused by operating a back-hoe without first <br> using one of the &quot;call before digging&quot; services to mark out the location <br> of all of the buried utilities. What's done accidentally can also be <br> done deliberately, and the same services that help diggers avoid <br> utilities might point them out to an attacker.<br> <br> The most surprising news from Morgan Hill is that they survived <br> reasonably unscathed. That they did so is a result of emergency planning <br> in place for California's four seasons: fire, floods, earthquakes, and <br> riots. Most communities don't practice disaster plans as intensively.<br> Will there be another Morgan Hill? Definitely. And the next time it <br> might happen to a denser community that won't be so astonishingly able <br> to sustain the trouble using its two-way radios and hams. The next time, <br> it might be connected with some other event, be it crime or terrorism. <br> Company and government officers take notice: the only way you'll fare <br> well is if you start planning /now./<br> </p> </div> <!--~-|**|PrettyHtmlStart|**|-~--> <div width="1" style="color: white; clear: both;">__._,_.___</div> <!-- Start the section with Message In topic --> <div id="ygrp-actbar" style="clear: both; margini-bottom: 25px; white-space:nowrap; color: #666; text-align: right;"> <span class="left" style="float: left; white-space:nowrap;"> <a href="http://groups.yahoo.com/group/hfdec/message/672;_ylc=X3oDMTMzZzdjMTRtBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAM2NzIEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMjQwNTE5MjA2BHRwY0lkAzY3Mg--"> Messages in this topic </a> (<span class="bld" style="font-weight:bold;">1</span>) </span> <a href="http://groups.yahoo.com/group/hfdec/post;_ylc=X3oDMTJwdmZjdGg1BF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAM2NzIEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMjQwNTE5MjA2?act=reply&messageNum=672"> <span class="bld" style="font-weight:bold;"> Reply </span> (via web post) </a> | <a href="http://groups.yahoo.com/group/hfdec/post;_ylc=X3oDMTJmcGkwc3FkBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNudHBjBHN0aW1lAzEyNDA1MTkyMDY-" class="bld" style="font-weight:bold;"> Start a new topic </a> </div> <!------- Start Nav Bar ------> <!-- |**|begin egp html banner|**| --> <div id="ygrp-vitnav" style="padding-top: 10px; font-family: Verdana; font-size: 77%; margin: 0;"> <a href="http://groups.yahoo.com/group/hfdec/messages;_ylc=X3oDMTJmNTVydWNyBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNtc2dzBHN0aW1lAzEyNDA1MTkyMDY-">Messages</a> | <a href="http://groups.yahoo.com/group/hfdec/files;_ylc=X3oDMTJncnVtMnJkBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNmaWxlcwRzdGltZQMxMjQwNTE5MjA2">Files</a> | <a href="http://groups.yahoo.com/group/hfdec/photos;_ylc=X3oDMTJmNGNiMHRiBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNwaG90BHN0aW1lAzEyNDA1MTkyMDY-">Photos</a> | <a href="http://groups.yahoo.com/group/hfdec/members;_ylc=X3oDMTJmZHNrdXRoBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNtYnJzBHN0aW1lAzEyNDA1MTkyMDY-">Members</a> </div> <!-- |**|end egp html banner|**| --> <div id="ygrp-mkp"> <div id="hd">MARKETPLACE</div> <div id="ads"> <div class="ad" style="color:#628C2A; font-family:Arial; font-weight:bold;"> <a href="http://us.ard.yahoo.com/SIG=14k91nq2p/M=733250.13416488.13509112.10835568/D=groups/S=1705063108:MKP1/Y=YAHOO/EXP=1240526407/L=/B=_qr9D0PDhEM-/J=1240519207121004/K=ngdJGGPwteGktx7ydw6eNQ/A=5687713/R=0/SIG=12ecgaa63/*http://www.socialtrack.net/redir.aspx?CID=18601&AFID=43106&DID=81069&SID=ad2">I'm happy I lost my Job. Now I make $12,000/mo online! See how I do it: WealthResource.org.</a> </div> <div class="ad" style="color:#628C2A; font-family:Arial; font-weight:bold;"> <hr size=1 noshade> <p><a href="http://us.ard.yahoo.com/SIG=14k3fa6hs/M=493064.12016295.13271503.10835568/D=groups/S=1705063108:MKP1/Y=YAHOO/EXP=1240526407/L=/B=AKv9D0PDhEM-/J=1240519207121004/K=ngdJGGPwteGktx7ydw6eNQ/A=5697381/R=0/SIG=11eaa5dke/*http://groups.yahoo.com/group/mompowergroup/">Mom Power: Discover the community of moms doing more for their families, for the world and for each other</a></p> </div> </div> </div> <!-- yahoo logo --> <!-- |**|begin egp html banner|**| --> <div id="ygrp-ft" style="font-family: verdana; font-size: 77%; border-top: 1px solid #666; padding: 5px 0;"> <a href="http://groups.yahoo.com/;_ylc=X3oDMTJlb2lxYzNiBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTI0MDUxOTIwNg--"> <img src="http://us.i1.yimg.com/us.yimg.com/i/yg/img/logo/ma_grp_160.gif" height="15" width="106" border="0" alt="Yahoo! Groups"></a> <br> <a href="http://groups.yahoo.com/group/hfdec/join;_ylc=X3oDMTJndjZndG9pBF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNzdG5ncwRzdGltZQMxMjQwNTE5MjA2">Change settings via the Web</a> (Yahoo! ID required) <br> Change settings via email: <a href="mailto:hfdec-digest@yahoogroups.com?subject=Email Delivery: Digest">Switch delivery to Daily Digest</a> | <a href = "mailto:hfdec-traditional@yahoogroups.com?subject=Change Delivery Format: Traditional">Switch format to Traditional</a> <br> <a href="http://groups.yahoo.com/group/hfdec;_ylc=X3oDMTJlNHNsM2I2BF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNocGYEc3RpbWUDMTI0MDUxOTIwNg--"> Visit Your Group </a> | <a href="http://docs.yahoo.com/info/terms/"> Yahoo! Groups Terms of Use </a> | <a href="mailto:hfdec-unsubscribe@yahoogroups.com?subject="> Unsubscribe </a> </div> <!-- |**|end egp html banner|**| --> </div> <!-- ygrp-msg --> <!-- Sponsor --> <!-- |**|begin egp html banner|**| --> <div id="ygrp-sponsor" style="width:160px; float:right; clear:none; margin:0 0 25px 0; background: white;"> <!-- Network content --> <!-- Start Recommendations --> <div id="ygrp-reco"> </div> <!-- End Recommendations --> <!-- Start vitality --> <div id="ygrp-vital" style="background-color: #e0ecee; margin-bottom: 20px; padding: 2px 0 8px 8px;"> <div id="vithd" style="font-size: 77%; font-family: Verdana; font-weight: bold; color: #333; text-transform: uppercase;">Recent Activity</div> <ul style="list-style-type:none; padding: 0; margin: 2px 0;"> </ul> <a href="http://groups.yahoo.com/group/hfdec;_ylc=X3oDMTJmaDhxMGc1BF9TAzk3MzU5NzE0BGdycElkAzIwNjg2MjI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2Z2hwBHN0aW1lAzEyNDA1MTkyMDY-"> Visit Your Group </a> </div> <!-- Network content --> <div style="background-color:#EEEEEE; margin-bottom:20px; padding:10px 8px;"> <div id="nc"> <div class="ad" style="color:#628C2A; font-family:Arial; font-weight:bold;"> <div id="hd1">Drive Traffic</div> <p><a href="http://us.ard.yahoo.com/SIG=14hr3hb82/M=493064.12016255.12445662.8674578/D=groups/S=1705063108:NC/Y=YAHOO/EXP=1240526407/L=/B=Aav9D0PDhEM-/J=1240519207121004/K=ngdJGGPwteGktx7ydw6eNQ/A=4025338/R=0/SIG=12jnci1fd/*http://us.rd.yahoo.com/evt=44092/*http://searchmarketing.yahoo.com/srch/index.php">Sponsored Search</a></p> <p>can help increase</p> <p>your site traffic.</p> </div> <div class="ad" style="color:#628C2A; font-family:Arial; font-weight:bold;"> <div id="hd1">All-Bran</div> <p><a href="http://us.ard.yahoo.com/SIG=14h129t23/M=493064.12016283.12445687.8674578/D=groups/S=1705063108:NC/Y=YAHOO/EXP=1240526407/L=/B=Aqv9D0PDhEM-/J=1240519207121004/K=ngdJGGPwteGktx7ydw6eNQ/A=5202317/R=0/SIG=11aijbghb/*http://new.groups.yahoo.com/allbrangroup">Day 10 Club</a></p> <p>on Yahoo! Groups</p> <p>Feel better with fiber.</p> </div> <div class="ad" style="color:#628C2A; font-family:Arial; font-weight:bold;"> <div id="hd1">Find helpful tips</div> <p><a href="http://us.ard.yahoo.com/SIG=14hetsmto/M=493064.12016258.12582637.8674578/D=groups/S=1705063108:NC/Y=YAHOO/EXP=1240526407/L=/B=A6v9D0PDhEM-/J=1240519207121004/K=ngdJGGPwteGktx7ydw6eNQ/A=5191954/R=0/SIG=112mhte3e/*http://www.ygroupsblog.com/blog/">for Moderators</a></p> <p>on the Yahoo!</p> <p>Groups team blog.</p> </div> </div> </div> </div> <!-- |**|end egp html banner|**| --> <div style="clear:both; color: #FFF; font-size:1px;">.</div> </div> <img src="http://geo.yahoo.com/serv?s=97359714/grpId=20686226/grpspId=1705063108/msgId=672/stime=1240519206/nc1=4025338/nc2=5202317/nc3=5191954" width="1" height="1"> <br> <div style="color: white; clear: both;">__,_._,___</div> <!--~-|**|PrettyHtmlEnd|**|-~--> </body> <!--~-|**|PrettyHtmlStart|**|-~--> <head> <style type="text/css"> <!-- #ygrp-mkp{ border: 1px solid #d8d8d8; font-family: Arial; margin: 14px 0px; padding: 0px 14px; } #ygrp-mkp hr{ border: 1px solid #d8d8d8; } #ygrp-mkp #hd{ color: #628c2a; font-size: 85%; font-weight: bold; line-height: 122%; margin: 10px 0px; } #ygrp-mkp #ads{ margin-bottom: 10px; } #ygrp-mkp .ad{ padding: 0 0; } #ygrp-mkp .ad a{ color: #0000ff; text-decoration: none; } --> </style> </head> <head> <style type="text/css"> <!-- #ygrp-sponsor #ygrp-lc{ font-family: Arial; } #ygrp-sponsor #ygrp-lc #hd{ margin: 10px 0px; font-weight: bold; font-size: 78%; line-height: 122%; } #ygrp-sponsor #ygrp-lc .ad{ margin-bottom: 10px; padding: 0 0; } --> </style> </head> <head> <style type="text/css"> <!-- #ygrp-mlmsg {font-size:13px; font-family: arial,helvetica,clean,sans-serif;*font-size:small;*font:x-small;} #ygrp-mlmsg table {font-size:inherit;font:100%;} #ygrp-mlmsg select, input, textarea {font:99% arial,helvetica,clean,sans-serif;} #ygrp-mlmsg pre, code {font:115% monospace;*font-size:100%;} #ygrp-mlmsg * {line-height:1.22em;} #ygrp-text{ font-family: Georgia; } #ygrp-text p{ margin: 0 0 1em 0; } dd.last p a { font-family: Verdana; font-weight: bold; } #ygrp-vitnav{ padding-top: 10px; font-family: Verdana; font-size: 77%; margin: 0; } #ygrp-vitnav a{ padding: 0 1px; } #ygrp-mlmsg #logo{ padding-bottom: 10px; } #ygrp-reco { margin-bottom: 20px; padding: 0px; } #ygrp-reco #reco-head { font-weight: bold; color: #ff7900; } #reco-category{ font-size: 77%; } #reco-desc{ font-size: 77%; } #ygrp-vital a{ text-decoration: none; } #ygrp-vital a:hover{ text-decoration: underline; } #ygrp-sponsor #ov ul{ padding: 0 0 0 8px; margin: 0; } #ygrp-sponsor #ov li{ list-style-type: square; padding: 6px 0; font-size: 77%; } #ygrp-sponsor #ov li a{ text-decoration: none; font-size: 130%; } #ygrp-sponsor #nc{ background-color: #eee; margin-bottom: 20px; padding: 0 8px; } #ygrp-sponsor .ad{ padding: 8px 0; } #ygrp-sponsor .ad #hd1{ font-family: Arial; font-weight: bold; color: #628c2a; font-size: 100%; line-height: 122%; } #ygrp-sponsor .ad a{ text-decoration: none; } #ygrp-sponsor .ad a:hover{ text-decoration: underline; } #ygrp-sponsor .ad p{ margin: 0; font-weight: normal; color: #000000; } o{font-size: 0; } .MsoNormal{ margin: 0 0 0 0; } #ygrp-text tt{ font-size: 120%; } blockquote{margin: 0 0 0 4px;} .replbq{margin:4} dd.last p span { margin-right: 10px; font-family: Verdana; font-weight: bold; } dd.last p span.yshortcuts { margin-right: 0; } div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited { text-decoration: none; } div.file-title a, div.file-title a:active, div.file-title a:hover, div.file-title a:visited { text-decoration: none; } #ygrp-msg p#attach-count { clear: both; padding: 15px 0 3px 0; overflow: hidden; } #ygrp-msg p#attach-count span { color: #1E66AE; font-weight: bold; } div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts { font-family: Verdana; font-size: 10px; font-weight: normal; } #ygrp-msg p a { font-family: Verdana; font-size: 10px; } #ygrp-mlmsg a { color: #1E66AE; } div.attach-table div div a { text-decoration: none; } div.attach-table { width: 400px; } --> </style> </head> <!--~-|**|PrettyHtmlEnd|**|-~--> </html><!--End group email --> --xnERzH5YzOIIb2LxOBuBcq1c1NM4axnIvSYSY62-- ]