<?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>John Hattaway &#187; Technology and Gadgets</title>
	<atom:link href="http://www.johnhattaway.com/category/technology-and-gadgets/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johnhattaway.com</link>
	<description>Everyone is entitled to their secrets, even if those secrets are obvious.</description>
	<lastBuildDate>Fri, 30 Jul 2010 01:32:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>The White Screen or what happens when hard drives go to heaven</title>
		<link>http://www.johnhattaway.com/2009/05/the-white-screen-or-what-happens-when-hard-drives-go-to-heaven/</link>
		<comments>http://www.johnhattaway.com/2009/05/the-white-screen-or-what-happens-when-hard-drives-go-to-heaven/#comments</comments>
		<pubDate>Sat, 16 May 2009 03:57:48 +0000</pubDate>
		<dc:creator>smokingpen</dc:creator>
				<category><![CDATA[On Writing]]></category>
		<category><![CDATA[Technology and Gadgets]]></category>

		<guid isPermaLink="false">http://www.johnhattaway.com/?p=1859</guid>
		<description><![CDATA[So, I got home from work this morning, did my thing-a-tee-thing and then sat down for some brief, but good, computer time. Yesterday was, in part, spent moving my desk around in the office, inserting large window A/C into small window, and making sure I was set-up and comfortable. On top of which, the thoughts [...]]]></description>
			<content:encoded><![CDATA[<p>So, I got home from work this morning, did my thing-a-tee-thing and then sat down for some brief, but good, computer time. Yesterday was, in part, spent moving my desk around in the office, inserting large window A/C into small window, and making sure I was set-up and comfortable. On top of which, the thoughts and just missing wife and child who are in Utah for a few days was enough to cause me to not get good sleep. Anyway, was sitting at my computer, minding my own business, when all of the sudden everything locks up, I get the weird rainbow thinking logo Apple uses these days, and then nothing. After quite a few minutes of attempting to get the computer to force quit the application that appeared to be locked up I shut the system down. When I restarted I got what is called (online) <strong>the white screen of death</strong>.</p>
<p>The white screen of death, I am sure aptly named by ex-<strong>Microsoft</strong> detractors, is what happens when the hard drive on the computer won&#8217;t mount. I did the reasonably sane thing, pulled out the <a title="Apple :: iPhone" href="http://www.apple.com/iphone/" target="_blank">iPhone</a>, and started searching for possible fixes for the problem. Allow another hour of elapsed time and I realize there really is no way of getting around packing the computer up and taking it to the closest, or one of the closest, <a title="Apple :: store" href="http://www.apple.com/retail/" target="_blank">Apple store</a> so their well advertised Geniuses at the <a title="Apple :: store :: Genius Bar" href="http://www.apple.com/retail/geniusbar/" target="_blank">Genius Bar</a> could look at it. For those who are in the need to know, you can actually schedule a time from home to visit one of these geniuses. In my case, I got there, had to set up an appointment, and then waited about an hour and a half before they saw me.</p>
<p>The genius determined the same thing I did: the hard drive is dead.</p>
<p>They checked to see if there was any way of getting my data off the now dead hard drive &#8211; they couldn&#8217;t; with the outcome that I&#8217;ve lost all of the data and documents created (more or less) since I bought the computer. There are some items that were uploaded to different places, my <strong>writing samples</strong> are all on my website and an external hard drive, and I have some things in email, but for the most part, I get to start over on all of the fiction writing I&#8217;ve done since I started working in this environment.</p>
<p>The outcome, a bit more than a hundred dollar&#8217;s for a new hard drive and a stand so that air gets all around the laptop and I am back up and running.</p>
<p>What I did notice was that I had to configure the <a title="Apple :: Leopard" href="http://www.apple.com/osx/" target="_blank">OSX 10.5</a> install the Apple Store put on the computer (I do have Leopard and took the disks in case they needed them . . . dumb me) then told it to check for updates. If this had been Microsoft, those updates would&#8217;ve been downloading and installing for about twelve hours. I was done in under an hour.</p>
<p>At this time, I reinstalled <a title="Apple :: iWork" href="http://www.apple.com/iwork/" target="_blank">iWork</a> and <a title="Mozilla :: Firefox" href="http://www.firefox.com/" target="_blank">Firefox</a>, made sure <a title="Apple :: iTunes" href="http://www.apple.com/itunes/" target="_blank">iTunes</a> is up-to-date and am hoping when I sync my <strong>iPhone</strong> and the <strong>iPod Classic</strong> and (maybe) get the paid for music not backed up on <a title="Erin's website" href="http://www.littlekitegirl.com/" target="_blank">Erin</a>&#8216;s computer or the external hard drive.</p>
<p>The outcome, my computer is back to being alive and well. I lost everything. And I am happy.</p>
John Hattaway | smokingpen | Alicia Grey | Clockwork Princess | Cassandra West
<p>
<p><strong>Real Heroes Fly</strong>
]]></content:encoded>
			<wfw:commentRss>http://www.johnhattaway.com/2009/05/the-white-screen-or-what-happens-when-hard-drives-go-to-heaven/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Things that Happened when I didn&#8217;t Update</title>
		<link>http://www.johnhattaway.com/2009/04/things-that-happened-when-i-didnt-update/</link>
		<comments>http://www.johnhattaway.com/2009/04/things-that-happened-when-i-didnt-update/#comments</comments>
		<pubDate>Sat, 04 Apr 2009 06:21:53 +0000</pubDate>
		<dc:creator>smokingpen</dc:creator>
				<category><![CDATA[On Writing]]></category>
		<category><![CDATA[Technology and Gadgets]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.johnhattaway.com/?p=1797</guid>
		<description><![CDATA[This week has been interesting. The lack of updates has been more a result of me working graveyards than anything else. I get home, spend some time with CAMPER and Erin and then I go to bed and sleep for a period of hours before I wake up, spend a little more time with CAMPER [...]]]></description>
			<content:encoded><![CDATA[<p>This week has been interesting. The lack of updates has been more a result of me working graveyards than anything else. I get home, spend some time with CAMPER and <a title="Erin's website" href="http://www.littlekitegirl.com/" target="_blank">Erin</a> and then I go to bed and sleep for a period of hours before I wake up, spend a little more time with CAMPER and Erin (hopefully) before I head off to work. At the moment I am sitting in front of my computer after 1 a.m. because I took over with CAMPER (he&#8217;s asleep and someone has to pay attention to him and his needs) and he is now back to sleep AND I am not tired, though I hope to get another four hours of sleep before sunrise, I am in for the long-haul.</p>
<p>I did apply (or start the application process) for a graduate program. Sent them my resume (which is required) and my writing sample (just a wee bit longer than 20 pages). <a title="Erin's website" href="http://www.littlekitegirl.com/" target="_blank">Erin</a> offered to go over it again, but I decided that we could nitpick until the cows came home and, at least for the moment, it needed to be sent out into the world to live its own life. I am currently beating my head against a required <strong>Personal Statement</strong>. I need to send that over as well, get some mailings together, look up how to get the three different schools I spent parts of my undergraduate career at to send the transcripts over to the new university, and then cross my fingers to get in.</p>
<p>Speaking of fingers, a couple of nights ago, whilst at work, I sliced open the index finger on my left hand. The manager on duty asked if I could just put a bandaid on it. Since it was both long, over a joint, and deep I said, &#8220;No,&#8221; and then went to the <strong>Emergency Room</strong>. It&#8217;s sad to note that that was the easy part, when I got back to work last night I was told I had a bunch of paperwork to fill out and that I had to go to a <strong>compulsory drug screening</strong> at 8 a.m. this morning. Gotta tell you, I am normally in bed or ready for bed and heading (quickly) in that direction by the time I was to be drug screened and that a <strong>salaried member of management</strong> had to take me. The outcome was me staying at work for an extra couple of hours, me finishing ALL of the computer-based learning modules &#8211; including power lifting equipment (which means I will get to use power lifting equipment in the near future) &#8211; and then (smelling of dirty human being) was taken for the drug screening.</p>
<p>All I can really say is, &#8220;Thank god for not having a shy bladder.&#8221;</p>
<p>Anyway, finally made it home. <a title="Erin :: Saddest Day of my Life" href="http://www.littlekitegirl.com/2009/04/03/saddest-day-of-my-life/" target="_blank">Waited with CAMPER until Erin had gotten ready for the day and then slept for about four hours</a>. When I woke up, <a title="Erin's website" href="http://www.littlekitegirl.com/" target="_blank">Erin</a> and I went on a date where we ate at <a title="Bennigans Restaurant and other stuff" href="http://www.bennigans.com/" target="_blank">Bennigans</a>, bought some things for <strong>Easter</strong>, went to the bookstore where books were purchased (though absolutely none for me, which is amazing as I generally use any excuse to buy books) before heading home and ensuring CAMPER was asleep and then I was put to bed, which is where I was until about midnight when I got up, told Erin to get some sleep, and let CAMPER sleep on top of me for about an hour.</p>
<p>Really, I&#8217;ve had some thoughts about things to write. While <strong>working graveyards</strong> and having music piped (pretty) directly into my ears most of the night realized something important:</p>
<blockquote><p><strong>It is against the laws of Islaam for djinni to take on the form of animals</strong>.</p></blockquote>
<p>Not the kind of important (I am sure) you thought it would be. However, along with a new application I am using on the <a title="Apple :: iPhone" href="http://www.apple.com/iphone/" target="_blank">iPhone</a>, <a title="SmartGo" href="http://www.smartgo.com" target="_blank">SmartGo</a> (I am a little amazed at the <strong>iPhone adaptation</strong> when the company does not support <strong>Mac</strong>), I have been trying to connect disparate pieces of a story together. I  know this story is going to be something significant for me AND at the same time I have to have more than character A arrives in town, meets character B, and ends with the opening of object Z. Confusing, but it makes a lot of sense to me. Not really the point other than to say that I&#8217;ve discovered aspects of my story I didn&#8217;t know existed before. And yes, the above is actually very important.</p>
John Hattaway | smokingpen | Alicia Grey | Clockwork Princess | Cassandra West
<p>
<p><strong>Real Heroes Fly</strong>
]]></content:encoded>
			<wfw:commentRss>http://www.johnhattaway.com/2009/04/things-that-happened-when-i-didnt-update/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The Better Part&#8230;</title>
		<link>http://www.johnhattaway.com/2008/08/the-better-part/</link>
		<comments>http://www.johnhattaway.com/2008/08/the-better-part/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 22:08:18 +0000</pubDate>
		<dc:creator>smokingpen</dc:creator>
				<category><![CDATA[Technology and Gadgets]]></category>
		<category><![CDATA[quick post]]></category>

		<guid isPermaLink="false">http://www.johnhattaway.com/?p=965</guid>
		<description><![CDATA[Sometimes when life starts tossing rotten lemons at you, experience dictates that you turn the other cheek and take the better part of valor by not responding to whatever thing you think you should respond to. One of the hallmarks of an immature person is someone who reacts eye-for-eye and tooth-for-tooth. Like responses to injury [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes when life starts tossing rotten lemons at you, experience dictates that you turn the other cheek and take the <em>better part of valor</em> by not responding to whatever thing you think you should respond to. One of the hallmarks of an immature person is someone who reacts <strong>eye-for-eye</strong> and <strong>tooth-for-tooth.</strong> Like responses to injury are an Old Testament, Moses thing. It&#8217;s a theoretically immature people (collectively) unprepared for the responsibility of a higher covenant. Since this is not a religious post, but a post on maturity, the outcome lends itself to flame wars online.</p>
<p>I won&#8217;t point anywhere specifically, but what is interesting to me is that many aspects of the internet are created by individuals who are talented at programming but do not have the emotional capacity to handle criticism, especially competitive criticism heaped on by peers. What makes all of this pertinent is that when you use the internet and you find something you like, chances are it was developed (or at least programmed) by someone who was sub-30, has a lot of talent, and also has very little to know control over emotions and is willing and able to speak up and sabotage other people.</p>
<p>And this is why, on the internet, flame wars are so dangerous. Because you will, more than likely, cause someone to get made who is emotionally immature and who knows more about how the internet works than you. The emotional immature is the actual problem.</p>
<p>John Hattaway | smokingpen | Alicia Grey | Clockwork Princess | Cassandra West</p>
<p><strong>Real Heroes Fly</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johnhattaway.com/2008/08/the-better-part/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cracking the Interweb</title>
		<link>http://www.johnhattaway.com/2008/03/cracking-the-interweb/</link>
		<comments>http://www.johnhattaway.com/2008/03/cracking-the-interweb/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 17:32:43 +0000</pubDate>
		<dc:creator>smokingpen</dc:creator>
				<category><![CDATA[Technology and Gadgets]]></category>
		<category><![CDATA[Alicia Grey]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[BYU]]></category>
		<category><![CDATA[Cassandra West]]></category>
		<category><![CDATA[Clockwork Princess]]></category>
		<category><![CDATA[cracking]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[interweb]]></category>
		<category><![CDATA[John Hattaway]]></category>
		<category><![CDATA[mod]]></category>
		<category><![CDATA[smokingpen]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.johnhattaway.com/?p=837</guid>
		<description><![CDATA[I work on campus at <a href="http://www.byu.edu/" title="Brigham Young University" target="main">BYU</a>. Well, one of my jobs is on campus at <a href="http://www.byu.edu/" title="Brigham Young University" target="main">BYU</a> - I do the other one (and potential other ones) from various locations to include on campus and at home (basically wherever I can find a high-speed internet connection).
]]></description>
			<content:encoded><![CDATA[<p>I work on campus at <a href="http://www.byu.edu/" title="Brigham Young University" target="main">BYU</a>. Well, one of my jobs is on campus at <a href="http://www.byu.edu/" title="Brigham Young University" target="main">BYU</a> &#8211; I do the other one (and potential other ones) from various locations to include on campus and at home (basically wherever I can find a high-speed internet connection).</p>
<p>My job on campus is supposed to be a webdeveloper position. Essentially, I come to work and help in the creation and display of websites. I don&#8217;t mind telling you all that I felt qualified to make changes (I still do), but I didn&#8217;t feel a whole lot when it came to creating pages from scratch. I don&#8217;t see myself as possessing the <i>visually creative</i> gene. Some people do and can create dynamically appealing websites; I, on the other hand, can create functional websites with (what I consider) very little visual appeal. S&#8217;why this site (and others) remain so&#8230; BLAH!!!!</p>
<p>I do like knowing something about CSS though.</p>
<p>I also like the fact that my boss will push different non-design related things my way &#8211; and he is patient in allowing me to do what I can (and am comfortable) do within the group. What I can do: create new pages from old templates and research issues and provide (possible) solutions (often implemented).</p>
<p>One problem that presented its ugly head (last month) was the main site being cracked. Yes, I am tempted to post the site I work for on here (and no it is not the main <a href="http://www.byu.edu/" title="Brigham Young University" target="main">BYU</a> website), but I won&#8217;t. The crack on the site was pretty benign, though a lot disturbing, which inserted a lot (read thousands) of invisible links into the index.html page. What this does is create a positive improvement for the receiving site (<a href="http://www.google.com/" title="Google search engine" target="main">Google</a>, <a href="http://www.msn.com/" title="MSN search engine" target="main">MSN</a>, <a href='http://www.yahoo.com/" title="Yahoo! search engine" target="main">Yahoo</a>, and others), but remains invisible on our site.</p>
<p>Since we are pretty constantly on our site(s) changing, adjusting, moving, upgrading, we found it &#8211; though none of us knew how long it had been there. Since I worked for the hosting provider before coming on board here, I knew some of the backdoor methods of looking things up and went through the process of fixing what I could on this end. At the same time, the other guys removed the excess code. Since the nature of the crack was probably an <i>includes</i> vulnerability, I created an <a href="http://www.apache.org/" title="Apache web" target="main">Apache</a> mod in our <a href="http://www.apache.org/" title="Apache web" target="main">Apache</a> file to stop includes from happening outside of our domain.</p>
<p>For me, the crack was done. Unless there is evidence it is still happening or could still happen, there isn&#8217;t a lot to worry about.</p>
<p>Move forward in time. Yesterday, when one of the coworkers got into the office, the site was down. Specifically, it had gone down around 7:15 a.m. Mountain Time and had stayed down until 8:30 a.m. Mountain Time. At which point the coworker along with our webhost discovered that the <a href="http://www.apache.org/" title="Apache web" target="main">Apache</a> file had its permissions changed to block anyone from reading it. Permissions are shifted and our site is back up and alive.</p>
<p>Enter me. I start to look into the crack. To do this I needed to come up with a hypothesis about what caused the downtime and permissions change. Since I have a little bit of experience with computers and the internet (I am amazing on paper) I knew that the <a href="http://www.apache.org/" title="Apache web" target="main">Apache</a> file was not something a regular joe could get at and manipulate; therefore, I postulated that someone or something internally had to have access to it and lock it up.</p>
<p>Before I could test that, though, I had to test under what conditions (and through what programs) the file would have its permissions set wrong. Once I established the permissions that I needed to replicate I proceeded to launch and run a variety of applications that had access top that particular file. Pretty much, you have to have account Root access to get to the file which means there are (about) five people who have access to it (right now). Well, six.</p>
<p>Anyway, as I stated I started with a hypothesis and proceeded to test against it. The problem I (almost immediately) came up with was that I couldn&#8217;t replicate the problem. Nothing I did would cause the permissions to even hickup let alone change and, as a result, I decided to look into other aspects of the site.</p>
<p>One of the initial changes I made to the administration of the site (upon employment) was logging access by visitors. What this does is create insanely large access logs on the server in the terms of tens of thousands of lines that, when cracked, you have to go through. Knowing when the crack ended allowed me to do a couple of things: first, to look at various web analytics systems the school uses and pays for to see how website traffic was affected by this crack and when that affect took place; and second, moving backward through the log files from when I knew the crack ended (there are error codes that indicate whether a person was successful in connecting to the site or not). This allowed me to establish a) time the site went down (to the second); and b) time site came live. More, I could look at who had connected to the site (and how, from where, and with what) and see what they were doing just before (and trying to do after) the site went down.</p>
<p>Since I knew that the file had been altered at 3:30 p.m. on Friday, and I knew (from having done it) that the site was accessible until 5:00 p.m. on Friday, and the analytics software indicated a lower-than-normal visitor trending over the weekend (possibly due to Easter), but did have visitors with an average time-on-site of five minutes-ish, I could establish when the crack to place and how long it lasted.</p>
<p>At that point, I changed my hypothesis (since I could not change permissions without intentionally accessing the file) and decided that there was a security hole. Since I could see who accessed, where the access took place, and what was accessed I decided to try and search for the <a href="http://www.apache.org/" title="Apache web" target="main">Apache</a> file &#8211; a file that shouldn&#8217;t EVER show up in the log files. I found the file. At that point I copied the string used to access the file into a browser, pre-pending the string with the appropriate domain URL, and brought up a screen (black background, lime green text) that allowed me to not only access but control any file on the server.</p>
<p>This is bad news.</p>
<p>At that point I took the first three octets and searched the logs for them, wanting to see from what IP&#8217;s the user was trying to access the site. It ended up being four different IP addresses. I recorded the IP addresses and the proceeded to search the internet for information on the interface screen that was in front of me. In my head I wondered if the screen was a part of PHP that I&#8217;d never heard of (not out of line since I am not a PHP guru), but didn&#8217;t know whether it was authorized PHP and a part of the PHP5 release we are using or something malicious.</p>
<p>What I came across, rather quickly, was that the script was malicious and often found within TXT files that are then accessed through an includes script within PHP. I then proceeded to search the TXT files on the server to see if anything jumped out at me as the culprit for the includes, and discovered that all TXT files were valid and legitimate files.</p>
<p>I then went to the .php page that the cracker accessed through to see if I could find an includes file and dropped down (intentionally) to line 183 to see what would&#8217;ve failed there once other aspects of the site had become unavailable (again, intentionally done since I&#8217;d broken an aspect of the site to discover that part of the scripting broke at line 183). At that point I noticed identical script to what I&#8217;d found when I was doing my searching for malicious intent. I immediately cut out the script and copied it into the database file used for tracking the crack.</p>
<p>At that point (about the end of my shift) I decided that the site was (more or less) secure and could go home; even though I&#8217;d broken a search function within the software that had been compromised. I knew that I needed to find out when the script had been inserted and I needed to check against earlier log files (February) for access logs; but had already changed the &#8220;edited on&#8221; date of the file.</p>
<p>The last thing I did was to make sure the users IP addresses were blocked from our server (with the intent of running a search against new log file with the first three octets over the coming days/weeks).</p>
<p>So, I left the files broken last night and didn&#8217;t pursue more research until this morning.</p>
<p>This morning I established that the file had been cracked on November 29th in the afternoon and the malicious code (most likely) inserted at that time. My guess is that this was a part of the includes crack I&#8217;d stopped in February (which also, incidentally, stopped the insertion of invisible links) and after establishing a potential insertion date went through the February log files (oldest we have) to search for running of malicious script and known IP strings. Neither came up in February, which allows me to believe that the February crack attempts were definitely caused by running includes scripts in the address bar.</p>
<p>After I finished searching the logs, I proceeded to locate and verify the validity of all .php files that could&#8217;ve had the malicious code inserted. Once I established that all files were clear of the code, and then copied a <i>clean</i> version of the .php file (in question) into the cracked directory of the server, restoring search capabilities; I could then focus my attention on known vulnerabilities and upgrades to the software we are using.</p>
<p>With all of that accomplished and a new version of the software to install on all sites using it, as well as needing to go into all of the databases and assure that we have a universal administrative username and password for our team, I believe that this crack attempt has been (for the moment) thwarted. This does not mean that I believe our site is universally crack proof and need to verify the inclusion of .ini files and <a href="http://www.apache.org/" title="Apache web" target="main">Apache</a> mods into all of the (potentially) vulnerable folders, but for the moment I believe we have successfully removed this one threat from our pool of potential crackers.</p>
<p>Truth told, even though the process was very much me and a computer screen, and felt a lot like a 90&#8242;s movie where a cracker is actively being thwarted by a geek at a 24-hour manned terminal (knowing that most internet security is NOT manned actively), the outcome and process was boring to watch and probably equally boring to read about &#8211; even if I do feel rather proud of the discovery and how the crack was able to be stopped, thwarted, and the cracker blocked.</p>
<p>John Hattaway | smokingpen | Alicia Grey | Clockwork Princess | Cassandra West</p>
<p><b>Real Heroes Fly</b></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johnhattaway.com/2008/03/cracking-the-interweb/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
