X040702A: Blogger FTP Corruption

Status	Date	Description



	2004-08-27	Clean this up enough to be able to report back to Blogger.com about how it was not resolved.
	2004-08-27	Bring this one current based on the restoration process as it has proceeded today.
	2004-08-27	I like the structure of later incident reports with regard to actions, lessons learned, etc. Recast this one that way.
done 2004-08-14	2004-08-03	The what's next and the what-to-expect as we recover notices need to be reflected in the index.htm at /wingnut or in some other way, so that visits to the wingnut page can know what the current experiment is.
done 2004-08-13	2004-08-03	Slam-down the 2004/07/why-learn-assembly-language.asp page too, because it is linked from my user-profile page on Blogger
done 2004-08-14	2004-07-31	Post a slam-down for the 2004_06_27_clu-chive.asp page. Usually it goes on top of the last good version, but for now, we put it in place of the version that only existed in a corrupted state. [dh: Just saved B040801B.HTM right there, then changed it to an Include Page of that.]
done	2004-07-31	Clean the quarantined material off of the site image and off of the site itself.
done	2004-07-31	Back down the 2004_06_27_clu-chive.asp to the previous version on the site image and share back to the development folder for Blunderdome/clueless/. update: No previous version. So it is deleted from here to be replaced by the first instance of an archive-page slam-down.
done	2004-07-31	Quarantine the original corrupted binaries: X040702D.bin is the post, why-learn-assembly-language.asp, X040702E.bin is default.asp, and X040702F.bin is clu-atom.xml. The 2004_06_27_clu-chive.asp archive page is X040702G.bin.
	2004-07-31	The description of how to produce a manual feed entry should be moved off to another place and then referenced there.
done	2004-07-26	Synchronize the version situation on X040702B and tidy up the description a little.
	2004-07-24	The use of an ASP page to solve the XML encoding and Web host content type problem is also a way to screen for a corrupted feed and raise an alarm. That's an interesting idea!
done 2004-07-24	2004-07-23	Reissue the notice so that it refers to the stable feed file that constitutes the demonstration of validity.
done 2004-07-24	2004-07-23	Have this feed demonstrate its validity with a stable customization of wing-atom.xml, so that the validation is not confused by later invalidating changes at the time the button is clicked. [dh:2004-07-24 This only holds up if the copy has the same validation result. I now have situations where it doesn't work like that.]
	2004-07-23	Include information about validators for atom feeds.
	2004-07-23	In any discussion about manually-produced feeds, find out what the <id> elements really are, and especially with the use in the top level versus in the individual entries.
done 2004-07-23	2004-07-22	Make a page that will be the permanent identification for my feed entry announcing the lockdown. Another log page may cover more about this. But get the entry in a permaplace that describes what it is and has the correct identification.
done	2004-07-22	Move over items from the X000000, C000000, and BlunderDome (B040701A) that need to be handled as part of this forensic work.
done 2004-08-14	2004-07-21	Add a feed item on what will be seen next in the feed when it is operating, what may happen in an incident, and what they will see when an incident response is underway: [dh:2004-08-14 Wingnut, Clueless, Lair, Peano]
done 2004-07-30	2004-07-21	Add a feed item on what is being done next, in terms of steps I am taking
done 2004-07-24	2004-07-21	Correct the feed from the other three blogs so they match up: orcmid, clueless, and pn
done 2004-07-23	2004-07-21	Verify it with the on-line validator
done 2004-07-23	2004-07-21	Create a corrected feed for the Wingnut lockdown announcement
done 2004-07-23	2004-07-21	Create a page to hold the URL for the corrected feed entry, with the objections, and &#160 explanation. Tie it to the forensic work and the incident-response procedures to be defined
done 2004-07-23	2004-07-21	Rerun the Wingnut Atom Feed through the on-line validator
done	2004-07-15	Create this page with the Lab Notebook style
	2004-07-09	Include the error report and the response from tech support as part of the incident analysis
	2004-07-09	In the detection of corruption arrangement, show how to split out the corrupt or defective page and roll back the one here to provide the necessary restoration fork. Once that is done, the rest can be handled. Illustrate with `2004_06_27_clu-chive.asp` being backed down.
done 2004-07-31	2004-07-09	In the description of the FTP corruption, include default.bad.bin, clu-atom.bad.bin, and also split out 2004_06_27_cluchive.asp and the posted page in 2004/07 (not brought to compagno developer yet).
done 2004-07-15	2004-07-09	Create lab note for the forensic analysis of the Blogger FTP corruption, and the steps that occurred. (See 2004-07-02 also) [dh:2004-07-31 This is done in incident report X040702.]
done 2004-07-15	2004-07-02	Put up a lab note on the problem with the damaged FTP pages [dh:2004-07-23: done with an incident page]