<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bulbous, Not Tapered</title>
	<atom:link href="http://mikelococo.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikelococo.com</link>
	<description>Foo-Fu and other favorites...</description>
	<lastBuildDate>Thu, 29 Mar 2012 22:17:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Capacity Planning for Snort IDS</title>
		<link>http://mikelococo.com/2011/08/snort-capacity-planning/</link>
		<comments>http://mikelococo.com/2011/08/snort-capacity-planning/#comments</comments>
		<pubDate>Sun, 14 Aug 2011 14:43:02 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>

		<guid isPermaLink="false">http://mikelococo.com/?p=352</guid>
		<description><![CDATA[Snort is a very capable network intrusion detection system, but planning a first-time hardware purchase can be difficult. It requires fairly deep knowledge of x86 server performance, network usage patterns at your site, along with some snort-specific knowledge. Documentation is &#8230; <a href="http://mikelococo.com/2011/08/snort-capacity-planning/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.snort.org/">Snort</a> is a very capable network intrusion detection system, but planning a first-time hardware purchase can be difficult. It requires fairly deep knowledge of x86 server performance, network usage patterns at your site, along with some snort-specific knowledge. Documentation is poor, current planning guides tend to focus on one or two factors in depth without addressing other broad issues that can cause serious performance problems. This post aims to be a comprehensive but high-level overview of the issues that must be considered when sizing a medium to large snort deployment.</p>
<h2>A Note About Small Sites</h2>
<p>Small snort-deployments don&#8217;t require much planning. Almost any system or virtual-machine will suffice to experiment with Snort on a DSL or cable internet connection with a bandwidth of 5-10Mbits/sec, just jump right in. If you need to monitor 50-100Mbits/sec of network traffic, or 5-10Gbits/sec of network traffic, then this guide can help you size you size your sensor hardware.</p>
<h2>Know Your Site</h2>
<p>It helps to know a few things about your site before you start planning.</p>
<h3>What link(s) do you intend to monitor?</h3>
<p>The most common way to get started is to monitor your internet link(s). Many organizations also expand to monitor some internal links: data-center routers, site-to-site links, or networks with VIP workstations. Unless you know what you&#8217;re doing, I suggest starting with your internet links and expanding once you&#8217;ve got that performing well. There are generally far fewer internet links to consider, and they are often much lower bandwidth than internal links which can make your first deployment simpler.</p>
<h3>Link Locations</h3>
<p>Life is simple if you have a single internet connection at a single site. If your network is more complicated then you&#8217;ll need to work with the team that manages your routers. They can help you figure out how many locations will need to get a sensor and how many capture interfaces each of those sensors will need to monitor the links at that site.</p>
<h3>How much traffic do you need to monitor?</h3>
<p>The single biggest factor when sizing your snort hardware is the amount of traffic that it must monitor. The values to consider are the maximum burst speed of each link, and also its average daily peak. It&#8217;s common to have burst capacity well in excess of actual usage and when you design your sensors you must decide what traffic level you&#8217;re going to plan for. Planning for the burst value ensures that you won&#8217;t drop packets even in a worst-case scenario, but may be much more expensive than planning for the average daily peak.</p>
<p>For example, it&#8217;s common to contract with an ISP for 100Mbits/sec of bandwidth that is delivered over a 1000Mbits/sec link. The average daily peak for such a link may be 60Mbits/sec, but on rare occasions it may burst up to the full 1000Mbits/sec for short durations. A sensor designed for the relatively small amount of daily peak traffic is inexpensive and simple to manage, but may drop 80% of packets or more during bursts.</p>
<p>If MRTG or Nagios graphs of router utilization are available, they can be very helpful in capacity planning.</p>
<h3>Inline, Tap, Span, or VACL Capture</h3>
<p>There are various ways to extract traffic for examination. Inline deployments where Snort is used as an intrusion prevention system should be treated with great caution because sizing problems and configuration issues related to Snort can cause network problems and outages for all your users. When running a detection configuration in conjunction with taps, spans, or VACL captures, Snort problems generally don&#8217;t cause user-facing network outages are a much much lower risk.</p>
<p>Security teams generally favor taps due to their consistent performance even when a router is overloaded, but there are successful Snort deployments that utilize all of the above methods of obtaining traffic for inspection. Ntop.org has a good document on making the <a href="http://www.ntop.org/blog/ntop/port-mirror-vs-network-tap/">tap vs span decision</a>, and the wikipedia page on <a href="http://en.wikipedia.org/wiki/Network_tap">network taps</a> provides informative background as well.</p>
<h3>Operating System Expertise</h3>
<p>Consider what operating systems your technical staff have expertise in. It is common to run high-performance Snort deployments on various Linux distributions or on FreeBSD. At one time, FreeBSD had a considerable performance advantage over equivalent Linux systems but it is currently possible to built a 10Gbit/sec deployment on Linux or BSD based systems using roughly equivalent hardware.</p>
<p>I recommend against deploying on Windows because not all Snort features are supported on that platform. Notably, shared-object rules do not function on windows as of Snort 2.9.0.5. While there are far fewer shared-object rules than normal &#8220;GID 1&#8243; rules, and they are released less frequently, they can still be a useful source of intelligence.</p>
<p>I also recommend against deploying Snort on *nixes other than Linux or BSD. Although Snort may work well on these platforms, the community employing them is much smaller. It will be much more difficult to find guidance on any platform-specific issues that you encounter.</p>
<p>It&#8217;s worth mentioning that my own experience is with high-performance Snort deployments on Linux, and parts of this post reflect that bias.</p>
<h2>Single-Threading vs Multiple-CPUs</h2>
<p>Snort is essentially  single-threaded, which means that out of the box it doesn&#8217;t make  effective use of multiple CPUs (technically there is more than one  thread in a snort process, but the others are used for housekeeping  tasks that don&#8217;t require much CPU power, not for scaling traffic analysis across  multiple CPUs).<em> </em> As of August 2011, Snort on a single-CPU can be tuned to examine 200-500Mbits/sec, depending on the size of the ruleset used.</p>
<p>It&#8217;s possible to scale to 10Gbits/sec by running multiple copies of snort on the same  computer, each using a different CPU. A multi-snort/multi-CPU configuration is quite a lot more complex to manage than a  single-cpu deployment. Traffic from high-capacity links must be divided up into 200-500Mbit/sec chunks that can be examined by a single CPU, techniques to perform this load-balancing are discussed in the next section. Additionally, startup-scripts often must be customized and it can be difficult to manage multiple configuration files and log files. In spite of the management complexity, large organizations have successfully managed high performance Snort deployments this way for many years.</p>
<p>Suricata is a relatively new project that is well-worth keeping an eye on. It has a multi-threaded architecture that makes effective use of multiple CPUs, but is <a href="http://www.inliniac.net/blog/2010/07/22/on-suricata-performance.html">not as CPU efficient as Snort</a> as of Suricata 1.0.0. As such, Suricata on a large multi-core system is much faster than Snort running on a single CPU, but about <a href="http://lists.emergingthreats.net/pipermail/emerging-sigs/2010-August/008613.html">4x slower than many Snort instances</a> running on that same multi-core system. As Suricata matures, performance will improve. Additionally, managing a single Suricata instance is simpler than managing many Snort instances.</p>
<h2>Traffic Capture Frameworks</h2>
<p>Snort is a modular system that supports many frameworks for capturing traffic, but not all of them scale equally well.</p>
<h3>AFPACKET</h3>
<p>The default capture framework on Linux since Snort 2.9, afpacket provides no features to load-balance traffic between multiple instances of snort running on multiple CPUs. As such, it can&#8217;t scale beyond 200-500Mbits/sec of throughput without some external technique to balance the load between several network interfaces. Even with this limitation, afpacket is the simplest and best choice for snort deployments with less than 200Mbits/sec of traffic.</p>
<h3>Libpcap 0.9.x</h3>
<p>The default capture framework on Linux for the Snort the 2.8.x series and prior, libpcap is very similar to afpacket from a user-perspective. It also lacks a built-in load-balancing feature, and can scale to a few hundred Mbits/sec of traffic. Consider upgrading Snort and using afpacket instead.</p>
<h3>Libpcap &gt;= 1.x.x</h3>
<p>Around 1.0.0, libpcap introduced an mmapped feature designed to improve capture performance. Unfortunately the feature backfired and reduced performance due to a <a href="http://lists.virus.org/snort-users/msg00108.html">hard-coded buffer-size</a> that is too small for most sites. Use afpacket instead unless you know what you&#8217;re doing.</p>
<h3>PFRING and TNAPI/DNA</h3>
<p><a href="http://www.ntop.org/products/pf_ring/">Pfring</a> is a linux kernel-module that provides load-balancing through its <em>ring clusters</em> feature. It additionally supports several capture cards through its TNAPI/DNA high-performance drivers, which are available for $200-250 from the <a href="http://www.nmon.net/shop/cart.php">ntop store</a>. Pfring, used in conjunction with a TNAPI-compatible network interface, is the least expensive method available to load-balance traffic to several instances of Snort running on several CPUs, and can scale to 10G on appropriate hardware.</p>
<h3>High-Performance Capture Cards</h3>
<p><a href="http://www.endace.com/">Endace</a> and other companies manufacture high-performance capture cards with integrated drivers that have load-balancing features. Depending on speed and features these cards can cost anywhere from $2,000-$25,000, and at the high end scale to 10Gbits/sec. Most of my high-performance Snort experience is on Endace hardware, which has its niggles but generally works very well.</p>
<h3>Sourcefire 3D Hardware</h3>
<p>Last, but certainly not least, Sourcefire sells <a href="http://www.sourcefire.com/security-technologies/cyber-security-products/3d-system">snort hardware</a> that is throughput rated and can simplify much of your planning.  Managing a multi-Snort deployment is a lot of work, and Sourcefire has  designed their systems to provide the power of Snort with an easy to  manage interface, plus some features like RNA that are only available  via Sourcefire. They&#8217;re more expensive than similar hardware to run  open-source snort, but they may be more cost-effective in the long-run  unless your organization has a do-it-yourself culture with time and  technical expertise to tackle a complex open-source Snort deployment.</p>
<h2>Traffic Management Techniques</h2>
<p>The following traffic management techniques can be used in conjunction with the capture frameworks above to provide additional flexibility.</p>
<h3>Hardware Load-Balancers</h3>
<p><a href="http://www.gigamon.com/gigavue-2404-mid-density-10g-data-access-switch">Gigamon</a>, <a href="http://www.cpacket.com/">CPacket</a>, and <a href="http://www.corero.com/content/products/intrusion_detection/ids_balancer.jsp">Top-Layer</a> produce specialized network switches that can perform load-balancing to multiple network interfaces. The port-channeling feature of retired Cisco routers can be used to similar effect. These devices can be used to distribute traffic to multiple network interfaces in a single server or even to multiple servers, possibly scaling beyond 10G (I haven&#8217;t tested beyond 10G). I&#8217;ve worked with both Gigamon and Top-Layer hardware and found that they both do what they claim, although only Gigamon offers many 10Gbit/sec interfaces in one device. CPacket has been used by knowledgeable peers of mine and offers a unique feature that allows you to use any vanilla network switch to expand the port count of their load-balancer by using mac-address rewriting. These systems are fairly expensive, typically carrying 5-figure price tags, but often can be put to many uses in a large organization.</p>
<h3>Manual Load-Balancing</h3>
<p>Sometimes, traffic can be manually divided simply by configuring routers to send about half of your networks over one port and half over another. This &#8220;poor man&#8217;s&#8221; load-balancing can be cost-effective for links that are just a bit too large for one network interface.</p>
<h3>Linux Bonded Interfaces</h3>
<p>The opposite of load-balancing, if you have several low-bandwidth interfaces that you would like to inspect without the overhead of managing multiple copies of snort you can use <a href="http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding">bonding</a> to <a href="http://lists.virus.org/snort-users-0303/msg00250.html">aggregate them together</a> as long as the total throughput isn&#8217;t more than a few hundred Mbits/sec.</p>
<h2>Sizing Hardware</h2>
<p>Now that you know how many locations you need to place a server at, how many links there are to monitor at each location, and what capture-frameworks can work for you, it&#8217;s time to choose your servers.</p>
<h3>CPU</h3>
<p>A very rough and conservative rule of thumb is that Snort running on a single CPU can examine 200Mbits/sec of traffic without dropping an appreciable number of packets. Snort can examine 500Mbits/sec of traffic or even much more on a single CPU with the right networking hardware and a very small or very well-tuned ruleset, but don&#8217;t count on achieving that kind of throughput unless you have tested and measured it in your environment. Martin has posted a more detailed <a href="http://ossectools.blogspot.com/2011/04/network-intrusion-detection-systems.html">CPU sizing exercise</a> on his blog if you&#8217;d like to dig a little deeper.</p>
<p>Remember that snort is single-threaded. Unless you plan to use a load-balanced capture-framework, single-CPU performance is more important than number of cores. Alternately, if you know that you have lots of traffic to monitor, you&#8217;ll need a multi-core system paired with a load-balanced capture framework. Snort scales very linearly with the number of cores you throw at it, so don&#8217;t worry about diminishing returns as you add cores.</p>
<h3>RAM</h3>
<p>Each snort process can occupy 2Gbytes-5Gbytes of ram. How much depends on:</p>
<ul>
<li>Traffic &#8211; The more traffic a sensor handles, the more state it must track. Stream5 can use anywhere from a few Mbytes to 1Gbyte to track TCP state.</li>
<li>Pattern Matcher &#8211; Some pattern matchers are <a href="http://sourceforge.net/mailarchive/message.php?msg_id=27113364">very CPU efficient, and others are very memory efficient</a>. The ac-nq matcher is the most cpu-efficient, reducing CPU usage by up to 30% over ac-split, but adding over 1Gbyte of ram usage per process.  The ac-bnfa matcher is quite memory efficient, reducing ram usage by several hundred Mbytes per process, but increasing CPU usage by up to 20%.</li>
<li>Number of rules &#8211; The more rules that are active, the more memory the pattern matcher uses.</li>
<li>Preprocessor configs &#8211; The stream5 memcap is one crucial factor for controlling memory usage, but all preprocessors occupy memory and many can be configured to be conservative or resource-hungry.</li>
</ul>
<p>A Snort process inspecting 400Mbits/sec of traffic, with 7000 active rules, using the ac-nq pattern matcher (which is memory-hungry), and a stream5 memcap of 1Gbyte uses about 4.5Gbytes of RAM. With a smaller ruleset and the ac-bnfa pattern matcher (which is memory-efficient), I&#8217;ve observed snort processes use about 2.5Gbytes of RAM.</p>
<p>Note that the operating system and other applications will need some RAM as well, and if you don&#8217;t have unusual needs 2G is generally plenty. A detailed discussion of RAM sizing for the database is beyond the scope of this post, but generally for a multi-snort deployment it&#8217;s worth putting the database on a separate server that has 1-4Gbytes of RAM.</p>
<h3>Disk Capacity and I/O</h3>
<p>Snort generates very little disk I/O when outputting unified2 logs. Similarly barnyard2 generates very little I/O when reading them. Any hard-disk configuration, even a single low-rpm disk will meet snort&#8217;s performance needs.</p>
<p>A detailed discussion of the database I/O needs is beyond the scope of this post. Again, most multi-snort sites should consider putting the database on a different server.  I/O needs will vary depending on the alert-rate, the number of users querying the database, and the front-end used, but in general a 4-disk raid-10 will suffice even for a large multi-gigabit deployment. Small sites with only a few hundred megabits/sec of traffic could even use a single-disk if it meets their availability requirements.</p>
<h3>Administrative Network Interface</h3>
<p>Snort doesn&#8217;t generate a notable amount of network traffic on the administrative interface unless you&#8217;re connecting to the database over a low-bandwidth wan-link. Any network interface that is supported under Linux will suffice for even the largest 10Gbit/sec deployments.</p>
<h3>Capture Network Interfaces</h3>
<p>Each site has widely varying requirements for capture interfaces, so it&#8217;s difficult to make generic recommendations. Consider the following factors:</p>
<ul>
<li>Have enough servers to put one at each site where there is a link to be monitored.</li>
<li>Have enough interfaces in each server to monitor the number of links at its site.</li>
<li>Ensure that each interface is fast enough to monitor the link assigned to it without dropping packets.</li>
<li>If any individual link exceeds about 200Mbits/sec, employ a capture framework that features load-balancing and select a compatible interface.</li>
</ul>
<h3>PCI Bus Speed</h3>
<p>At multi-Gbit/sec traffic rates, it is possible to saturate the PCI Express bus. Each PCI Express 16x slot has a bandwidth of 32Gbits/sec (4Gbytes/sec), 8x slots are half that, and 4x slots are half again.Theoretically, each slot has dedicated bandwidth such that two PCI Express 16x slots should have a combined bandwidth of 64Gbits/sec, but in practice the uplink between the PCI Express bus and the main memory bus is different in each motherboard chipset and may not be fast enough to provide the full theoretical bandwidth to every slot.</p>
<p>Bus saturation is only a potential issue at very high traffic rates, either involving multiple 10Gbit/sec links or inspection of a single 10Gbit/sec link with multiple sensor applications. Be prepared to split sensor functionality across multiple servers if testing shows unexpected performance bottlenecks that might be related to bus saturation. Hardware load-balancers such as those sold by Gigamon can be useful to duplicate and load-balance very high traffic rates to multiple 10Gbit/sec sensors.</p>
<h2>Putting It All Together</h2>
<p>There are many factors to consider listed above, but 80% or more of cases fall into a few broad classes that can be summed up briefly:</p>
<ol>
<li>One or two links, 200Mbits/sec or slower &#8211; Almost any server you buy today can handle this. Get 2-4 cores, 8 Gbytes of ram and 2-4 network interfaces of any type if you want to maximize your options.</li>
<li>One or two links, 200-400Mbits/sec &#8211; You should consider multi-snort load-balancing with PFRING or another suitable capture framework. If you&#8217;re going try to feed this traffic to a single-snort instance in order to avoid the maintenance overhead of multi-snort, get the highest-clocked fastest single-CPU that you can find, otherwise any system with sufficient RAM will work well.</li>
<li>One or two links, 500-1000Mbits/sec &#8211; You need multi-snort, consider pfring and with a TNAPI compatible network interface listed on ntop.org.  You&#8217;ll need 2-4 snort processes, which means 10-20Gbytes of ram and a quad-core system.</li>
<li>One or two links 1-10Gbit/sec &#8211; You definitely need multi-snort with high-performance capture hardware. I&#8217;m partial to Endace, but pfring with a 10G TNAPI-compatible card should also work. You need 1-core and 4Gbytes of ram for every 250Mbits/sec of traffic that you need to inspect. Alternatively, consider a Sourcefire system. If you&#8217;re just getting started with Snort this is going to be a big project to do on your own.</li>
<li>Many links or greater than 10Gbit/sec traffic &#8211; Try to break the problem down into multiple instances of the above cases. A Gigamon box at each site may give you the flexibility that you need to split the problem across multiple servers effectively. You also might also need a moderately high-performance database server, properly tuned and sized.</li>
</ol>
<h2>Wrapping Up</h2>
<p>Good luck with your new Snort server. Now go get some rules:</p>
<ul>
<li><a href="http://www.emergingthreats.net/index.php?option=com_content&amp;view=article&amp;id=16&amp;Itemid=38">Emerging Threats</a>: Excellent for detecting trojans and malware that have successfully compromised systems on your network and are &#8220;phoning home&#8221;. The ET rules are available free of charge and anyone can contribute fixes or new rules if you find a gap or problem with the ruleset.</li>
<li><a href="http://www.snort.org/snort-rules/#subscription">VRT Subscriber Feed</a>: Excellent for detection of exploits and attacks before they become compromised systems. The subscriber feed is developed and maintained by the experts on Sourcefire&#8217;s Vulnerability Research Team, and they charge $30/yr for a personal subscription or $500/yr for a business subscription.</li>
<li><a href="http://www.snort.org/snort-rules/#registered">VRT Registered Feed</a>: The registered feed contains the same rules as the subscriber feed, but updates are released 30-days after subscribers receive them. The registered feed is a reasonable alternative for personal use, but if you&#8217;re protecting a business I recommend the subscriber feed.</li>
<li><a href="http://www.emergingthreatspro.com/">ETPro</a>: ETPro aims to supplement the ET community sigs with attack/exploit sigs similar to what the VRT provides. Pricing is $35/yr for personal use or $350/yr for businesses. I haven&#8217;t used it, though it&#8217;s on my todo list to try.</li>
</ul>
<p>Once you&#8217;ve got things running, consider reading my slides on <a href="http://mikelococo.com/2011/04/snort-zabbix/">monitoring Snort performance with Zabbix</a> to see how well you sized your system.</p>
<h2 id="license">License and Feedback</h2>
<p>If you find errors in this guide or know of additions that would improve it, leave a comment below.</p>
<p><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img style="border-width: 0;" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" alt="Creative Commons License" /></a><br />
<span>Capacity Planning for Snort IDS</span> by <a rel="cc:attributionURL" href="http://mikelococo.com/2011/08/snort-capacity-planning/">Mike Lococo</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.<br />
Permissions beyond the scope of this license may be available at <a rel="cc:morePermissions" href="http://mikelococo.com/2011/08/snort-capacity-planning/#license">http://mikelococo.com/2011/08/snort-capacity-planning/#license</a>.</p>
<p>If you&#8217;d like to reuse the contents of this post but the cc-by-sa license doesn&#8217;t work for you for some reason, I&#8217;m happy to discuss offering the contents of this guide under almost any reasonable terms at no cost to individuals and corporations alike. Whether you work for Sourcefire, the OISF, or are just another community member writing a Snort guide, I&#8217;m happy to work something out that lets you use any portion of this post you need. Leave a comment below or contact me using the information on  the <a href="http://mikelococo.com/about/">about page</a> if you&#8217;d like to discuss.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2011/08/snort-capacity-planning/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Monitoring Snort Performance with Zabbix</title>
		<link>http://mikelococo.com/2011/04/snort-zabbix/</link>
		<comments>http://mikelococo.com/2011/04/snort-zabbix/#comments</comments>
		<pubDate>Tue, 12 Apr 2011 17:51:00 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>

		<guid isPermaLink="false">http://mikelococo.com/?p=345</guid>
		<description><![CDATA[In January I gave a presentation to the REN-ISAC on how to monitor the performance of Snort IDS systems. It covers: A comparison of high-performance capture-frameworks like vanilla-libpcap vs pfring vs dedicated capture cards from Endace or similar. An overview &#8230; <a href="http://mikelococo.com/2011/04/snort-zabbix/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>In January I gave a presentation to the <a href="http://ren-isac.net/">REN-ISAC</a> on how to monitor the performance of Snort IDS systems. It covers:</p>
<ul>
<li>A comparison of high-performance capture-frameworks like vanilla-libpcap vs pfring vs dedicated capture cards from Endace or similar.</li>
<li>An overview of the perfmon preprocessor and the &#8211;enable-perfprofiling configure-option that allow snort to log useful performance metrics.</li>
<li>A very brief overview of Zabbix as a system-monitoring framework, followed by some worked-examples of actual snort problems that are analyzed using data collected by Zabbix.</li>
</ul>
<p>The presentation-video is available only to REN-ISAC membership, but I&#8217;m making the <a href="http://mikelococo.com/files/2011/2011_01_25-snort_performance.pdf">slides and my notes</a> available here. They&#8217;re a bit rough, but if I get questions in the comments here or on the <a href="https://lists.sourceforge.net/lists/listinfo/snort-users">snort-users mailing list</a> I&#8217;ll try to be helpful. If there&#8217;s enough confusion based on the roughness of the slides, and enough interest to warrant it I can expand the presentation into a series of blog-posts to clarify some of the points that are unclear. In the meantime, have a look at an article by Juliet Kemp that fleshes out some of this material called <a href="http://olex.openlogic.com/wazi/2011/use-profiling-to-improve-snort-performance/">Use Profiling to Improve Snort Performance</a>.</p>
<p><strong>Update 2012-02-09:</strong> The notes for slide 16 of this deck assert that the averaging period for the &#8220;Drop Rate&#8221; provided by perfmon is the lifetime of the Snort process instead of the data-collection period, and warns of the type of confusion this can cause. That note is incorrect, the Drop Rate is averaged over the data-collection period like everything else. The misinformation was from my own research, dating back several versions of Snort. It&#8217;s possible that my original analysis was mistaken, or that I noticed a bug which has since been quietly fixed.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2011/04/snort-zabbix/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Relaunch</title>
		<link>http://mikelococo.com/2010/10/relaunch/</link>
		<comments>http://mikelococo.com/2010/10/relaunch/#comments</comments>
		<pubDate>Wed, 20 Oct 2010 03:45:36 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[maintenance]]></category>
		<category><![CDATA[vps]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/?p=328</guid>
		<description><![CDATA[My RSS subscriber has reminded me that my feeds have gone a little bit wild over the last couple of days as I&#8217;ve gone through old posts to retag and update dead links. That&#8217;s all finished now, promise. I&#8217;ve been &#8230; <a href="http://mikelococo.com/2010/10/relaunch/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>My RSS subscriber has reminded me that my feeds have gone a little bit wild over the last couple of days as I&#8217;ve gone through old posts to retag and update dead links. That&#8217;s all finished now, promise. I&#8217;ve been cleaning house and generally updating things&#8230;</p>
<ul>
<li>I&#8217;ve migrated from <a href="http://laughingsquid.us/">Laughing Squid</a> shared hosting to a <a href="http://www.linode.com/">linode</a> virtual private server. Laughing squid has been good to me over the years, but I&#8217;ve gotten to the point where I really want a root shell on my web-server. And VPS&#8217;s have gotten cheap enough now to be a reasonable option.</li>
<li>I&#8217;ve retired the <a href="http://mikelococo.com/projects/wucoco/">WuCoco Theme</a>. It&#8217;s also had a good run, but I don&#8217;t have time or interest in bringing it up to date with the latest WordPress features. I&#8217;m now using a mildly tweaked version of <a href="http://2010dev.wordpress.com/">Twenty Ten</a>, which will likely continue to evolve.</li>
<li>General post, page, and link pruning.</li>
</ul>
<p>This move should lay the groundwork to roll out some of the <a href="http://mikelococo.com/genealogy/">genealogy resources</a> I&#8217;ve talked about wanting to make. When I&#8217;m done, there should be some mailing-list archives, a wiki, and maybe an image gallery&#8230; hopefully all authenticated via OpenID. We&#8217;ll see how it pans out, but preliminary tests have gone well so far.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2010/10/relaunch/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Virtualization and Security Boundaries</title>
		<link>http://mikelococo.com/2009/06/virtualization-and-security-boundaries/</link>
		<comments>http://mikelococo.com/2009/06/virtualization-and-security-boundaries/#comments</comments>
		<pubDate>Mon, 08 Jun 2009 04:07:34 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[personal]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virtualization]]></category>

		<guid isPermaLink="false">http://mikelococo.com/?p=141</guid>
		<description><![CDATA[Virtualization security is coming up frequently in higher-ed security forums as folks scramble to understand best-practices before whatever path-of-least-resistance gets too entrenched to change.  Unfortunately, there&#8217;s almost no intermediate-level documents on virtualization security to help us wrap our heads around &#8230; <a href="http://mikelococo.com/2009/06/virtualization-and-security-boundaries/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Virtualization security is coming up frequently in higher-ed security forums as folks scramble to understand best-practices before whatever path-of-least-resistance gets too entrenched to change.  Unfortunately, there&#8217;s almost no intermediate-level documents on virtualization security to help us wrap our heads around the problem.  There&#8217;s plenty of introductory documents rehashing the same six bullet points over and over and there&#8217;s quite a lot of deep-dive technical material on various details, but almost no technical survey material for folks looking to bootstrap themselves on the topic.</p>
<p>I gave a <a href="http://net.educause.edu/SEC09/Program/1020687?PRODUCT_CODE=SEC09/SESS35">presentation</a> on virtualization security at the <a href="http://net.educause.edu/content.asp?SECTION_ID=394">Educause Security Professionals Conference</a> in April, and there seemed to be agreement and frustration about the lack of available survey material, which gave me the motivation I needed to polish up this paper for release.  It includes a basic taxonomy of virtualization technologies for security practitioners, an overview of attacks in virtualized environments, a list of best-practices with links to more detailed documents, and identifies areas where best practices haven&#8217;t yet been established.</p>
<p>Read <a href="http://mikelococo.com/files/2009/virtualization-and-security-boundaries.pdf">Virtualization and Security Boundaries</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2009/06/virtualization-and-security-boundaries/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fedora 8 on a Dell Latitude D620</title>
		<link>http://mikelococo.com/2008/03/fedora8-on-d620/</link>
		<comments>http://mikelococo.com/2008/03/fedora8-on-d620/#comments</comments>
		<pubDate>Mon, 24 Mar 2008 04:12:35 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[d620]]></category>
		<category><![CDATA[dell]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[hardware compatibility]]></category>
		<category><![CDATA[latitude]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2008/03/fedora8-on-d620/</guid>
		<description><![CDATA[Fedora 8 works quite well on the D620 right out of the box, and with a few tweaks can be just about fully supported. This guide summarizes what I&#8217;ve done to get things working to my satisfaction. It is not &#8230; <a href="http://mikelococo.com/2008/03/fedora8-on-d620/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Fedora 8 works quite well on the D620 right out of the box, and with a few tweaks can be just about fully supported.  This guide summarizes what I&#8217;ve done to get things working to my satisfaction.  It is not a step by step howto, but does attempt to link to more detailed resources when they are available.  The table below shows at a glance what is and isn&#8217;t working well on my system.  Most items worked immediately after install without manual intervention, italic items were made fully functional after some manual configuration, bold items have significant unsolved issues associated with them.</p>
<ul>
<li>Dual-core Processor: Both cores are detected on the 2.17GHz Intel Core Duo processor, the 32bit i686 smp kernel is installed and just works.  Dynamic CPU frequency scaling works well and if you wish to monitor/change the scaling behavior there&#8217;s a gnome panel applet to do so. I haven&#8217;t tried the 64 bit build, but most reports I&#8217;ve read indicate that it works well.</li>
<li>USB: Works, no config needed.</li>
<li>PCMCIA Slot: Works, no config needed.</li>
<li>Touchpad/Track Stick: Works, no config needed.  Install <a href="http://gsynaptics.sourceforge.jp/">gsynaptics</a> from Extras if you want to customize the trackpad behavior.</li>
<li><em>Suspend to Ram:</em> How this works will depend on the options you ordered your laptop with and the video drivers you&#8217;re using. My understanding is that it will work fine out of the box with Intel graphics or if you&#8217;re using the open source NV drivers with your NVidia card, however both of these options have fairly poor 3D performance. With some tweaking, suspend can also be made to work when using the proprietary drivers that will allow you to have strong 3D performance with one of the Quadro cards offered in the D620. <a href="http://www.clasohm.com/blog/one-entry?entry_id=56860">Classohm.org has detailed instructions</a> (for the D800/F7, but they apply here as well). Since the NVidia cards offered in the D620 are PCI-E and not AGP, you can skip the AGP tweaks and just create the scripts in /etc/pm/config.d/. I&#8217;ve tested suspend with kernel 2.6.23.9-85/smp.</li>
<li><strong>Hibernate to Disk:</strong> Untested, please report if this works out of the box or if you have a link with instructions on any required tweaking.</li>
<li>Ethernet: Works, no config needed.</li>
<li>Wireless Networking: I didn&#8217;t have to jump through any hoops, other than to <a href="http://fedoraproject.org/wiki/Tools/NetworkManager#head-fc3fe44e92c63867615113b1ef69cf4fc0dc03cf">enable the network manager applet</a> in order to avoid using iwconfig from the terminal all the time.  <a href="http://blog.adl.pl/fedora-8-on-dell-latitude-d620-and-inspiron-640m/62">Dawid Lorenz reports trouble that he solved</a> by switching from the built in iwl3945 to the freshrpm&#8217;s ipw3945, which have worked well for me on previous versions of Fedora. Note that the <a href="http://mikelococo.com/2006/10/fc5-on-d620/">awful Broadcom 4310</a> required ndis-wrapper to be supported in past versions of Fedora, I&#8217;m not certain what state it&#8217;s in today.</li>
<li>Bluetooth: Works, no config needed.</li>
<li>2D Video: Works, no config needed.</li>
<li><em>3D Acceleration:</em> The NVidia Quadro 110M works well after installing nvidia-x11-drv from freshrpms, bumping glxgears performance from ~900fps to ~2300fps.  Don&#8217;t forget to install kernel-devel for your kernel version and reboot. Note that installing the proprietary drivers will bork suspend/resume until you fix it using the instructions above.</li>
<li>External Monitor: If all you want is to switch to the external output instead of the internal LCD, you can do so easily right out of the box.  Use the screen resolution control panel to set your resolution, and Fn-F8 to toggle between the displays.  If you choose to install the NVidia driver, it includes a simple dialog for setting up multimonitor support using TwinView.  TwinView isn&#8217;t perfect, windows maximize dumbly (across both displays) and if the resolutions of the two monitors are mismatched there&#8217;s an area where it&#8217;s possible to move the mouse and place windows that doesn&#8217;t show up in any monitor.  All in all, it&#8217;s a bit lame but does get the job done in a pinch.</li>
<li>CD/DVD Burning: Works out of the box. At one time <a href="http://www.fedoraforum.org/forum/showthread.php?t=114586">this tweak</a> substantially improved burn speed and system responsiveness while burning, I haven&#8217;t tested to determine if it&#8217;s still needed. Post a comment if you&#8217;ve done testing.</li>
<li>Sound Playback: Works, no config needed.</li>
<li>Sound Recording: Works, no config needed.  If you&#8217;re not getting recorded sound, check the Volume Control app to make sure that capture is enabled and the recording level isn&#8217;t way down.</li>
<li>Volume Keys: Now work out of the box. You can mess with the key bindings in System &#8211;&gt; Preferences &#8211;&gt; Keyboard shortcuts but they control volume without any tweaking now.</li>
<li>Radio On/Off Switch: Works fine, and has a noticeable effect on battery life.  You may need to &#8220;up&#8221; the interface with the connection manager of your choice if you enable the radio while the system is running.</li>
<li>ACPI Power Management: All the power management features work (fan speed autoadjusts, cpu frequency scaling works, there&#8217;s a gnome applet to easily control it).</li>
<li><strong>Fingerprint Reader:</strong> Untested.</li>
<li><strong>Modem:</strong> Untested.</li>
</ul>
<h3>Output of lspci</h3>
<p><code>00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)<br />
00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)<br />
03:01.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 40)<br />
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)<br />
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</code></p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2008/03/fedora8-on-d620/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multihop SSH with Putty/WinSCP</title>
		<link>http://mikelococo.com/2008/01/multihop-ssh/</link>
		<comments>http://mikelococo.com/2008/01/multihop-ssh/#comments</comments>
		<pubDate>Thu, 10 Jan 2008 04:38:41 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[bouncing]]></category>
		<category><![CDATA[chaining]]></category>
		<category><![CDATA[putty]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[stacking]]></category>
		<category><![CDATA[winscp]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2008/01/multihop-ssh/</guid>
		<description><![CDATA[Introduction It&#8217;s not always possible to ssh to a host directly. Many networks require high-value systems to be accessed via an intermediate bastion/proxy host that receives extra attention in terms of security controls and log monitoring. The added security provided &#8230; <a href="http://mikelococo.com/2008/01/multihop-ssh/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<h3>Introduction</h3>
<p>It&#8217;s not always possible to ssh to a host directly. Many networks require high-value systems to be accessed via an intermediate bastion/proxy host that receives extra attention in terms of security controls and log monitoring. The added security provided by this connection bouncing comes with a cost in convenience, though. It requires multiple logins to access the protected systems and substantially complicates scp/stfp file transfers.</p>
<p>Fortunately, there are a number of ways to automate connection bouncing and make it as convenient as direct connection. There are already a number of web-sites detailing the approaches to this issue, and I won&#8217;t repeat their contents, to get a broad overview of the topic read the following:</p>
<ul>
<li><a href="http://www.hackinglinuxexposed.com/articles/20040830.html">SSH Bouncing Part 1</a> from Hacking Linux Exposed</li>
<li><a href="http://www.hackinglinuxexposed.com/articles/20040923.html">SSH Bouncing Part 2</a> from Hacking Linux Exposed</li>
<li><a href="http://samba.anu.edu.au/rsync/firewall.html">Using rsync through a firewall</a>, the concepts in this document apply to all SSH setups, not just those integrating rsync</li>
</ul>
<h3>Terminology</h3>
<h4>SSH Connection &#8220;Chaining&#8221;</h4>
<p>Connection &#8220;chaining&#8221; refers to any approach that involves sshing to an intermediate host, and then sshing from the intermediate host to the next host (for example: <tt>ssh 1 'ssh 2 "ssh 3"'</tt>). This solution is attractive for setups with many hops because it&#8217;s easy to extend, for example <a href="http://www.cskk.ezoshosting.com/cs/css/ssh.html#sshto__bangstyle_ssh_to_do_multihop_ssh">sshto</a> makes this very easy. The primary disadvantage is that end-to-end encryption is lost. The connection is decrypted by every host in the chain, and an attacker with sufficient privilege on an intermediate system can sniff the connection without compromising either of the endpoints. I consider this to be a significant failing, and have a strong preference for &#8220;stacked&#8221; connections wherever they are logistically feasible.</p>
<h4>SSH Connection &#8220;Stacking&#8221;</h4>
<p>Connection &#8220;stacking&#8221; refers to any solution that involves tunneling ssh connections inside each other. &#8220;Nesting&#8221; strikes me as a better term, but stacking seems to be more widely agreed upon. It is typically implemented with proxy-commands or with ssh port-forwarding. It can be more difficult to manage for connections with many hops, and it forces one of the endpoints to bear the encryption load of all the connections (in chained setups, the load is spread evenly among all the hosts in the chain). It does maintain end-to-end encryption, preventing connection/credential sniffing by intermediate hosts.</p>
<h3>My Setup</h3>
<p>The key properties for my setup are:</p>
<ul>
<li>End-to-end encryption is maintained using stacked connections</li>
<li>Only a single intermediate host is involved, the proxy features I utilize do not trivially scale to longer connection paths</li>
<li>Putty is used for shell connections, and WinSCP is used for scp/sftp connections</li>
<li>No special software is required beyond a default Putty installation, WinSCP, and an SSH server with port forwarding enabled. Specifically, netcat is not required on the intermediate host as is common with ProxyCommand setups.</li>
</ul>
<h4>WinSCP Config</h4>
<p>The WinSCP Config is quite simple and utilizes its &#8220;tunnel&#8221; feature. Open WinSCP and configure a saved session for the final destination host as follows:</p>
<ol>
<li>On the Session page, fill in the hostname and user name for the final destination host. Leave the password blank.</li>
<li>Check the &#8220;Advanced options&#8221; box in the login dialog.</li>
<li>Select the Connection &#8211;&gt; Tunnel page.</li>
<li>Check the &#8220;Connect through SSH tunnel&#8221; box.</li>
<li>Fill in the Host name and user name of the intermediate host. Leave the password blank.</li>
<li>Save the session using the button in the lower right-hand corner of the window.</li>
</ol>
<p>When you log in using the new profile, you will be prompted for two passwords. The first is for your account on the intermediate host, and the second is for your account on the final-destination host. After login, the bounce is entirely transparent and WinSCP works as if you had connected directly to the final-destination host. The connection process can be made even more transparent and secure by using public key authentication with Pageant instead of passwords.</p>
<h4>Putty Config</h4>
<p>The Putty setup is slightly more complicated and requires that public key authentication be used on the intermediate host. It utilizes Putty&#8217;s &#8220;local proxy&#8221; feature, which allows you to specify an arbitrary command on the local machine to act as a proxy. Instead of creating a TCP connection, PuTTY will communicate using the proxy program&#8217;s standard input and output streams. Our local proxy will be plink, which is a command-line ssh connection program included in the Putty default installation. Plink&#8217;s -nc option provides functionality similar to the ProxyCommand/netcat approach, but does so using the ssh server&#8217;s native port-forwarding interface and does not require that netcat be installed on the intermediate system. To set things up, configure a saved session for the final destination host:</p>
<ol>
<li><a href="http://www.ualberta.ca/CNS/RESEARCH/LinuxClusters/pka-putty.html">Configure public key authentication</a> for the intermediate host and make sure it works.</li>
<li>Start putty and on the &#8220;Session&#8221; page of the &#8220;Putty Configuration Dialog&#8221; that appears, fill in the host name and user name for the final destination host.</li>
<li>Switch to the Connection &#8211;&gt; Proxy page, select &#8220;Local&#8221; as the proxy type enter the following as the local proxy command: <tt>plink.exe intermediate.proxy.host -l username -agent -nc %host:%port\n</tt></li>
<li>Save the session.</li>
</ol>
<p>Remember to replace &#8220;intermediate.proxy.host&#8221; with your intermediate hostname and &#8220;username&#8221; with your real username. &#8220;%host&#8221; and &#8220;%port&#8221; are variables that putty will feed to plink at connection time, so leave those as is. If all is working properly, when you log in using the new profile plink will handle the login to the intermediate system silently. Putty isn&#8217;t smart enough to prompt if the proxy command requires user input, so you&#8217;ll get a connection error if public key authentication on the intermediate host isn&#8217;t working. If you use password authentication on the final destination host you&#8217;ll be prompted for your password, or if you use pubkey authentication there as well you&#8217;ll land at a prompt with no fuss at all.</p>
<p>If you have trouble, make sure plink is executing properly. You may need to enter the full pathname, usually c:\program files\putty\plink.exe. You can also try executing the plink command from a prompt, remembering to substitute the %host and %port values of your final destination host. If it&#8217;s working properly, you&#8217;ll be logged into the intermediate system with your pageant-cached private key, and instead of a prompt you&#8217;ll be presented with the SSH banner for your final destination system.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2008/01/multihop-ssh/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>SSH Key Management and Presence</title>
		<link>http://mikelococo.com/2007/12/ssh-presence/</link>
		<comments>http://mikelococo.com/2007/12/ssh-presence/#comments</comments>
		<pubDate>Mon, 10 Dec 2007 04:49:20 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[screensaver]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[ssh-keys]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2007/12/ssh-key-management-and-presence/</guid>
		<description><![CDATA[There are a number of excellent guides to setting up public key authentication for ssh, but they tend to stop short of describing how to integrate presence events like a screensaver turning on. It&#8217;s a topic that isn&#8217;t possible to &#8230; <a href="http://mikelococo.com/2007/12/ssh-presence/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>There are a number of excellent guides to setting up public key authentication for ssh, but they tend to stop short of describing how to integrate presence events like a screensaver turning on.  It&#8217;s a topic that isn&#8217;t possible to cover in a generic way, since it depends heavily on your operating system, distribution, desktop environment, and preferred shell.  I present here the information I&#8217;ve pulled together to get things running under Linux, specifically Fedora 8 with Gnome and Bash.</p>
<p>First off, if you&#8217;re not already quite familiar public key authentication, go read the three part IBM developerWorks series on the topic (<a href="http://www.ibm.com/developerworks/library/l-keyc.html">1</a>,<a href="http://www.ibm.com/developerworks/library/l-keyc.html"> </a><a href="http://www.ibm.com/developerworks/library/l-keyc2/">2</a>, <a href="http://www.ibm.com/developerworks/linux/library/l-keyc3/">3</a>), which is the best primer I&#8217;ve found.  I&#8217;m using public key authentication with encrypted keys, am caching my credentials with ssh-agent, and am using keychain as my interface to ssh-agent. My primary goal was to automatically run <tt>keychain --clear</tt> to clear my credentials any time I left my system unattended.  I also outline how to run <tt>keychain ~/.ssh/id_rsa</tt> when you return to your system (or whenever you open a shell) in order to reload your ssh key.</p>
<h3>Login</h3>
<p>When I log in to my system, keychain runs and does some housekeeping.  It starts an ssh-agent process if one isn&#8217;t already running and prompts for the passwords to my ssh keys if they aren&#8217;t already loaded, or if all that has already been done it just reports its status and exits. The following lines can be placed in ~/.bash_profile which is executed when you log into your system (via remote ssh session, text console, and oddly enough gnome executes bash_profile on login as well).</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;"><span style="color: #000000; font-weight: bold;">if</span> <span style="color: #7a0874; font-weight: bold;">&#91;</span> <span style="color: #ff0000;">&quot;<span style="color: #007800;">$PS1</span>&quot;</span> <span style="color: #7a0874; font-weight: bold;">&#93;</span>; <span style="color: #000000; font-weight: bold;">then</span>
<span style="color: #000000; font-weight: bold;">/</span>usr<span style="color: #000000; font-weight: bold;">/</span>bin<span style="color: #000000; font-weight: bold;">/</span>keychain ~<span style="color: #000000; font-weight: bold;">/</span>.ssh<span style="color: #000000; font-weight: bold;">/</span>id_rsa
<span style="color: #7a0874; font-weight: bold;">source</span> ~<span style="color: #000000; font-weight: bold;">/</span>.keychain<span style="color: #000000; font-weight: bold;">/</span>yourhostname-sh
<span style="color: #000000; font-weight: bold;">fi</span></pre></div></div>

<p>The &#8220;if&#8221; statement ensures that keychain is only run for interactive shells.  Because keychain generates output on execution it can confuse some programs that run non-interactively, notably <a href="http://www.openssh.com/faq.html#2.9">sftp breaks</a> if you don&#8217;t do this.</p>
<h3>New Shell</h3>
<p>I actually like keychain to run <em>every</em> time I start a new shell, not just when I first log in. This means that I can clear my credentials manually if I won&#8217;t be using ssh for a while and when I open a fresh terminal window (or &#8220;window&#8221; in a screen session, or whatever) keychain automatically prompts me for my password.  This can be done by placing the same lines from above in ~/.bashrc instead of bash_profile (bashrc is executed from bash_profile, so you only need one or the other).</p>
<h3>Screensaver</h3>
<p>When my screensaver turns on, it&#8217;s an indication that I&#8217;m away from my desk and that my credentials should be cleared. To my knowledge, gnome-screensaver does not provide per-user screensaver-on and screensaver-off scripts where you can easily add these sorts of things (it should, if you ask me).  It does, however, emit a DBUS signal that you can listen for and act on. I found some folks using <a href="http://nxsy.org/blog/archives/2007/03/20/getting-amarok-to-pause-when-the-screen-locks-using-python-of-course#comment-5167" class="broken_link" rel="nofollow">python scripts</a> to handle similar needs and adapted them for my purpose, others have done similar things with <a href="http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#Is_there_a_way_to_perform_actions_when_the_screensaver_activates_or_deactivates.3F__Or_when_the_session_becomes_idle.3F">bash script</a>. Once you&#8217;ve customized your DBUS signal listener script, add it to your default gnome session using System &#8211;&gt; Preferences &#8211;&gt; Personal &#8211;&gt; Sessions so that it&#8217;s automatically started when you log in.</p>

<div class="wp_syntax"><div class="code"><pre class="python" style="font-family:monospace;"><span style="color: #808080; font-style: italic;">#!/usr/bin/python</span>
<span style="color: #ff7700;font-weight:bold;">import</span> dbus
<span style="color: #ff7700;font-weight:bold;">from</span> dbus.<span style="color: black;">mainloop</span>.<span style="color: black;">glib</span> <span style="color: #ff7700;font-weight:bold;">import</span> DBusGMainLoop
<span style="color: #ff7700;font-weight:bold;">import</span> gobject
<span style="color: #ff7700;font-weight:bold;">import</span> <span style="color: #dc143c;">os</span>
&nbsp;
<span style="color: #ff7700;font-weight:bold;">def</span> clear_keychain<span style="color: black;">&#40;</span>state<span style="color: black;">&#41;</span>:
<span style="color: #483d8b;">&quot;&quot;&quot;Called when screensaver on/off events occur&quot;&quot;&quot;</span>
&nbsp;
<span style="color: #808080; font-style: italic;"># clear ssh keys when screensaver turns on</span>
<span style="color: #ff7700;font-weight:bold;">if</span> state == <span style="color: #008000;">True</span>:
<span style="color: #dc143c;">os</span>.<span style="color: black;">system</span><span style="color: black;">&#40;</span><span style="color: #483d8b;">'/usr/bin/keychain --clear'</span><span style="color: black;">&#41;</span>
&nbsp;
<span style="color: #808080; font-style: italic;"># Load ssh keys when screensaver turns off</span>
<span style="color: #808080; font-style: italic;">#     if state == False:</span>
<span style="color: #808080; font-style: italic;">#          os.system('/usr/bin/keychain id_rsa')</span>
&nbsp;
<span style="color: #808080; font-style: italic;"># Connect to the gnome session bus:</span>
dbus.<span style="color: black;">mainloop</span>.<span style="color: black;">glib</span>.<span style="color: black;">DBusGMainLoop</span><span style="color: black;">&#40;</span>set_as_default=<span style="color: #008000;">True</span><span style="color: black;">&#41;</span>
bus = dbus.<span style="color: black;">SessionBus</span><span style="color: black;">&#40;</span><span style="color: black;">&#41;</span>
&nbsp;
<span style="color: #808080; font-style: italic;"># Listen for SessionIdleChanged signals</span>
bus.<span style="color: black;">add_signal_receiver</span><span style="color: black;">&#40;</span>clear_keychain,<span style="color: #483d8b;">'SessionIdleChanged'</span>,<span style="color: #483d8b;">'org.gnome.ScreenSaver'</span><span style="color: black;">&#41;</span>
loop = gobject.<span style="color: black;">MainLoop</span><span style="color: black;">&#40;</span><span style="color: black;">&#41;</span>
loop.<span style="color: black;">run</span><span style="color: black;">&#40;</span><span style="color: black;">&#41;</span></pre></div></div>

<h3>Logout</h3>
<p>Logging out of the system (whether from a remote ssh session, a local text console, or a graphical gnome session) is an indication that my workstation is going to be idle for a while and that my credentials should be cleared. This can be (mostly) accomplished by making an addition to ~/.bash_logout. This file is run any time a non-gnome login shell exits, like a remote ssh session or a local text console session (but not terminal windows in gnome, screen windows, or other non-login shells):</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;"><span style="color: #000000; font-weight: bold;">/</span>usr<span style="color: #000000; font-weight: bold;">/</span>bin<span style="color: #000000; font-weight: bold;">/</span>keychain <span style="color: #660033;">--clear</span></pre></div></div>

<p>For some utterly insane reason, gnome doesn&#8217;t execute bash_logout even though it <strong>does</strong> execute bash_profile on login, and it doesn&#8217;t provide a sane alternative.  The only method I&#8217;m aware of for running a script on gnome-logout involves xsession hackery, but I&#8217;ve punted on this issue since I rarely exit my gnome session. If you find an elegant solution, leave a comment.</p>
<h3>Other SSH Tips</h3>
<ul>
<li><strong>SSH Aliases:</strong> This is somewhat off-topic for this article, but is such a great timesaver that it bears a quick mention in any article about ssh. You can <a href="http://www.innovatingtomorrow.net/2008/01/21/type-less-ssh-aliases" class="broken_link" rel="nofollow">define short names</a> for hosts you ssh to often in ~/.ssh/config.</li>
<li><strong>Clearing Credentials At Login:</strong> An alternative to all of this, and one of the strategies suggested in the developerWorks series is to start keychain with the &#8211;clear option in .bash_profile or wherever you call it from.  The assumption is that by clearing your credentials on login instead of logout, you can stay authenticated all the time (and gain the benefit of being able to run cron scripts) but an attacker will lose access to your credentials the moment they try to access your account.  It&#8217;s an interesting strategy, but not one I&#8217;m entirely comfortable with. I prefer to clear my credentials when they&#8217;re not being used, and designate special-purpose keys with appropriate <a href="http://joey.kitenet.net/blog/entry/locking_down_ssh_authorized_keys/">constraints</a> for <a href="http://troy.jdmz.net/rsync/index.html">cron jobs</a>.</li>
</ul>
<h3>Conclusion</h3>
<p>With the tips in the developerWorks series, and the information in this article, you can have an incredibly convenient ssh key management setup while you&#8217;re using your computer and know that your credentials will be automatically cleared when you&#8217;re away from your system.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2007/12/ssh-presence/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New York City?!!???!</title>
		<link>http://mikelococo.com/2007/04/new-york-city/</link>
		<comments>http://mikelococo.com/2007/04/new-york-city/#comments</comments>
		<pubDate>Sun, 15 Apr 2007 16:44:25 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[move]]></category>
		<category><![CDATA[new job]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2007/04/new-york-city/</guid>
		<description><![CDATA[Making good on the heels of my CISSP certification, I&#8217;m going to be joining the Security Services group at NYU in May as a Senior Network Security Analyst. Security Services is charged to protect the entire NYU network, which provides &#8230; <a href="http://mikelococo.com/2007/04/new-york-city/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Making good on the heels of my <a href="http://mikelococo.com/2006/12/cissp-certification/">CISSP certification</a>, I&#8217;m going to be joining the <a href="http://www.nyu.edu/its/security/">Security Services group at NYU</a> in May as a Senior Network Security Analyst.  Security Services is charged to protect the entire NYU network, which provides connectivity to around 40,000 nodes.</p>
<p>I&#8217;m incredibly excited about the move.  Since my partner lives in New York, I&#8217;ve been job hunting there for almost a year and half and I&#8217;ve found that it&#8217;s a very competitive market.  I needed to do a lot of professional development in order to be considered seriously for the positions I wanted, and this was the most interesting position I saw or applied for in my entire search.  To have been hired into it just fantastic.</p>
<p>So anyhoo&#8230; I&#8217;ll be selling or giving away most of my stuff this month so Laura, Kip, and I can fit into an apartment the size of a shoebox.  Have a gander if you need anything.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2007/04/new-york-city/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Poor Battery Life on Latitude D620</title>
		<link>http://mikelococo.com/2007/03/d620-battery-life/</link>
		<comments>http://mikelococo.com/2007/03/d620-battery-life/#comments</comments>
		<pubDate>Sun, 04 Mar 2007 20:21:55 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[battery]]></category>
		<category><![CDATA[d620]]></category>
		<category><![CDATA[dell]]></category>
		<category><![CDATA[latitude]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2007/03/d610-battery-life/</guid>
		<description><![CDATA[Dawid Lorenz, myself, and a number of other folks (read the comments on Dawid&#8217;s page, and also on the product pages for the D620 batteries) have all experienced poor battery life on Dell Latitude D620&#8242;s that are typically less than &#8230; <a href="http://mikelococo.com/2007/03/d620-battery-life/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.adl.pl/linux-power-management-and-laptop-battery-life/49">Dawid Lorenz</a>, <a href="http://mikelococo.com/2007/01/fc6-on-d620/">myself</a>, and a number of other folks (read the comments on Dawid&#8217;s page, and also on the product pages for the D620 batteries) have all experienced poor battery life on Dell Latitude D620&#8242;s that are typically less than six months old.  There may or may not be a high failure rate for this battery model, and this page details my experiences in diagnosing the health of my battery and obtaining a replacement under warranty.</p>
<h3>Determining Battery Health</h3>
<p>There are several methods of determining your battery&#8217;s capacity relative to it&#8217;s initial specification (aka &#8220;health&#8221;).</p>
<ul>
<li>Press and hold the status button located on the bottom of your battery.  The five LED lights will initially display your battery&#8217;s current charge (five lights is charged, zero lights is discharged), and if you continue pressing the status button for three seconds the lights will blink off and back on again, now displaying the health of your battery.  If zero lights appear your battery is operating at greater than 80% of its specified capacity, if five lights appear your battery is operating at less than 60% of its specified capacity.  This information was pulled from the <a href="http://support.dell.com/support/edocs/systems/latd620/en/UG/battery.htm">D620 User Guide</a>.</li>
<li>If you enter the system BIOS by pressing &#8220;F2&#8243; during the Dell logo while booting, there is a &#8220;Battery Health&#8221; option under the &#8220;Sytem&#8221; menu which gives a qualitative assessment of battery health.</li>
<li>The power manager under FC6 tracks the maximum capacity of your battery at its last full charge and generates a health percentage based on the factory spec charge for your battery.  To view this information, right-click the battery meter in your gnome panel, select &#8220;Information&#8221;, and expand the &#8220;More&#8221; area of the &#8220;Device Information&#8221; panel.</li>
<li>If you kept your initial Windows XP install, there is a battery health meter under the Dell Quickset applet in the lower right hand corner of the screen that gives the same information that is available through the system BIOS.</li>
</ul>
<h3>Obtaining a Replacement Battery</h3>
<p>Of course, you always have the option of purchasing a replacement battery from Dell (<a href="http://accessories.us.dell.com/sna/productdetail.aspx?c=us&amp;l=en&amp;cs=19&amp;sku=312-0386">9-cell</a> or <a href="http://accessories.us.dell.com/sna/productdetail.aspx?c=us&amp;l=en&amp;cs=19&amp;sku=312-0383">6-cell</a>), or simply living with degraded battery life.  There are some circumstances where you may be able to obtain a replacement under warranty, though.  If the BIOS/Quickset health gauges are showing the battery as failed even though it&#8217;s less than a year old, Dell will replace it under warranty.  According to the phone rep that I spoke to, a battery is considered to have failed when operating at less than 50% of its rated capacity.  When I called, my battery was five months old and operating at 50%-60% of it&#8217;s capacity (5 death lights, BIOS noted lowered battery life but did not pronounce failure, FC6 power manager rated health at 56%, observed battery life was 50%-60% of expected).  I was able to successfully make the case that the battery was clearly borderline and would certainly be replaced within a month or two, and that doing so now was an opportunity to provide excellent customer service whereas forcing me to wait would serve no purpose other than irritating me.  To his credit, the phone rep immediately acknowledged that my line of thinking was reasonable, spoke to a supervisor, and was able to authorize the early replacement.</p>
<h3>Conclusion</h3>
<p>I love my laptop, and in general I&#8217;m very happy with it.  It does look like there&#8217;s a trend toward premature battery failure, though, and if your situation is severe enough you may be eligible for a warranty replacement.  Once your replacement arrives, go read about how to <a href="http://blog.adl.pl/linux-power-management-and-laptop-battery-life/49">monitor and optimize battery performance</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2007/03/d620-battery-life/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>Fedora Core 6 on a Dell Latitude D620</title>
		<link>http://mikelococo.com/2007/01/fc6-on-d620/</link>
		<comments>http://mikelococo.com/2007/01/fc6-on-d620/#comments</comments>
		<pubDate>Wed, 17 Jan 2007 05:04:39 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[d620]]></category>
		<category><![CDATA[dell]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[hardware compatibility]]></category>
		<category><![CDATA[latitude]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2007/01/fc6-on-d620/</guid>
		<description><![CDATA[Dawid Lorenz already has a very comprehensive set of notes on running Fedora Core 6 on the Dell Latitude D620, but I&#8217;m going to drop in my two cents as well for variety&#8217;s sake. FC6 works quite well on the &#8230; <a href="http://mikelococo.com/2007/01/fc6-on-d620/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Dawid Lorenz already has a very comprehensive set of notes on running <a href="http://blog.adl.pl/fedora-core-6-on-dell-latitude-d620/18">Fedora Core 6 on the Dell Latitude D620</a>, but I&#8217;m going to drop in my two cents as well for variety&#8217;s sake.</p>
<p>FC6 works quite well on the D620 right out of the box, and with a few tweaks can be just about fully supported.  This guide summarizes what I&#8217;ve done to get things working to my satisfaction.  It is not a step by step howto, but does attempt to link to more detailed resources when they are available.  The list below shows at a glance what is and isn&#8217;t working well on my system.  Most items worked immediately after install without manual intervention, italic items were made fully functional after some manual configuration, and bold items have significant unsolved issues associated with them.</p>
<ul>
<li>Dual-core Processor: Both cores are detected on the 2.17GHz Intel Core Duo processor, the 32bit i686 smp kernel is installed and just works.  Dynamic CPU frequency scaling works well and if you wish to monitor/change the scaling behavior there&#8217;s a gnome panel applet to do so.</li>
<li>USB: Works, no config needed.</li>
<li>PCMCIA Slot: Works, no config needed.</li>
<li>Touchpad/Track Stick: Works, no config needed.  Install <a href="http://gsynaptics.sourceforge.jp/">gsynaptics</a> from Extras if you want to customize the trackpad behavior, or copy/modify <a href="http://blog.adl.pl/fedora-core-6-on-dell-latitude-d620/18">Dawid&#8217;s xorg.config settings</a> (search for &#8220;touchpad&#8221;).</li>
<li><em>Suspend to Ram:</em> Works with kernel 2.6.18-1.2869, wireless networking needs to be restarted on wakeup and you need to nudge the volume control to wake up the soundcard.</li>
<li><strong>Hibernate to Disk:</strong> Doesn&#8217;t work, system hangs during hibernation and needs a hard reset.  This worked in Fedora Core 5, so I imagine it will get fixed again relatively soon.</li>
<li>Ethernet: Works, no config needed.</li>
<li><em>Wireless Networking:</em> Install dkms-ipw3945, ipw3945d and ipw3945-firmware from freshrpms, install the kernel-devel package for your kernel, and reboot.  Once you&#8217;re configured, don&#8217;t forget to <a href="http://fedoraproject.org/wiki/Tools/NetworkManager#head-fc3fe44e92c63867615113b1ef69cf4fc0dc03cf">enable the network manager applet</a> so you don&#8217;t have to iwconfig from the terminal all the time.  The Intel 3945 has much better linux support than the <a href="http://mikelococo.com/2006/10/fc5-on-d620/">awful Broadcom 4310</a> in the Dell Truemobile 1390 that was previously installed in this laptop.</li>
<li>Bluetooth: Works, no config needed.</li>
<li>2D Video: Works, no config needed.</li>
<li><em>3D Acceleration:</em> The NVidia Quadro 110M works well after installing nvidia-x11-drv from freshrpms.  Don&#8217;t forget to install kernel-devel for your kernel version and reboot.  <strike>Battery life drops by about 40% while running the NVidia driver, even if you&#8217;re not doing 3D work.</strike>  <a href="http://mikelococo.com/2007/03/d620-battery-life/">I had a bad battery</a>.</li>
<li>External Monitor: If all you want is to switch to the external output instead of the internal LCD, you can do so easily right out of the box.  Use the screen resolution control panel to set your resolution, and Fn-F8 to toggle between the displays.  If you choose to install the NVidia driver, it includes a simple dialog for setting up multimonitor support using TwinView.  TwinView isn&#8217;t perfect, windows maximize dumbly (across both displays) and if the resolutions of the two monitors are mismatched there&#8217;s an area where it&#8217;s possible to move the mouse and place windows that doesn&#8217;t show up in any monitor.  All in all, it&#8217;s a bit lame but does get the job done in a pinch.</li>
<li>CD/DVD Burning: Works out of the box, but <a href="http://www.fedoraforum.org/forum/showthread.php?t=114586">this tweak</a> substantially improves burn speed and system responsiveness while burning.</li>
<li>Sound Playback: Works, no config needed.</li>
<li>Sound Recording: Works, no config needed.  If you&#8217;re not getting recorded sound, check the Volume Control app to make sure that capture is enabled and the recording level isn&#8217;t way down.</li>
<li><em>Volume Keys:</em> Go into System &#8211;> Preferences &#8211;> Keyboard shortcuts and assign the multimedia keys to vol down/up/mute (or whatever you want them to do).</li>
<li>Radio On/Off Switch: Works fine, and has a noticeable effect on battery life.  You may need to &#8220;up&#8221; the interface with the connection manager of your choice if you enable the radio while the system is running.</li>
<li>ACPI Power Management: All the power management features work (fan speed autoadjusts, cpu frequency scaling works, there&#8217;s a gnome applet to easily control it)<strike>, but battery life is inexplicably poor.  Under FC5, my battery life was over 4 hours with a 9-cell battery, wifi/bt off, backlight dimmed, and cpu locked to 1GHz.  After migrating to FC6, battery life is less than 3 hours and the laptop runs noticeably warmer when performing routine tasks.</strike>  <a href="http://mikelococo.com/2007/03/d620-battery-life/">I had a bad battery</a>.</li>
<li><strong>Fingerprint Reader:</strong> Untested.</li>
<li><strong>Modem:</strong>Untested.</li>
</ul>
<h3>Output of lspci</h3>
<p><code>00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 01)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)<br />
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 110M / GeForce Go 7300 (rev a1)<br />
03:01.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 40)<br />
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)<br />
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</code></p>
<h3>Useful Links</h3>
<ul>
<li><a href="http://blog.adl.pl/fedora-core-6-on-dell-latitude-d620/18">Fedora Core 6 on the D620</a></li>
<li><a href="http://mikelococo.com/2006/10/fc5-on-d620/">My previous guide to Fedora Core 5 on the D620</a></li>
<li><a href="http://www.linux-on-laptops.com/dell.html">Linux on Laptops page for Dells</a> (search the page for 620)</li>
<li><a href="http://javier.rodriguez.org.mx/index.php/linux/debian-gnulinux-on-dell-d620/">Debian on the D620</a></li>
<li><a href="http://www.oiepoie.nl/linux_on_d620/">Another guide to Fedora Core 5 on the D620</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2007/01/fc6-on-d620/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>CISSP Certification</title>
		<link>http://mikelococo.com/2006/12/cissp-certification/</link>
		<comments>http://mikelococo.com/2006/12/cissp-certification/#comments</comments>
		<pubDate>Sat, 16 Dec 2006 21:46:13 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[cissp]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/12/cissp-certification/</guid>
		<description><![CDATA[As of Thursday I&#8217;ve fulfilled all the requirements for CISSP certification, my papers should be in the mail by Monday. I haven&#8217;t wanted to talk about it online until I had some firm results, but folks who know me in &#8230; <a href="http://mikelococo.com/2006/12/cissp-certification/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>As of Thursday I&#8217;ve fulfilled all the requirements for <a href="https://www.isc2.org/cissp/">CISSP certification</a>, my papers should be in the mail by Monday.  I haven&#8217;t wanted to talk about it online until I had some firm results, but folks who know me in meatspace know I&#8217;ve been studying on and off since August.  I&#8217;m a little <a href="http://mikelococo.com/2006/05/aplus/">more amped about this credential</a> because they&#8217;re not handed out like party-favors and people who have them seem to be doing interesting things.</p>
<p>Although my study schedule was 4 months, my intensity level for the second and third month varied a lot.  I also spent a lot of time doing cover-to-cover reading, which in retrospect isn&#8217;t a terribly efficient way to approach an exam with this much breadth.  I kind of wish I had done more practice tests early in my study process so I could have spent more time on weak areas and less time agonizing over the subtleties of topics that I already fundamentally understood.</p>
<p>Most folks use a number of study resources, and I was no exception:</p>
<ul>
<li>I started with Shon Harris&#8217; <a href="http://www.amazon.com/CISSP-All-One-Guide-Third/dp/0072257121/">CISSP All in One Exam Guide</a>.  Like most Osbourne books, it&#8217;s a little bit chatty, has some laughably bad diagrams, and more than it&#8217;s share of ambiguities, errors, and bad practice questions.  Even still it&#8217;s a pretty good book, especially if you need to bootstrap yourself a bit before you feel prepared for the more no-nonsense books.</li>
<li>Once I felt comfortable with Harris, I started working through the Hansche/Berti/Hare <a href="http://www.amazon.com/Official-ISC-Guide-CISSP-Exam/dp/084931707X/">Official (ISC)<sup>2</sup> Guide to the CISSP Exam</a>, published by Auerbach.  Although dry, I think it&#8217;s important to work with this book.  Because of the strict confidentiality requirements surrounding the test it&#8217;s hard to get reliable information about which topics are emphasized, what the editorial style of the questions is like, and how to disambiguate words that may have a number of meanings depending on what part of the industry you work in but which are used in a specific and consistent way by (ISC)<sup>2</sup>.  I found that I simply absorbed a lot of useful information about the (ISC)<sup>2</sup> writing style when reading this book that gave me a tangible edge in the exam room.  Plus it&#8217;s generally well done and has the best practice questions I was able to find.  The worst thing I can say about it is that the CBK sections at the end of each chapter are fantastically vague, needlessly scary, and completely useless.  They&#8217;re easy to ignore, though, and that&#8217;s what I recommend doing with them.</li>
<li><a href="http://cccure.org/">Cccure.org</a> is an excellent resource for free practice questions.  Quality does vary, but at the high end is very good and on average is pretty ok.</li>
<li>I also bought a set of <a href="http://www.boson.com/Product/132.html">Boson</a> practice questions and was extremely disappointed, to the point of not even using most of them.  Some of the highlights of my Boson experience were:
<ol>
<li>A fill in the blank question with a nine word answer that needed to be typed exactly to be graded correctly.  The answer was obviously not a standard phrase worth memorizing, and <a href="https://www.isc2.org/cgi-bin/content.cgi?page=807#format">the CISSP exam is entirely multiple choice</a>.</li>
<li>A multiple-choice question that offered only one answer option&#8230; er&#8230; I mean&#8230; a single-choice question&#8230; or&#8230; um&#8230; would that just be a statement?</li>
<li>An email conversation with a Boson support rep that took three rounds of explanation before understanding why a multiple-choice question with no alternate options is defective, and who offered to take no corrective action other than passing the complaint up the chain.</li>
</ol>
</li>
<li>I did a lot of Googling to fill in gaps on topics I wasn&#8217;t familiar with.</ul>
<p>If you&#8217;re thinking of becoming a CISSP, have a look at the <a href="http://www.cccure.org/flash/intro/player.html">flash video introduction</a> on cccure.org.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/12/cissp-certification/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Fedora Core 5 on a Dell Latitude D620</title>
		<link>http://mikelococo.com/2006/10/fc5-on-d620/</link>
		<comments>http://mikelococo.com/2006/10/fc5-on-d620/#comments</comments>
		<pubDate>Sat, 28 Oct 2006 05:57:08 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[d620]]></category>
		<category><![CDATA[dell]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[hardware compatibility]]></category>
		<category><![CDATA[latitude]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/10/fc5-on-d620/</guid>
		<description><![CDATA[Instructions for getting Fedora Core 5 humming on the Dell Latitude D620 probably fall into the category of better late than never at this point. Since FC6 was recently released, this post will primarily serve as a comparison against a &#8230; <a href="http://mikelococo.com/2006/10/fc5-on-d620/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Instructions for getting Fedora Core 5 humming on the Dell Latitude D620 probably fall into the category of better late than never at this point.  Since FC6 was recently released, this post will primarily serve as a comparison against a future (and more timely) <a href="http://mikelococo.com/2007/01/fc6-on-d620/">guide for FC6 on the D620</a>.</p>
<p>FC5 can be made to work fairly well on the D620, but many things require tweaking to work properly.  This guide summarizes what can be made to work and how.  It is not a step by step howto, but does attempt to link to more detailed resources when they are available.  Most items worked without any manual configuration, those that required some tweaking to be fully functional are in italics, and issues that couldn&#8217;t be resolved are in bold. It&#8217;s worth noting that essentially all of my issues with the laptop stem from the use of a Broadcom wireless card, it&#8217;s a very well supported system when paired with the Intel wireless option.</p>
<ul>
<li>Dual-core Processor: Both cores are detected on the 2.17GHz Intel Core Duo processor, the 32bit i686 smp kernel is installed and just works.</li>
<li>USB: Works, no config needed.</li>
<li>PCMCIA Slot: Works, no config needed.</li>
<li>Touchpad/Track Stick: Works, no config needed.  Install <a href="http://gsynaptics.sourceforge.jp/">gsynaptics</a> from Extras if you want to customize the trackpad behavior.</li>
<li><em>Suspend to Ram:</em>Works after updating kernel to 2.6.18-1.2200.fc5smp.</li>
<li><em>Suspend to Disk:</em> Works after updating kernel to 2.6.18-1.2200.fc5smp.</li>
<li>Ethernet: Works, no config needed.</li>
<li><strong>Wireless Networking:</strong> Works with ndiswrapper, but conflicts with 3D acceleration (see the 3D section for details).  I accidentally purchased the Dell Truemobile 1390 wireless card option, which is based on the awful Broadcom BCM4310.  You should order the Intel wireless option instead, but if you already have an icky Broadcom it can be made to work using ndiswrapper.  Follow the <a href="http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation">standard installation instructions</a> using the <a href="http://support.dell.com/support/downloads/download.aspx?c=us&#038;cs=19&#038;l=en&#038;s=dhs&#038;releaseid=R115321&#038;SystemID=INS_PNT_PM_600M&#038;os=WW1&#038;osl=en&#038;deviceid=9110&#038;devlib=0&#038;typecnt=1&#038;vercnt=9&#038;formatcnt=1&#038;libid=0&#038;fileid=152055">r115321.exe driver</a> available from Dell.  Once you&#8217;re configured, don&#8217;t forget to <a href="http://fedoraproject.org/wiki/Tools/NetworkManager#head-fc3fe44e92c63867615113b1ef69cf4fc0dc03cf">enable the network manager applet</a> so you don&#8217;t have to iwconfig from the terminal all the time.</li>
<li><em>2D Video:</em> The native display resolution is incorrectly detected, add the correct modeline to xorg.conf to fix (ignore the 915resolution stuff if you have an NVidia card like me). (Update 2010-10-18: The link with the modeline instructions is now dead)</li>
<li><strong>3D Acceleration:</strong> The NVidia Quadro 110M works well after installing NVidia drivers from livna, but causes the Broadcom wireless card to stop working reliably.  I&#8217;m not aware of a workaround other than to use the open source nv driver which doesn&#8217;t offer 3D acceleration (or to purchase the Intel wireless option, which doesn&#8217;t suffer from the issue).  Track progress on the issue <a href="https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/57355">here</a> and <a href="http://www.nvnews.net/vbulletin/showthread.php?t=48327&#038;page=2">here</a>.</li>
<li><em>External Monitor:</em> If you don&#8217;t use the NVidia driver, hooking up to the VGA out is painful.  <strike>Changing to a standard (non-wide) resolution and back again requires editing xorg.conf</strike> (some update, not sure which, added the correct resolution to the screen-res dialog so changing resolutions isn&#8217;t that painful anymore), there&#8217;s no proper resolution scaling, and no graphical interface for configuring dual-head.</td>
</tr>
<li>CD/DVD Burning: Works out of the box, but <a href="http://www.fedoraforum.org/forum/showthread.php?t=114586">this tweak</a> substantially improves burn speed and system responsiveness while burning.</li>
<li>Sound Playback: The audio drivers for the Intel High Definition Audio devices used in this system had problems in the initial release of FC5, but it should work fine after a yum update.</li>
<li>Sound Recording: Works after updating.  If you&#8217;re not getting recorded sound, look in the preferences for the Volume Control app, make sure that &#8220;capture&#8221; is enabled and the recording level isn&#8217;t way down.</li>
<li><em>Volume Keys:</em> Go into System &#8211;> Preferences &#8211;> Keyboard shortcuts and assign the multimedia keys to vol down/up/mute (or whatever you want them to do).</li>
<li>Radio On/Off Switch: Works fine, and has a noticeable effect on battery life.  You may need to &#8220;up&#8221; the interface with the connection manager of your choice if you enable the radio while the system is running.</li>
<li><strong>Fingerprint Reader:</strong> Untested. </li>
<li><strong>Bluetooth:</strong> Untested.</li>
<li><strong>Modem:</strong> Untested.</li>
<li>ACPI Power Management: Auto fan speed and cpu frequency scaling work without configuration.  Right-click the top gnome panel (the bar with the applications menu and the clock) and add the cpu frequency scaling monitor if you want some feedback and control over frequency scaling (which definitely affects battery life and laptop temperature during use).</li>
</ul>
<h3>Output of lspci</h3>
<p><code>00:00.0 Host bridge: Intel Corporation Mobile Memory Controller Hub (rev 03)<br />
00:01.0 PCI bridge: Intel Corporation Mobile PCI Express Graphics Port (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controllers cc=IDE (rev 01)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)<br />
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 01d7 (rev a1)<br />
03:01.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 40)<br />
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)<br />
0c:00.0 Network controller: Broadcom Corporation BCM4310 UART (rev 01)</code></p>
<h3>Useful Links</h3>
<ul>
<li><a href="http://www.linux-on-laptops.com/dell.html">Linux on Laptops page for Dells</a> (search the page for 620)</li>
<li><a href="http://javier.rodriguez.org.mx/index.php/linux/debian-gnulinux-on-dell-d620/">Debian on the D620</a></li>
<li><a href="http://www.oiepoie.nl/linux_on_d620/">Another guide to Fedora Core 5 on the D620</a></li>
<li><a href="http://mikelococo.com/2007/01/fc6-on-d620/">My guide to Fedora Core 6 on the D620</a></li>
<li><a href="http://blog.adl.pl/fedora-core-6-on-dell-latitude-d620/18">Another guide to Fedora Core 6 on the D620</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/10/fc5-on-d620/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Parsons Design Workshop</title>
		<link>http://mikelococo.com/2006/09/parsons-design-workshop/</link>
		<comments>http://mikelococo.com/2006/09/parsons-design-workshop/#comments</comments>
		<pubDate>Thu, 28 Sep 2006 22:16:45 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[design workshop]]></category>
		<category><![CDATA[parsons]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/09/parsons-design-workshop/</guid>
		<description><![CDATA[My partner is part of a group of graduate students at Parsons who have been working to design and build a laundromat and community information center in DeLisle, Mississippi. The student-lead team worked from January to May to design the &#8230; <a href="http://mikelococo.com/2006/09/parsons-design-workshop/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>My partner is part of a group of graduate students at <a href="http://parsons.edu">Parsons</a> who have been working to design and build a laundromat and community information center in <a href="http://maps.yahoo.com/maps_result?csz=delisle+mississippi">DeLisle, Mississippi</a>.  The student-lead team worked from January to May to design the building and plan its construction, then moved to DeLisle for the summer where they lived and worked to build the structure. The project has been very well received:</p>
<ul>
<li>It was displayed in a group exhibit at the 2006 <a href="http://www.labiennale.org/en/architecture/">Venice Biennale</a>.</li>
<li>It was featured in September 2006 edition of Architecture magazine (one of four articles linked off this month&#8217;s homepage for the magazine).  To highlight the student-run nature of the project, the magazine had the students write their own article and submit their own photos, which were taken by Laura. (Update 2010-10-18, the link for this article is now dead unfortunately.)</li>
<li>Dwell Magazine published an article in June of 2007 (Update 2010-10-18, this link has also stopped working).</li>
<li>Allegedly NBC planned some coverage, but I&#8217;m not sure if it was ever released. Let me know if you find it.</li>
<li>The <a href="http://www.nytimes.com/2006/11/06/arts/design/06pars.html?adxnnl=1">New York Times</a> published an article in November of 2006.</li>
<li><a href="http://www.designtaxi.com/news.jsp?id=11934&amp;monthview=1&amp;month=9&amp;year=2007" class="broken_link" rel="nofollow">The American Institute of Architects</a> awarded the project an AIA New York State Design Award in September of 2006.</li>
</ul>
<p>For more information about the project, click through their <a href="http://www.flickr.com/photos/infowash/">flickr photo page</a>.  For more information about the Parsons Design Workshop in general have a look through the following links:</p>
<ul>
<li><a href="http://www.newschool.edu/pressroom/pressreleases/2005/081505_parsons_tdw.html">2005 Retrospective announcement</a></li>
<li><a href="http://www.metropolismag.com/cda/story.php?artid=1709">Writeup of the 2005 project</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/09/parsons-design-workshop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WuCoco 0.10.2</title>
		<link>http://mikelococo.com/2006/09/wucoco-0102/</link>
		<comments>http://mikelococo.com/2006/09/wucoco-0102/#comments</comments>
		<pubDate>Mon, 25 Sep 2006 04:24:10 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/09/wucoco-0102/</guid>
		<description><![CDATA[This is a bugfix release for WuCoco, it contains no new features but resolves the following issues: Comments now render properly in IE6. This is a moderately severe bug. Posts with complex HTML tags now display properly in the category &#8230; <a href="http://mikelococo.com/2006/09/wucoco-0102/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This is a bugfix release for WuCoco, it contains no new features but resolves the following issues:</p>
<ul>
<li>Comments now render properly in IE6.  This is a moderately severe bug.</li>
<li>Posts with complex HTML tags now display properly in the category archives.</li>
<li>All theme variants are now validating again (thanks for the patch Brian).</li>
<li>The comments link now correctly links to the comment form when a post has no existing comments.</li>
</ul>
<p>By now, you know the drill:  Download the <a href="http://mikelococo.com/files/2006/wucoco_1col-0.10.2.zip">one-column layout</a>, the <a href="http://mikelococo.com/files/2006/wucoco_2col-0.10.2.zip">two-column layout</a>, the <a href="http://mikelococo.com/files/2006/wucoco_3col-0.10.2.zip">new three-column layout</a>, or the <a href="http://mikelococo.com/files/2006/wucoco_imgsrc-0.10.0.zip">image sources</a> (which haven&#8217;t changed since 0.10.0) in Gimp XCF format. Read the <a href="/projects/wucoco/">project page</a> for the latest downloads and more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/09/wucoco-0102/feed/</wfw:commentRss>
		<slash:comments>176</slash:comments>
		</item>
		<item>
		<title>Droopy Drew, Where Are You?</title>
		<link>http://mikelococo.com/2006/08/droopy-drew/</link>
		<comments>http://mikelococo.com/2006/08/droopy-drew/#comments</comments>
		<pubDate>Mon, 28 Aug 2006 21:25:21 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[friends]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/08/droopy-drew/</guid>
		<description><![CDATA[Drew&#8230; you didn&#8217;t leave your e-mail address or phone number. Try another way. Or send me an e-mail at the address I contacted your brother from like a normal person. You&#8217;d be impressed with the sleuthing job Rich and I &#8230; <a href="http://mikelococo.com/2006/08/droopy-drew/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Drew&#8230; you didn&#8217;t leave your e-mail address or phone number.  Try another way.  Or send me an e-mail at the address I contacted your brother from like a normal person.  You&#8217;d be impressed with the sleuthing job Rich and I did to find you.</p>
<p>P.S.  Sorry for the private post in a public forum, folks.  I&#8217;m tracking down an old friend and don&#8217;t have conventional contact info yet.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/08/droopy-drew/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Peanut Threat</title>
		<link>http://mikelococo.com/2006/08/the-peanut-threat/</link>
		<comments>http://mikelococo.com/2006/08/the-peanut-threat/#comments</comments>
		<pubDate>Sat, 12 Aug 2006 02:38:18 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[soapbox]]></category>
		<category><![CDATA[security theater]]></category>
		<category><![CDATA[terrorism]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/08/the-peanut-threat/</guid>
		<description><![CDATA[Earlier this week, Schneier wrote about a short paper from the CATO Institute that attempts to give some everyman-context to the risks associated with terrorist threats. Although it was BoingBoinged the same day, apparently not enough people read it because &#8230; <a href="http://mikelococo.com/2006/08/the-peanut-threat/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Earlier this week, <a href="http://www.schneier.com/blog/archives/2006/08/cato_on_the_ris.html">Schneier</a> wrote about a short <a href="http://www.cato.org/pubs/regulation/regv27n3/v27n3-5.pdf">paper from the CATO Institute</a> that attempts to give some everyman-context to the risks associated with terrorist threats.  Although it was <a href="http://www.boingboing.net/2006/08/07/only_traitors_try_to.html">BoingBoinged</a> the same day, apparently not enough people read it because the media is ablaze all over again with totally <a href="http://www.cbsnews.com/stories/2006/08/10/eveningnews/main1884609.shtml">irrational commentary</a> since the <a href="http://news.bbc.co.uk/1/hi/uk/4778615.stm?ls">incident in the UK</a>.  A choice quote from the CATO paper puts the risk of dying in a terrorist incident into perspective:</p>
<blockquote><p>Even with the September 11 attacks included in the count, the number of Americans killed by international terrorism since the late 1960s&#8230; is about the same as the number of Americans killed over the same period by lightning, accident-causing deer, or severe allergic reaction to peanuts.</p></blockquote>
<p>This one compares airline terrorism to the risks associated with driving:</p>
<blockquote><p>University of Michigan transportation researchers&#8230; determined there would have to be one set of September 11 crashes a month for [flying to be as risky as driving an equivalent distance].</p></blockquote>
<p>So I say enough is enough.  Forget about this terrorism baloney, what I want to know is what the government is doing to protect America from destruction by the new Triangle Of Terror: lightning, rogue-deer, and peanuts.  Now please excuse me while I go buy some lotto tickets.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/08/the-peanut-threat/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WuCoco 0.10.1</title>
		<link>http://mikelococo.com/2006/07/wucoco-0101/</link>
		<comments>http://mikelococo.com/2006/07/wucoco-0101/#comments</comments>
		<pubDate>Tue, 01 Aug 2006 00:06:27 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/07/wucoco-0101/</guid>
		<description><![CDATA[WuCoco 0.10.1 is a small update that adds IE7 compatability. Please don&#8217;t download IE7, though. Seriously. Internet Explorer has been an anchor tied to the leg of the web design community for years. CSS3 support is just around the corner, &#8230; <a href="http://mikelococo.com/2006/07/wucoco-0101/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>WuCoco 0.10.1 is a small update that adds IE7 compatability.</p>
<p>Please don&#8217;t download IE7, though.  Seriously.  Internet Explorer has been an anchor tied to the leg of the web design community for years.  CSS3 support is just around the corner, and it&#8217;s going to start all over again with the hacks and the new features that are supported by every browser but IE. <a href="http://mozilla.com/">Firefox</a> is great, <a href="http://opera.com/">Opera</a> is great, Safari is great.  There&#8217;s really only one wrong answer, so do your part to make the web a better place and switch today.</p>
<p>Anyway, all ranting and no downloading makes Jack a dull boy.  Get the <a href="http://mikelococo.com/files/2006/wucoco_1col-0.10.1.zip">one-column layout</a>, the <a href="http://mikelococo.com/files/2006/wucoco_2col-0.10.1.zip">two-column layout</a>, the <a href="http://mikelococo.com/files/2006/wucoco_3col-0.10.1.zip">three-column layout</a>, or the <a href="http://mikelococo.com/files/2006/wucoco_imgsrc-0.10.0.zip">image sources</a> in Gimp XCF format (which haven&#8217;t changed since 0.10.0). Read the <a href="/projects/wucoco/">project page</a> for the latest downloads and more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/07/wucoco-0101/feed/</wfw:commentRss>
		<slash:comments>62</slash:comments>
		</item>
		<item>
		<title>Wucoco 0.10.0</title>
		<link>http://mikelococo.com/2006/07/wucoco-0100/</link>
		<comments>http://mikelococo.com/2006/07/wucoco-0100/#comments</comments>
		<pubDate>Thu, 20 Jul 2006 02:48:36 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/07/wucoco-0100/</guid>
		<description><![CDATA[During the development for 0.9.0 I thought I was ramping up for the big one-oh release, but as I dig deeper into the theme I&#8217;m finding that there are a few more cycles of disruptive development before I&#8217;m ready to &#8230; <a href="http://mikelococo.com/2006/07/wucoco-0100/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>During the development for 0.9.0 I thought I was ramping up for the big one-oh release, but as I dig deeper into the theme I&#8217;m finding that there are a few more cycles of disruptive development before I&#8217;m ready to settle into a maintenance cycle.  WuCoco 0.10.0 features&#8230;</p>
<ul>
<li>The much requested three column variant.  I&#8217;d like to thank Soulpress.net for generously sponsoring the development of this feature.</li>
<li>A completely revamped layout engine, based on the Octopus Engine from Dragon Labs.  Now that WuCoco no longer relies on faux columns it&#8217;s much easier to adjust column-width, and I no longer have to maintain separate graphic assets for the different variants.  As an added bonus, it&#8217;s possible to easily switch to independent column heights if you choose.</li>
</ul>
<p>The new layout engine involves a lot of changes under the hood.  It&#8217;s quite possible that rendering bugs have been introduced, so speak up if you find one.  By now, you know the drill:  Download the <a href="http://mikelococo.com/files/2006/wucoco_1col-0.10.0.zip">one-column layout</a>, the <a href="http://mikelococo.com/files/2006/wucoco_2col-0.10.0.zip">two-column layout</a>, the <a href="http://mikelococo.com/files/2006/wucoco_3col-0.10.0.zip">new three-column layout</a>, or the <a href="http://mikelococo.com/files/2006/wucoco_imgsrc-0.10.0.zip">image sources</a> in Gimp XCF format. Read the <a href="/projects/wucoco/">project page</a> for the latest downloads and more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/07/wucoco-0100/feed/</wfw:commentRss>
		<slash:comments>36</slash:comments>
		</item>
		<item>
		<title>A Tale of How</title>
		<link>http://mikelococo.com/2006/07/a-tale-of-how/</link>
		<comments>http://mikelococo.com/2006/07/a-tale-of-how/#comments</comments>
		<pubDate>Sun, 09 Jul 2006 05:21:50 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[Blackheart Gang]]></category>
		<category><![CDATA[Tale of How]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/07/a-tale-of-how/</guid>
		<description><![CDATA[Check out the amazing animated short available from the Blackheart Gang, A Tale of How (low-res youtube version). It feels grand and beautiful and immediately evokes a kind of childlike wonderment that&#8217;s all too rare in the adult world. The &#8230; <a href="http://mikelococo.com/2006/07/a-tale-of-how/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><img align="left" width="200" hspace="7" height="124" border="0" src="/files/2006/tale_of_how.png" />Check out the amazing animated short available from the <a href="http://www.theblackheartgang.com/">Blackheart Gang</a>, <i>A Tale of How</i> (<a href="http://www.youtube.com/watch?v=cQvKnK08RXg">low-res youtube version</a>).  It feels grand and beautiful and immediately evokes a kind of childlike wonderment that&#8217;s all too rare in the adult world.</p>
<p>The short is often and aptly compared Terry&#8217;s Gilliam&#8217;s animation for Monty Python&#8217;s Flying Circus and to anything by Tim Burton (WFMU says: &#8220;I&#8217;m sure they whip a stapler across the room every time someone goes &#8216;Tim Burton.&#8217;&#8221;), although it&#8217;s denser and more surreal than either (yes, more surreal than Tim Burton).  The most apt comparison I can make is to the little known work of <a href="http://www.patrickwoodroffe-world.com/image.htm">Patrick Woodroffe</a>.  I first encountered Patrick&#8217;s drawings when I was a child through the very collectible <i><a href="http://www.patrickwoodroffe-world.com/second.htm">The Second Earth:  The Pentateuch Retold</a></i>, which confused and intrigued me with it&#8217;s simple but striking story and fantastically detailed imagery.</p>
<p>There&#8217;s not currently a lot of information about the Blackheart Gang on the web, but Motionographer does have an informative writeup including links to <a href="http://www.motionographer.com/2006/06/07/blackheart-gang-tale-of-how/">two additional BHG audio files</a> that I haven&#8217;t seen posted elsewhere.  Update 5/7/07:  Siouxwire has an <a href="http://siouxwire.blogspot.com/2007/05/interview-blackheart-gang-ree-treweek.html">interview with the Blackheart Gang</a>.</p>
<p>Via <a href="http://blog.wfmu.org/">WFMU&#8217;s Beware of the Blog</a> (Update 2010-10-18: The original story at WFMU has disappeared, linking to their front-page instead).</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/07/a-tale-of-how/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WuCoco 0.9.0</title>
		<link>http://mikelococo.com/2006/06/wucoco-090/</link>
		<comments>http://mikelococo.com/2006/06/wucoco-090/#comments</comments>
		<pubDate>Wed, 07 Jun 2006 02:27:47 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/06/wucoco-090/</guid>
		<description><![CDATA[WuCoco 0.9.0 is the result of the first round of concerted development work on the theme since its creation and it&#8217;s chock-full of new features and bugfixes: Clean archives (Update: website for the clean archives plugin has disappeared) has been &#8230; <a href="http://mikelococo.com/2006/06/wucoco-090/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>WuCoco 0.9.0 is the result of the first round of concerted development work on the theme since its creation and it&#8217;s chock-full of new features and bugfixes:</p>
<ul>
<li>Clean archives (Update: website for the clean archives plugin has disappeared) has been integrated to provide an information rich and inviting view of your post history.  No fussing with plugins required.</li>
<li>Author comments are now highlighted to stand out.</li>
<li>The two-column layout is widget friendly.</li>
<li>A bug that was causing the comment form border to occasionally render incorrectly has been fixed.</li>
<li>Post margins have been made robust (previously many seldom used tags rendered without a margin)</li>
<li>The stylesheets have been reworked to be ease future development.</li>
</ul>
<p>Download the <a href="/files/2006/wucoco_1col-0.9.0.zip">one-column layout</a>, the <a href="/files/2006/wucoco_2col-0.9.0.zip">two-column layout</a>, or the <a href="/files/2006/wucoco_imgsrc-0.9.0.zip">image sources</a> in Gimp XCF format.  Read the <a href="/projects/wucoco/">project page</a> for the latest downloads and more information.</p>
<p><b>Update 7/18</b>:  This version is also known as 0.5.0.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/06/wucoco-090/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>WuCoco Preview</title>
		<link>http://mikelococo.com/2006/06/wucoco-preview/</link>
		<comments>http://mikelococo.com/2006/06/wucoco-preview/#comments</comments>
		<pubDate>Sat, 03 Jun 2006 13:42:03 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/06/wucoco-preview/</guid>
		<description><![CDATA[This site is now running a pre-release copy of the next version of the WuCoco theme, which will be ready for public consumption soon. It includes several significant new features including author comment highlighting, clean archives style archives (Update: links &#8230; <a href="http://mikelococo.com/2006/06/wucoco-preview/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This site is now running a pre-release copy of the next version of the <a href="/projects/wucoco/">WuCoco theme</a>, which will be ready for public consumption soon.  It includes several significant new features including author comment highlighting, clean archives style archives (Update: links to the clean-archives plugin all appear to be dead), <a href="http://automattic.com/code/widgets/">widget</a> support in the two-column theme, and a major stylesheet revamp to ease future development.  Have a poke around and leave a comment if you have some feedback.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/06/wucoco-preview/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>A+ Certification</title>
		<link>http://mikelococo.com/2006/05/aplus/</link>
		<comments>http://mikelococo.com/2006/05/aplus/#comments</comments>
		<pubDate>Thu, 04 May 2006 23:29:58 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[personal]]></category>
		<category><![CDATA[a+ certification]]></category>
		<category><![CDATA[flashcards]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/05/aplus/</guid>
		<description><![CDATA[Not just grade A, I&#8217;m A+ and I have the papers to prove it. Or I should in 6-8 weeks. I took and passed the exams earlier this week. In some ways I feel a little silly about it, because &#8230; <a href="http://mikelococo.com/2006/05/aplus/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Not just grade A, I&#8217;m A+ and I have the papers to prove it.  Or I should in 6-8 weeks.  I took and passed the exams earlier this week.  In some ways I feel a little silly about it, because it&#8217;s a lightweight certification that&#8217;s meant to demonstrate only very basic computer maintenance skills.  I&#8217;ve put off doing the certification dance for too long though, and going through the process with an easy exam has been a good way to get my feet wet.</p>
<p>I took about 30 hours over two weeks to self-study, much of it spent reading the <a href="http://www.amazon.com/gp/product/0072229918/">Osborne book</a>, which I was fairly disappointed with.  Although I did learn something useful from most of the chapters in the book, it&#8217;s badly edited.  Technical terms are routinely misused, and many of the sample test questions are worded poorly enough to cause confusion even if you understand the material.  If I had it to do over again, I might try the <a href="http://www.amazon.com/gp/product/0782142435/">Sybex book</a> in hopes that it was better.</p>
<p>Although there&#8217;s some basic conceptual knowledge required to pass the test, a good deal of it is fact recall.  I made up a set of flashcards that I used to memorize the requisite bits.  <a href="/files/2006/aplus_flashcards.zip">Download the flashcards</a> in both granule deck format (<a href="http://granule.sourceforge.net/">granule</a> is a gem, by the way&#8230; especially on the Nokia 770) and colon-delimited text format.  If you use/improve them, please send me the updates and I&#8217;ll make them available here.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/05/aplus/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>WuCoco 0.4.3</title>
		<link>http://mikelococo.com/2006/04/wucoco-043/</link>
		<comments>http://mikelococo.com/2006/04/wucoco-043/#comments</comments>
		<pubDate>Tue, 25 Apr 2006 12:34:36 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/04/wucoco-043/</guid>
		<description><![CDATA[The latest version of the WordPress theme used on this site is now available. The updates are all documentation related, updating links to point to the new project page and preparing for submission to the WordPress Theme Competition. Download the &#8230; <a href="http://mikelococo.com/2006/04/wucoco-043/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The latest version of the WordPress theme used on this site is now available.  The updates are all documentation related, updating links to point to the new project page and preparing for submission to the <a href="http://www.arenawp.com/">WordPress Theme Competition</a>.</p>
<p>Download the <a href="/files/2006/wucoco_1col-0.4.3.zip">one-column layout</a>, the <a href="/files/2006/wucoco_2col-0.4.3.zip">two-column layout</a>, or the <a href="/files/2006/wucoco_imgsrc-0.4.3.zip">image sources</a> in Gimp XCF format.  Read the <a href="/projects/wucoco/">project page</a> for the latest downloads and more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/04/wucoco-043/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>Plunger Press</title>
		<link>http://mikelococo.com/2006/04/plunger-press/</link>
		<comments>http://mikelococo.com/2006/04/plunger-press/#comments</comments>
		<pubDate>Tue, 25 Apr 2006 02:58:21 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[soapbox]]></category>
		<category><![CDATA[plunger press]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/04/plunger-press/</guid>
		<description><![CDATA[Check out plungerpress.com for groovy political kitsch, including t-shirts with Donald Rumsfeld&#8217;s head in a mason jar. All products are hand-printed and shirts are nice quality cotton/poly tees by Hanes. I&#8217;m not clear if this is a permanent web fixture &#8230; <a href="http://mikelococo.com/2006/04/plunger-press/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Check out <a href="http://plungerpress.com/feature.html">plungerpress.com</a> for groovy political kitsch, including t-shirts with Donald Rumsfeld&#8217;s head in a mason jar.  All products are hand-printed and shirts are nice quality cotton/poly tees by Hanes.</p>
<p>I&#8217;m not clear if this is a permanent web fixture or temporary art installation.  It was incorporated into a recent graduate thesis in fine art at Cornell University.  But it&#8217;s not obvious to me if it&#8217;s aiming to create a pop-culture brand to market and financially support the artist&#8217;s work, or if it&#8217;s an ironic critique of consumerism.  Maybe it&#8217;s both.  Anyway, act fast if you want to consume their products&#8230; supplies are limited!</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/04/plunger-press/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ICDSoft Wrapup</title>
		<link>http://mikelococo.com/2006/04/icdsoft-wrapup/</link>
		<comments>http://mikelococo.com/2006/04/icdsoft-wrapup/#comments</comments>
		<pubDate>Fri, 07 Apr 2006 00:06:13 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[icdsoft]]></category>
		<category><![CDATA[maintenance]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/04/icdsoft-wrapup/</guid>
		<description><![CDATA[As previously mentioned, I did decide to migrate to a new domain and webhost. In addition to the comment left in response to my original ICDSoft commentary, an ICDSoft representative contacted me via e-mail. The message conveyed considerable distress over &#8230; <a href="http://mikelococo.com/2006/04/icdsoft-wrapup/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>As <a href="http://mikelococo.com/2006/03/new-home/">previously mentioned</a>, I did decide to migrate to a new domain and webhost.  In addition to the <a href="http://mikelococo.com/2006/03/icdsoft-rocks/#comments">comment</a> left in response to my original <a href="http://mikelococo.com/2006/03/icdsoft-rocks/">ICDSoft commentary</a>, an ICDSoft representative contacted me via e-mail.  The message conveyed considerable distress over my post and also mentioned an unspecified potential terms of use violation.  Although the representative suggested that ICDSoft would never consider censorship of its users, the choice to address possible policy violations in a conversation about critical content was distressing to me.</p>
<p>Even though there have been no tangible repercussions from the incident with ICDSoft, the experience has made it clear to me that my actions can reflect on and impact other members of the lococo.org community in unintended ways.  Migrating my content into its own namespace will channel future feedback directly to me and prevent possible confusion about whose opinion is being represented.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/04/icdsoft-wrapup/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>New Home</title>
		<link>http://mikelococo.com/2006/03/new-home/</link>
		<comments>http://mikelococo.com/2006/03/new-home/#comments</comments>
		<pubDate>Wed, 29 Mar 2006 04:52:43 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[icdsoft]]></category>
		<category><![CDATA[maintenance]]></category>

		<guid isPermaLink="false">http://mikelococo.com/2006/03/new-home/</guid>
		<description><![CDATA[Even though cool uri&#8217;s don&#8217;t change, I&#8217;m in the process of moving to a new home at mikelococo.com for reasons I&#8217;ll elucidate on shortly. The new site is already live (it looks just like the old one), and next week &#8230; <a href="http://mikelococo.com/2006/03/new-home/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Even though <a href="http://www.w3.org/Provider/Style/URI">cool uri&#8217;s don&#8217;t change</a>, I&#8217;m in the process of moving to a new home at <a href="http://mikelococo.com/">mikelococo.com</a> for reasons I&#8217;ll elucidate on shortly.  The new site is already live (it looks just like the old one), and next week I&#8217;ll tear things down on lococo.org.  After that happens, visitors who come here looking for me will be redirected the the corresponding page on the new site.  Hopefully it will all be fairly seamless.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/03/new-home/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ICDSoft Rocks (not)!</title>
		<link>http://mikelococo.com/2006/03/icdsoft-rocks/</link>
		<comments>http://mikelococo.com/2006/03/icdsoft-rocks/#comments</comments>
		<pubDate>Wed, 15 Mar 2006 03:31:50 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[soapbox]]></category>
		<category><![CDATA[icdsoft]]></category>
		<category><![CDATA[review]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/2006/03/icdsoft-rocks/</guid>
		<description><![CDATA[Update: Shortly after this post, I stopped using ICDSoft as a host due to this incident. Read ICDSoft wrapup for details. In short, they contacted me privately in an an email that conveyed considerable distress over my post. While they &#8230; <a href="http://mikelococo.com/2006/03/icdsoft-rocks/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><strong>Update:</strong> Shortly after this post, I stopped using ICDSoft as a host due to this incident. Read <a href="http://mikelococo.com/2006/04/icdsoft-wrapup/">ICDSoft wrapup</a> for details.  In short, they contacted me privately in an an email that conveyed considerable distress over my post. While they claimed that they would never consider attempting to censor their users, they also chose that conversation to mention an unspecified terms of use violation that I might have made. While nothing more came of the discussion and there were no tangible consequences, I decided it was time to move on after that.</p>
<p><a href="http://icdsoft.com">ICDSoft</a> isn&#8217;t giving me $200 to <a href="http://en.wikipedia.org/wiki/Shill">shill</a> for their hosting services but they are paying ten other lucky folks, according an announcement sent to customers on 3/8/2006 via the news section of their hosting control panel (bold sections are my emphasis):</p>
<blockquote><p>March 8th, 2006 | A &#8220;Thank You&#8221; to our loyal customers!</p>
<p>Over the past few years, ICDSoft has grown steadily to reach more than 70,000 domains hosted. We fully recognize that a big part of our success is the words of recommendation sent out by our existing customers to other potential clients all over the world. We realize that these recommendations are the best advertisement we could ever have. For this reason, we have decided to extend our gratitude to our customers by rewarding the best reviews of our hosting services.</p>
<p>Such an undertaking was not an easy task however. We started out by seeking and collecting all the reviews of our services that have been posted over the years. An ever bigger challenge was deciding which were the best. All reviews were assessed with several factors in mind: the objectivity of the information provided, the writing style, the popularity of the web site it is posted on, and others. <b>After a great deal of analysis, we have chosen to reward each of the following reviews with $200</b>:</p>
<ol>
<li><a href="http://www.webhostingtalk.com/showthread.php?t=473518">http://www.webhostingtalk.com/showthread.php?t=473518</a></li>
<li><a href="http://www.DiabeticMommy.com/hosting.htm">http://www.DiabeticMommy.com/hosting.htm</a></li>
<li><a href="http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews.html#hostreview3905">http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews.html#hostreview3905</a></li>
<li>http://www.amazon.com/exec/obidos/tg/detail/-/B00006EN7N/104-1375399-3445510?v=glance (link dead)</li>
<li><a href="http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews3.html#hostreview3365">http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews3.html#hostreview3365</a></li>
<li><a href="http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews3.html#hostreview3276">http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews3.html#hostreview3276</a></li>
<li><a href="http://wordpress.org/support/topic/20562#post-177232">http://wordpress.org/support/topic/20562#post-177232</a></li>
<li><a href="http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews3.html#hostreview3277">http://www.besthostratings.com/web-hosting/reviews/icdsoft-Reviews3.html#hostreview3277</a></li>
<li><a href="http://webhostingtalk.com/showthread.php?t=475347">http://webhostingtalk.com/showthread.php?t=475347</a></li>
<li><a href="http://www.webhostingtalk.com/showthread.php?threadid=345718">http://www.webhostingtalk.com/showthread.php?threadid=345718</a><br />
(<a href="http://www.webhostingtalk.com/showpost.php?p=2656502">http://www.webhostingtalk.com/showpost.php?p=2656502</a>)</li>
<p>It is important to note that we found many other fantastic reviews, but could not reward them because the domain name of the poster was not provided in the review. We are also sure that there were many reviews out there that we simply could not find. If you have posted a review about our services, you can tell us about it through the &#8220;Submit a review&#8221; link on the left pane of your hosting Control panel.</p>
<p><b>We are planning to express our gratitude in a similar fashion in the future as well.</b> Thank you once again for your support!</p>
<p>ICDSoft Team</p></blockquote>
<p>They don&#8217;t explicitly state that they&#8217;re paying for positive reviews, but if you follow the listed links it&#8217;s clear that they&#8217;re not paying for negative ones.  You&#8217;ve got to wonder if this is the first time they&#8217;ve done this, or just the first time they&#8217;ve made an official announcement about it.  This site is hosted on icdsoft (so if it disappears next week you&#8217;ll know why), and they actually are a pretty decent value-oriented host.  It <i>almost</i> seems odd that they would need to resort to <a href="http://en.wikipedia.org/wiki/Astroturfing">astroturfing</a>, but increasingly I find that no amount of <a href="http://www.nytimes.com/2005/03/29/politics/29donate.html?ex=1269752400&#038;en=f1312f1b5ae170ad&#038;ei=5090&#038;partner=rssuserland">moral turpitude</a> will surprise me.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/03/icdsoft-rocks/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>WuCoco 0.4.2</title>
		<link>http://mikelococo.com/2006/03/wucoco-042/</link>
		<comments>http://mikelococo.com/2006/03/wucoco-042/#comments</comments>
		<pubDate>Sun, 12 Mar 2006 03:24:55 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wucoco]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/2006/03/updated-skin/</guid>
		<description><![CDATA[At the request of Wuhan&#8217;s author, I&#8217;ve packaged up one- and two-column versions of this theme for download. Love/Hate mail as well as bug-reports can go in the comments here. Download the one-column layout, the two-column layout, or the image &#8230; <a href="http://mikelococo.com/2006/03/wucoco-042/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>At the request of Wuhan&#8217;s author, I&#8217;ve packaged up one- and two-column versions of this theme for download.  Love/Hate mail as well as bug-reports can go in the comments here.  </p>
<p>Download the <a href="/files/2006/wucoco_1col-0.4.2.zip">one-column layout</a>, the <a href="/files/2006/wucoco_2col-0.4.2.zip">two-column layout</a>, or the <a href="/files/2006/wucoco_imgsrc-0.4.2.zip">image sources</a> in Gimp XCF format.  Otherwise, head over to the <a href="http://mikelococo.com/projects/wucoco/">project page</a> for the latest downloads and more info.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/03/wucoco-042/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Skin for the Old Ceremony</title>
		<link>http://mikelococo.com/2006/03/new-skin-for-the-old-ceremony/</link>
		<comments>http://mikelococo.com/2006/03/new-skin-for-the-old-ceremony/#comments</comments>
		<pubDate>Fri, 10 Mar 2006 00:06:49 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[personal]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/2006/03/new-skin-for-the-old-ceremony/</guid>
		<description><![CDATA[So the new site skin is up and I&#8217;m fairly happy with it. It&#8217;s based on Wuhan 0.4 (2010-10-17 update, the Wuhan website has long since disappeared, so no link is available), with a short javascript lifted from Gespaa. I &#8230; <a href="http://mikelococo.com/2006/03/new-skin-for-the-old-ceremony/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>So the new site skin is up and I&#8217;m fairly happy with it.  It&#8217;s based on Wuhan 0.4 (2010-10-17 update, the Wuhan website has long since disappeared, so no link is available), with a short javascript lifted from <a href="http://ifelse.co.uk/gespaa/">Gespaa</a>.  I made lots of small changes, most notably folding the menubar into the header image and switching the layout to a one-column format.</p>
<p>I&#8217;ve also enabled comments again.  I turned them off almost immediately after starting the site when I had blog spam problems, but it has become increasingly clear to me that this site exists primarily in order to solicit feedback and it does a poor job of that with comments disabled.</p>
<p>If anyone finds the theme interesting, I&#8217;ve packaged it up to make it easy to use with WordPress 2.x.  To install, download <a href="/files/2006/wuhan_lococo-0.4.1.zip">wuhan_lococo-0.4.1.zip</a>, unzip, upload into /wp-content/themes/, and select it as your default theme in the wp-admin interface.  If you&#8217;re new to using themes in WordPress, check out the official <a href="http://codex.wordpress.org/Using_Themes">theme documentation</a> or leave a question in the comments.</p>
<p><b>Update, 4/25/05:</b>  There&#8217;s now a project page for the theme at <a href="/projects/wucoco/">http://mikelococo.com/projects/wucoco</a> where you can find more information as well as downloads for the latest packaged version.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/03/new-skin-for-the-old-ceremony/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrading WordPress</title>
		<link>http://mikelococo.com/2006/03/upgrading-wordpress/</link>
		<comments>http://mikelococo.com/2006/03/upgrading-wordpress/#comments</comments>
		<pubDate>Tue, 07 Mar 2006 00:10:31 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[maintenance]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/2006/03/upgrading-wordpress/</guid>
		<description><![CDATA[Beware of drastic changes in the appearance of the site while I&#8217;m fixing it up over the next few days. There may also be short outages while I perform upgrades to the backend.]]></description>
			<content:encoded><![CDATA[<p>Beware of drastic changes in the appearance of the site while I&#8217;m fixing it up over the next few days.  There may also be short outages while I perform upgrades to the backend.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/03/upgrading-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fun, With Punctuation</title>
		<link>http://mikelococo.com/2006/02/fun-with-punctuation/</link>
		<comments>http://mikelococo.com/2006/02/fun-with-punctuation/#comments</comments>
		<pubDate>Sat, 04 Feb 2006 21:55:11 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[friends]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/?p=105</guid>
		<description><![CDATA[Everybody&#8217;s talking &#8217;bout the new sound, funny but[t]. It&#8217;s still rock and roll to me. It&#8217;s especially funny if you can sound exasperated and lisp, sort of like Napolean Dynamite meets Butthead. I was recently contacted by a childhood friend &#8230; <a href="http://mikelococo.com/2006/02/fun-with-punctuation/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><em>Everybody&#8217;s talking &#8217;bout the new sound, funny but[t].  It&#8217;s still rock and roll to me.</em>  It&#8217;s especially funny if you can sound exasperated and lisp, sort of like Napolean Dynamite meets Butthead.</p>
<p>I was recently contacted by a childhood friend whom I remember fondly for his Butthead impressions.  He&#8217;s the first friend or foe to find me through my website, although I suspect he won&#8217;t be the last.  Lately I&#8217;ve had an increasing number of where-are-they-now conversations, even with friends who typically don&#8217;t care where &#8220;they&#8221; ended up.  I think we may be hitting the age when that sort of thing becomes common.</p>
<p>Anyway if you&#8217;ve wondered about where Sean/Christopher/Jonathan Fallon or Paul/Jeff Chenkus are now, check out their tech news blog at <a href="http://nerdapproved.com/">nerdapproved.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2006/02/fun-with-punctuation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A70 Service Notice</title>
		<link>http://mikelococo.com/2005/11/a70-service-notice/</link>
		<comments>http://mikelococo.com/2005/11/a70-service-notice/#comments</comments>
		<pubDate>Wed, 09 Nov 2005 01:13:18 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[Canon A70]]></category>
		<category><![CDATA[ccd]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[recall]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/?p=104</guid>
		<description><![CDATA[Some time ago, I wrote about my Canon A70 digital camera failing, and the subsequent replacement adventures I went through. It turns out I wasn&#8217;t the only one, the problem was quite widespread and affected several manufacturers. The fiasco is &#8230; <a href="http://mikelococo.com/2005/11/a70-service-notice/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Some time ago, I wrote about my Canon A70 digital <a href="/2005/03/camera-drama/">camera failing</a>, and the subsequent replacement adventures I went through.  It turns out I wasn&#8217;t the only one, the problem was quite widespread and affected several manufacturers.  The fiasco is documented in <a href="http://www.imaging-resource.com/NEWS/1128958202.html">excruciating</a> <a href="http://www.imaging-resource.com/NEWS/1128632808.html">detail</a> at <a href="http://www.imaging-resource.com/badccds.html">imaging-resource.com</a>, and Canon has published a service notice on the <a href="http://consumer.usa.canon.com/ir/controller?act=PgComSmModDisplayAct&#038;keycode=2112&#038;fcategoryid=221&#038;modelid=8776">A70 product page</a>.</p>
<p>The short of it is that Canon is offering to repair affected cameras at no charge regardless of warranty status.  Call them up, mention the service notice and that you&#8217;d like a free CCD evaluation.  They&#8217;ll ask you to go through some troubleshooting steps and if it looks like you have a bad CCD they&#8217;ll fix it for free (even covering shipping costs in both directions, which never happens).</p>
<p>I&#8217;m very impressed with how Canon has handled this.  I experienced short hold times, and got no hassle from the phone techs.  I was assured that the evaluation and shipping would be free even if the factory techs found that my camera&#8217;s problem wasn&#8217;t covered by the service notice, so I didn&#8217;t feel nervous about sending it in at all.  It took about two weeks to get my camera back in good repair, and I think they fixed a slight mechanical problem with the lens cover for free as well.  It&#8217;s great when a company takes a bad situation like this and turns it into an opportunity to provide great customer service.  Kudos to Canon.</p>
<p>Anyway, now I have an extra camera.  I think that the A70 will be handed down to Fio, so he can continue to develop his <a href="/2005/01/this-just-in/">film portfolio</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/11/a70-service-notice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More on Dubai</title>
		<link>http://mikelococo.com/2005/07/more-on-dubai/</link>
		<comments>http://mikelococo.com/2005/07/more-on-dubai/#comments</comments>
		<pubDate>Mon, 01 Aug 2005 03:36:52 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[dubai]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/?p=102</guid>
		<description><![CDATA[The more avid readers among you may have noticed that Hal&#8217;s posts have disappeared. It would appear that he was too honest for his own good, and he has chosen to self-censor rather than offend those who inspired him. We&#8217;ll &#8230; <a href="http://mikelococo.com/2005/07/more-on-dubai/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The more avid readers among you may have noticed that Hal&#8217;s posts have disappeared.  It would appear that he was too honest for his own good, and he has chosen to self-censor rather than offend those who inspired him.  We&#8217;ll all have to look forward to the book.</p>
<p>In the meantime, we&#8217;ll close his epoch on the site with some links about  <a href="http://www.tomdispatch.com/index.mhtml?pid=5807">Dubai</a> (via <a href="http://www.boingboing.net/2005/07/15/dubai_is_a_creepy_bu.html">BoingBoing</a>).  If Walt Disney were alive today, he&#8217;d build a brothel there (we&#8217;ve had numerous visitors stumble upon this very site searching for prostitutes in Dubai).  Home of the new New Urbanism, and (formerly) the biggest bowl of spaghetti, Dubai is where the end begins.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/07/more-on-dubai/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My House</title>
		<link>http://mikelococo.com/2005/06/my-house/</link>
		<comments>http://mikelococo.com/2005/06/my-house/#comments</comments>
		<pubDate>Fri, 03 Jun 2005 02:58:39 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[house]]></category>
		<category><![CDATA[photo]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/?p=96</guid>
		<description><![CDATA[&#8230;is a very very very fine house. There are, in fact two cats in the yard, although neither of them are mine. Lots of folks haven&#8217;t seen my place even though I&#8217;ve lived here almost a year, so now you &#8230; <a href="http://mikelococo.com/2005/06/my-house/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>&#8230;is a very very very fine house. There are, in fact two cats in the yard, although neither of them are mine. Lots of folks haven&#8217;t seen my place even though I&#8217;ve lived here almost a year, so now you can experience the experience of the comfort of my own home without leaving the comfort of your own home. It&#8217;s like magic. Click the map to be whisked away&#8230;</p>
<p><MAP NAME=tourmap><AREA HREF="/images/2005/virtualtour/office.jpg" ALT="my office" COORDS="32,39,149,120"><AREA HREF="/images/2005/virtualtour/bedroom.jpg" ALT="my bedroom" COORDS="33,123,144,214"><AREA HREF="/images/2005/virtualtour/living-room.jpg" ALT="the living room" COORDS="214,43,382,212"></MAP><img src="/images/2005/virtualtour/tour.jpg" alt="Virtual tour floorplan" USEMAP="#tourmap" /></p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/06/my-house/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blogging the Blog</title>
		<link>http://mikelococo.com/2005/05/blogging-the-blog/</link>
		<comments>http://mikelococo.com/2005/05/blogging-the-blog/#comments</comments>
		<pubDate>Thu, 19 May 2005 17:23:53 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>

		<guid isPermaLink="false">http://lococo.org/mike/?p=88</guid>
		<description><![CDATA[I&#8217;m going to attempt to make the transition from solo to group publication. Hal is the first additional contributor, and has already begun titillating audiences with the elegant writing style and unique perspective given voice is his recent post (yes, &#8230; <a href="http://mikelococo.com/2005/05/blogging-the-blog/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m going to attempt to make the transition from solo to group publication.  Hal is the first additional contributor, and has already begun titillating audiences with the elegant writing style and unique perspective given voice is his recent post (yes, this thing is on).</p>
<p>Things will be shifting around in the next couple weeks as I do some house cleaning and make the technical changes necessary to support more writers.  If this experiment is successful, we may gather more interested folk in exactly the way that a rolling stone fails to gather moss.</p>
<p>Keep your eyes peeled&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/05/blogging-the-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>exif_touch</title>
		<link>http://mikelococo.com/2005/05/exif_touch/</link>
		<comments>http://mikelococo.com/2005/05/exif_touch/#comments</comments>
		<pubDate>Tue, 10 May 2005 23:01:34 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[exif]]></category>
		<category><![CDATA[timestamps]]></category>

		<guid isPermaLink="false">/?p=85</guid>
		<description><![CDATA[See the permanent URL for information about exif-touch.]]></description>
			<content:encoded><![CDATA[<p>See the permanent URL for information about <a href="/projects/exif-touch/">exif-touch</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/05/exif_touch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dishes</title>
		<link>http://mikelococo.com/2005/05/dishes/</link>
		<comments>http://mikelococo.com/2005/05/dishes/#comments</comments>
		<pubDate>Sun, 08 May 2005 21:56:02 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[dishes]]></category>
		<category><![CDATA[photo]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">/?p=84</guid>
		<description><![CDATA[Hmm&#8230; perhaps I should do the dishes.]]></description>
			<content:encoded><![CDATA[<p>Hmm&#8230; perhaps I should do the <a href="/files/2005/dishes.gif">dishes</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/05/dishes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fun with Camera</title>
		<link>http://mikelococo.com/2005/04/fun-with-camera/</link>
		<comments>http://mikelococo.com/2005/04/fun-with-camera/#comments</comments>
		<pubDate>Sun, 17 Apr 2005 23:03:11 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[photo]]></category>

		<guid isPermaLink="false">/?p=80</guid>
		<description><![CDATA[I&#8217;ve had my camera for a couple of weeks now and have been snapping away like mad. Some patterns that caught me eye&#8230;]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve had my camera for a couple of weeks now and have been snapping away like mad.  Some patterns that caught me eye&#8230;</p>
<div><a target="_blank" href="/images/2005/funwithcamera/img002.jpg"><img src="/images/2005/funwithcamera/img002.jpg" /></a></div>
<p><span id="more-80"></span></p>
<div><a target="_blank" href="/images/2005/funwithcamera/img000.jpg"><img src="/images/2005/funwithcamera/t/img000.jpg" /></a> <a target="_blank" href="/images/2005/funwithcamera/img005.jpg"><img src="/images/2005/funwithcamera/t/img005.jpg" /></a></div>
<div><a target="_blank" href="/images/2005/funwithcamera/img003.jpg"><img src="/images/2005/funwithcamera/t/img003.jpg" /></a> <a target="_blank" href="/images/2005/funwithcamera/img004.jpg"><img src="/images/2005/funwithcamera/t/img004.jpg" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/04/fun-with-camera/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Labs â€“ Problem 3</title>
		<link>http://mikelococo.com/2005/04/google-labs-problem-3/</link>
		<comments>http://mikelococo.com/2005/04/google-labs-problem-3/#comments</comments>
		<pubDate>Tue, 12 Apr 2005 02:55:48 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>

		<guid isPermaLink="false">/?p=81</guid>
		<description><![CDATA[Google likes to put cute math problems in their employment ads.The first time I saw this was when they took out an ad in the Cornell Daily Sun, and I thought it was amusing enough to clip and hang on &#8230; <a href="http://mikelococo.com/2005/04/google-labs-problem-3/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Google likes to <a href="http://news.zdnet.co.uk/business/employment/0,39020648,39160024,00.htm">put</a> <a href="http://googleblog.blogspot.com/2004/07/warning-we-brake-for-number-theory.html">cute</a> <a href="http://googleblog.blogspot.com/2004/09/pencils-down-people.html">math</a> <a href="http://homepage.mac.com/asilber/googlefax/">problems</a> in their employment ads.The first time I saw this was when they took out an ad in the <a href="http://www.cornellsun.com/">Cornell Daily Sun</a>, and I thought it was amusing enough to clip and hang on the wall of my geek cave.</p>
<p><a href="/files/2005/googlelabs-problem3/googlelabs-problem3.jpg"><img alt="Photo of problem." src="/files/2005/googlelabs-problem3/googlelabs-problem3-thumb.jpg" /></a></p>
<p>This weekend I caught the bug to solve it and see if I&#8217;m smart enough to work at Google.  Apparently I&#8217;m not, because I ended up cheating when I checked my initial (and I thought correct) solution against what others had <a href="http://equars.com/~marco/google.html">found</a>.  By the time I realized I had made a mistake, I also realized what I needed to do to correct it.  I did independently fix my code (as evidenced by its extreme ugliness).  <a href="/files/2005/googlelabs-problem3/googlelabs-problem3.perl">Download it</a>, smack it up, flip it, rub it down, oh no.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/04/google-labs-problem-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Camera Drama</title>
		<link>http://mikelococo.com/2005/03/camera-drama/</link>
		<comments>http://mikelococo.com/2005/03/camera-drama/#comments</comments>
		<pubDate>Fri, 01 Apr 2005 02:35:36 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[Canon A70]]></category>
		<category><![CDATA[Canon S1 IS]]></category>
		<category><![CDATA[photography]]></category>

		<guid isPermaLink="false">/?p=79</guid>
		<description><![CDATA[My Canon A70 digital camera gave up the ghost after a year a half. Luckily, the folks servicing my Staples extended warranty came through and cut me a check for the purchase price of the camera, after determining that the &#8230; <a href="http://mikelococo.com/2005/03/camera-drama/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><img src="/images/2005/dead-camera.jpg" alt="My old digital camera died." align="left" width="200" height="150" hspace="7"/></p>
<p>My <a href="http://www.dpreview.com/reviews/specs/Canon/canon_a70.asp">Canon A70</a> digital camera gave up the ghost after a year a half.  Luckily, the folks servicing my Staples extended warranty came through and cut me a check for the purchase price of the camera, after determining that the repair was too expensive to bother with.</p>
<p><b>Update 9/2/05:</b>  It&#8217;s worth mentioning that Staples was more of a pain than I first thought to deal with.  They originally sent me a Staples gift card (after telling me I would get a check, and which arrived after I had already bought my new camera at Best Buy), and it took me over 2 months of frequent follow-up calls to get my check.</p>
<p>This put me in the market for another camera.  I wanted something with a longer zoom.  I was always trying to shoot things with the A70 that were too small or too far away to frame properly with the 3x lens.  I eventually decided on another Canon, the <a href="http://www.dpreview.com/reviews/specs/Canon/canon_s1is.asp">Powershot S1 IS</a>, which has a 10x zoom (equivalent to a 38mm-380mm lens on a traditional SLR camera).  It&#8217;s only 3.2 megapixels, but since I rarely print photos I have never felt limited by resolution.  After using it for a few days, I find that I enjoy using this camera much more than my last one.  In addition to the big zoom, it has several features that make it fun to shoot with:</p>
<ul>
<li><b>Good Controls:</b>  Almost everything I do while shooting can be done in one or two button presses without taking my eye off the &#8220;action&#8221;.  I almost never need to use a menu when setting up a shot.</li>
<li><b>Electronic Viewfinder:</b>  The badness of the A70 viewfinder defies description.  I never ever used it, no matter how much I had to squint to see the LCD screen in the sun.  The viewfinder in the S1 IS is nice, I like it better than the LCD most of the time.
<li><b>Focus Zoom:</b>  While adjusting the manual focus, a zoom view automatically pops up so you can see what you&#8217;re doing.  This combined with the well designed controls make manual focus a worthwhile alternative when the auto focus has trouble (which it sometimes does in very flat scenes or in low light).</li>
<li><b>Sleep Mode:</b>  The camera optionally switches into a low power mode after a short period of inactivity, and it can wake up again in less than a second.</li>
<li><b>Intervalometer:</b>  The camera can shoot unattended at regular intervals.  Most people wouldn&#8217;t care about this, but I think it&#8217;s great and I use it all the time.</li>
<li><b>Image Stabilization:</b> This feature is supposed to smooth out the natural movement of your hand, allowing you to shoot longer exposures than you would otherwise be able to without blurring the image.  I expected that it would work so poorly as to be worthless, but I&#8217;ve been pleasantly surprised.  I hate flashes, and the IS has allowed me to get halfway decent shots using available light in situations where I would otherwise end up with a blurry mess.  My most amusing IS shot to date is a 1 second handheld exposure that looks soft but not sloppy.</li>
</ul>
<p>I did briefly consider getting a 5 megapixel superzoom.  I even went so far as to purchase a <a href="http://www.dpreview.com/reviews/specs/Kodak/kodak_dx7590.asp">Kodak DX7590</a> on impulse because it was 5 megapixels and had a big, beautiful LCD display.  I ended up returning it unopened after reading that it has substandard image quality and long write delays.  There are some recently released 5mp superzooms that are supposed to be very nice, but they are also substantially more expensive than the S1 IS, so at least for now I&#8217;m not second guessing my choice.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/03/camera-drama/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Right to Disinterest</title>
		<link>http://mikelococo.com/2005/02/right-to-disinterest/</link>
		<comments>http://mikelococo.com/2005/02/right-to-disinterest/#comments</comments>
		<pubDate>Tue, 01 Mar 2005 04:45:31 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[soapbox]]></category>
		<category><![CDATA[first amendment]]></category>

		<guid isPermaLink="false">/?p=77</guid>
		<description><![CDATA[My interest was piqued when I came across this CNN story about a recent survey asking high school students, faculty, and principals about the first amendment. Even though I don&#8217;t normally post news commentary, I found some moderately amusing facts &#8230; <a href="http://mikelococo.com/2005/02/right-to-disinterest/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>My interest was piqued when I came across this CNN story about a recent <a href="http://firstamendment.jideas.org/downloads.php">survey</a> asking high school students, faculty, and principals about the first amendment. Even though I don&#8217;t normally post news commentary, I found some moderately amusing facts that I didn&#8217;t see noted elsewhere&#8230;</p>
<p>Update: CNN seems to have taken down their writeup, so I removed the link.</p>
<p>It&#8217;s true that the results are pretty distressing, the students did atrociously on the fact-based questions in the survey. A disturbing percentage of them also seemed willing to accept moderate or even severe limitations on freedoms of speech and press. They didn&#8217;t fare too much worse than faculty and administrators at their schools, though, and it&#8217;s hard to imagine how students could have done well given the knowledge of those responsible for their education.  The poor performance of teachers was downplayed in articles about the study and is not mentioned at all in the key findings of the study itself.</p>
<ul>
<li>Nearly half of the teachers surveyed don&#8217;t feel that musicians should be allowed to sing songs with lyrics that might be offensive to some. Younger generations are a little more liberal, less than a third of the students felt similarly.</li>
<li>One out of five teachers aren&#8217;t sure that newspapers should be allowed to publish stories without government approval, but surprisingly almost half of the students feel the same way. Perhaps it&#8217;s only a coincidence that most high school faculty and principals feel that student papers should require the approval of school authorities.</li>
<li>Three quarters of the students surveyed incorrectly believe that it&#8217;s illegal to burn a flag in political protest. One third of the teachers are under the same misconception, and apparently they&#8217;re doing a fantastic job getting through to their students on that issue.</li>
<li>Half of the students incorrectly believe that the government can restrict indecent content on the internet. Faculty and principals don&#8217;t know, either&#8230; also evenly split. It&#8217;s a funny question, though. The government absolutely does regulate content on the internet. There are currently existing federal statutes restricting the distribution of <a href="http://www.adultweblaw.com/laws/obscene.htm">obscene material</a> and <a href="http://www.adultweblaw.com/laws/childporn.htm">child pornography</a>.  A 1997 <a href="http://www.law.cornell.edu/supct/html/96-511.ZS.html">Supreme Court ruling</a> did narrow the scope of material restricted by the Communications Decency Act by allowing publication of &#8220;indecent&#8221; material, leaving in place restrictions on &#8220;obscene&#8221; material&#8230; but it seems a little dishonest to write a survey question directed at high-school students whose correct interpretation depends on the definition of a word that had its meaning disputed all the way to the Supreme Court.</li>
<li>More than half of faculty and principals surveyed think they&#8217;re doing a good job teaching about first amendment freedoms.</li>
<li>2% of faculty aren&#8217;t certain what the highest level of education they received was. Kudos to the survey team for anticipating the need for a &#8220;Don&#8217;t know&#8221; option on that question.</li>
</ul>
<p>The survey, partially funded by the <a href="http://www.knightfdn.org/">Knight Foundation</a>, didn&#8217;t explore non-governmental impediments to free information flow, such as consolidated media markets.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/02/right-to-disinterest/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Badger Cello</title>
		<link>http://mikelococo.com/2005/01/badger-cello/</link>
		<comments>http://mikelococo.com/2005/01/badger-cello/#comments</comments>
		<pubDate>Fri, 21 Jan 2005 23:52:47 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[anagram]]></category>
		<category><![CDATA[Cornell University]]></category>

		<guid isPermaLink="false">/?p=73</guid>
		<description><![CDATA[Anagrams are fun and educational. Cornell University can be rearranged to spell lots of fun things (not all of them appropriate for children). Find out which one is on the back of my car! It kind of looks like it &#8230; <a href="http://mikelococo.com/2005/01/badger-cello/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Anagrams are fun and educational.  Cornell University can be rearranged to spell lots of fun things (not all of them appropriate for children).  Find out which one is on the back of my car!</p>
<p><span id="more-73"></span></p>
<p><img alt="cleverly into ruins" src="/images/2005/cleverly-into-ruins.jpg" /></p>
<p>It kind of looks like it was stuck to the window by a three year old, but it brings me great joy nonetheless.  Go play on the <a href="http://www.wordsmith.org/anagram/">Internet Anagram Server</a>, or read some of my other favorites:</p>
<ul>
<li>cruellest ivory inn</li>
<li>nor ivy slut recline</li>
<li>recently loin virus</li>
<li>cleverly i iron nuts</li>
<li>cleverly i ruin snot</li>
<li>run evilly snort ice</li>
<li>i run celery in volts</li>
<li>yon vertices run ill</li>
<li>vinyl silencer tour</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/01/badger-cello/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>This Just Inâ€¦</title>
		<link>http://mikelococo.com/2005/01/this-just-in/</link>
		<comments>http://mikelococo.com/2005/01/this-just-in/#comments</comments>
		<pubDate>Thu, 06 Jan 2005 03:27:35 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[christmas]]></category>
		<category><![CDATA[family]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">/?p=70</guid>
		<description><![CDATA[Please enjoy this special holiday video report brought to you by Fio and Uncle Mike, there&#8217;s some great footage in it. Coming to you from the Lococo household in Massachusetts, Fio&#8217;s reportage unearths a poignant story of holiday cheer that&#8217;s &#8230; <a href="http://mikelococo.com/2005/01/this-just-in/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Please enjoy this special holiday video report brought to you by Fio and Uncle Mike, there&#8217;s some great footage in it.  Coming to you from the Lococo household in Massachusetts, Fio&#8217;s reportage unearths a poignant story of holiday cheer that&#8217;s not to be missed.</p>
<p><a href="/files/2005/christmasfio-2004.mp4"><img width="132" height="109" align="left" alt="video thumbnail" src="/images/2005/this-just-in.jpg" /></a><br />
Filesize: ~3.4M<br />
License:  all rights reserved<br clear="all" /></p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2005/01/this-just-in/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Christmas in Boston</title>
		<link>http://mikelococo.com/2004/12/christmas-in-boston/</link>
		<comments>http://mikelococo.com/2004/12/christmas-in-boston/#comments</comments>
		<pubDate>Sat, 01 Jan 2005 00:39:43 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[christmas]]></category>
		<category><![CDATA[family]]></category>
		<category><![CDATA[photo]]></category>

		<guid isPermaLink="false">/?p=67</guid>
		<description><![CDATA[Christmas in Boston, Fio was a riot whizzing around in his NASA space shuttle &#8220;jetpack&#8221;. He borrowed my camera to document his favorite gifts, and took the photo of the space shuttle puzzle.]]></description>
			<content:encoded><![CDATA[<p>Christmas in Boston, Fio was a riot whizzing around in his NASA space shuttle &#8220;jetpack&#8221;. He borrowed my camera to document his favorite gifts, and took the photo of the space shuttle puzzle.</p>
<div><a target="_blank" href="/images/2004/christmas04/img003.jpg"><img src="/images/2004/christmas04/t/img003.jpg" /></a></div>
<p><span id="more-67"></span></p>
<div><a target="_blank" href="/images/2004/christmas04/img004.jpg"><img src="/images/2004/christmas04/t/img004.jpg" /></a> <a target="_blank" href="/images/2004/christmas04/img002.jpg"><img src="/images/2004/christmas04/t/img002.jpg" /></a> <a target="_blank" href="/images/2004/christmas04/img005.jpg"><img src="/images/2004/christmas04/t/img005.jpg" /></a></div>
<div><a target="_blank" href="/images/2004/christmas04/img000.jpg"><img src="/images/2004/christmas04/t/img000.jpg" /></a> <a target="_blank" href="/images/2004/christmas04/img001.jpg"><img src="/images/2004/christmas04/t/img001.jpg" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/12/christmas-in-boston/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>(Let It Snow)^3</title>
		<link>http://mikelococo.com/2004/12/let-it-snow3/</link>
		<comments>http://mikelococo.com/2004/12/let-it-snow3/#comments</comments>
		<pubDate>Sun, 19 Dec 2004 20:39:25 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[photo]]></category>

		<guid isPermaLink="false">/?p=66</guid>
		<description><![CDATA[The first snowstorm with a couple inches of accumulation always announces the &#8220;real&#8221; arrival of winter in my mind. That was today in Ithaca, and Laura and I went on a winter walkabout to bring the experience to you.]]></description>
			<content:encoded><![CDATA[<p>The first snowstorm with a couple inches of accumulation always announces the &#8220;real&#8221; arrival of winter in my mind. That was today in Ithaca, and Laura and I went on a winter walkabout to bring the experience to you.</p>
<div><a target="_blank" href="/images/2004/letitsnow/img_3368.jpg"><img src="/images/2004/letitsnow/t/img_3368.jpg" /></a></div>
<p><span id="more-66"></span></p>
<div><a target="_blank" href="/images/2004/letitsnow/img_3371.jpg"><img src="/images/2004/letitsnow/t/img_3371.jpg" /></a> <a target="_blank" href="/images/2004/letitsnow/img_3372.jpg"><img src="/images/2004/letitsnow/t/img_3372.jpg" /></a></div>
<div><a target="_blank" href="/images/2004/letitsnow/img_3362.jpg"><img src="/images/2004/letitsnow/t/img_3362.jpg" /></a> <a target="_blank" href="/images/2004/letitsnow/img_3380.jpg"><img src="/images/2004/letitsnow/t/img_3380.jpg" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/12/let-it-snow3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Intertwingle</title>
		<link>http://mikelococo.com/2004/12/intertwingle/</link>
		<comments>http://mikelococo.com/2004/12/intertwingle/#comments</comments>
		<pubDate>Mon, 13 Dec 2004 22:47:44 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[personal]]></category>
		<category><![CDATA[final cut pro]]></category>
		<category><![CDATA[fxscript]]></category>
		<category><![CDATA[programmatic art]]></category>

		<guid isPermaLink="false">/?p=64</guid>
		<description><![CDATA[Filesize: ~600K License: by-nc-sa This is another automated art project and a bit of a work in progress. Some time ago I wrote an FXScript for Final Cut Pro 3.0 that edited a movie to run forward and backward, interleaving &#8230; <a href="http://mikelococo.com/2004/12/intertwingle/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="/files/2004/intertwingle.mp4"><img align="left" alt="intertwingle-video-thumbnail" src="/images/2004/intertwingle.jpg" /></a><br />
Filesize: ~600K<br />
License: <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">by-nc-sa</a><br clear="all" /></p>
<p>This is another automated art project and a bit of a work in progress.  Some time ago I wrote an <a href="http://fxscriptreference.org/">FXScript</a>  for Final Cut Pro 3.0 that edited a movie to run forward and backward, interleaving the frames instead of compositing them.  This is the test video I used as I was writing the script, you can still see (but not read in this heavily compressed version) the variables I was tracking on-screen while I debugged.</p>
<p>Someday I hope to revisit this project on a less awkward programming platform.  FXScript was difficult to do automated editing with because it assumed (as of FCP3, anyway) a linear flow through the video material.  I&#8217;m still on the lookout for a good high-level way to automate video editing.  Quicktime Pro might do what I want in combination with Applescript or Perl/PerlMagick, but I haven&#8217;t investigated deeply yet.</p>
<p>I&#8217;m not providing the FXScript I used to create this, only because I think there are better ways.  Contact me if you really want a copy.</p>
<p>As much as wish I had, I did not think of the word <a href="http://www-archive.mozilla.org/blue-sky/misc/199805/intertwingle.html">intertwingle</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/12/intertwingle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mohawk</title>
		<link>http://mikelococo.com/2004/11/mohawk/</link>
		<comments>http://mikelococo.com/2004/11/mohawk/#comments</comments>
		<pubDate>Sun, 07 Nov 2004 07:44:59 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[mohawk]]></category>
		<category><![CDATA[photo]]></category>

		<guid isPermaLink="false">/?p=63</guid>
		<description><![CDATA[I&#8217;m in the process of putting up lots of old junk that I&#8217;ve told people about but often haven&#8217;t been able to show them. Last time I shaved my head I kept a mohawk for a week. It&#8217;s funny to &#8230; <a href="http://mikelococo.com/2004/11/mohawk/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m in the process of putting up lots of old junk that I&#8217;ve told people about but often haven&#8217;t been able to show them. Last time I shaved my head I kept a mohawk for a week. It&#8217;s funny to have people look at you like you&#8217;re attached to your hair, but the novelty wears off pretty fast.</p>
<div><a target="_blank" href="/images/2004/mohawk/img_1176.jpg"><img src="/images/2004/mohawk/t/img_1176.jpg" /></a> <a target="_blank" href="/images/2004/mohawk/img_1174.jpg"><img src="/images/2004/mohawk/t/img_1174.jpg" /></a></div>
<p><b>Update 3/20/06:</b>  Since a few hundred folks a month seem to be finding this site searching for information about mohawks, a short update is in order.  I used Rave #4 (aka mega) hairspray to hold the spikes, which is cheap and works well.  Elmer&#8217;s or spraypaint will get you more cred, but it&#8217;s unlikely that someone searching for hair advice on the internet is going to last very long with folks that spike with spraypaint under any circumstances.  For that reason, I recommend sticking with something you won&#8217;t have to shave out until you have your sea-legs.  The process of styling isn&#8217;t rocket science, but it does take a long time while you&#8217;re figuring it out and you really want a blowdryer.  The tall spikes take a few layers of spray to stand up right and waiting for half a can of hairspray to air dry is not really an option.</p>
<p>p.s.  I&#8217;ll send a surprise gift to the first person who can figure out what the sign I&#8217;m holding is about.</p>
<p><b>Update 5/13/06:</b> The prize has been collected.  The photo is a reference to Johnny Cash&#8217;s drug arrest while crossing the Mexican border in 1965.  Although Cash doesn&#8217;t have a Mohawk in his mugshot, he was punk before hairspray was king.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/11/mohawk/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Giant Rainbow</title>
		<link>http://mikelococo.com/2004/11/giant-rainbow/</link>
		<comments>http://mikelococo.com/2004/11/giant-rainbow/#comments</comments>
		<pubDate>Sat, 06 Nov 2004 12:06:52 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[photo]]></category>
		<category><![CDATA[rainbow]]></category>

		<guid isPermaLink="false">/?p=62</guid>
		<description><![CDATA[I saw a giant rainbow over the summer. It rocked.]]></description>
			<content:encoded><![CDATA[<p>I saw a giant rainbow over the summer.  It rocked.</p>
<div><a target="_blank" href="/images/2004/rainbow/rainbow-web.jpg"><img width="200" vspace="3" hspace="3" height="79" border="0" src="/images/2004/rainbow/t/rainbow-web.jpg" /></a> <a target="_blank" href="/images/2004/rainbow/rainbow2-web.jpg"><img width="200" vspace="3" hspace="3" height="70" border="0" src="/images/2004/rainbow/t/rainbow2-web.jpg" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/11/giant-rainbow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Study in Gray</title>
		<link>http://mikelococo.com/2004/11/study-in-gray/</link>
		<comments>http://mikelococo.com/2004/11/study-in-gray/#comments</comments>
		<pubDate>Mon, 01 Nov 2004 21:40:22 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[geekery]]></category>
		<category><![CDATA[personal]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[programmatic art]]></category>

		<guid isPermaLink="false">/?p=61</guid>
		<description><![CDATA[study_in_gray_2x2 study_in_gray_3x2 The recent proliferation of high level computer programming languages has made it possible for non-expert users to write interesting programs without getting bogged down in technical specifics. In particular, the availability of libraries and API&#8217;s that provide high-level, &#8230; <a href="http://mikelococo.com/2004/11/study-in-gray/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><img src="/images/2004/studyingray/2x2.png" alt="2x2.png" align="baseline" width="32" height="32" /><br />
<em>study_in_gray_2x2</em></p>
<p><img src="/images/2004/studyingray/3x2.png" alt="3x2.png" align="baseline" width="192" height="128" /><br />
<em>study_in_gray_3x2</em></p>
<p>The recent proliferation of high level computer programming languages has made it possible for non-expert users to write interesting programs without getting bogged down in technical specifics.  In particular, the availability of libraries and API&#8217;s that provide high-level, user-oriented data primitives like pixels and video frames are very interesting because they allow users to approach visual tasks without having to understand how the computer internally represents visual data.</p>
<p>This series of images was born out of an interest in the repetition of very simple actions on an inhuman scale, and as a study in the nature of discrete verus continuous media.  A 3-panel by 3-panel digital print measuring about 2 1/2&#8242; square was displayed as the only ugly and conceptual work in the 2004 staff art show at Cornell University.</p>
<p>The <a target="_self" href="/files/2004/study_in_gray.perl">script</a> used to generate the images is GPL&#8217;ed.  It should run on any system with Perl and PerlMagick available.  The images in the <em>study_in_gray</em> series are released into the public domain.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/11/study-in-gray/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is the Federal Register?</title>
		<link>http://mikelococo.com/2004/10/what-is-the-federal-register/</link>
		<comments>http://mikelococo.com/2004/10/what-is-the-federal-register/#comments</comments>
		<pubDate>Sat, 23 Oct 2004 13:54:21 +0000</pubDate>
		<dc:creator>Mike Lococo</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[federalregister]]></category>

		<guid isPermaLink="false">/?p=60</guid>
		<description><![CDATA[It has been brought to my attention that 5 out of 5 otherwise intelligent and well-informed people have almost no clue what the Federal Register is. It&#8217;s where the action is in the Federal Government. If you have a question &#8230; <a href="http://mikelococo.com/2004/10/what-is-the-federal-register/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>It has been brought to my attention that 5 out of 5 otherwise intelligent and well-informed people have almost no clue what the <a target="_blank" href="http://www.gpoaccess.gov/fr/about.html">Federal Register</a> is.  It&#8217;s where the action is in the Federal Government.  If you have a question about a proposed law, an executive order by the president, a new FDA rule, or a recent change in FCC policy&#8230; the answer is in the Federal Register.  But really none of that is important.  The only thing you need to know about the Federal Register is that Ralph and I share a foodnote on page 12149 of Volume 67.</p>
]]></content:encoded>
			<wfw:commentRss>http://mikelococo.com/2004/10/what-is-the-federal-register/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

