<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<id>tag:old.nabble.com,2006:forum-419</id>
	<title>Nabble - Security - Forensics</title>
	<updated>2008-11-11T07:48:14Z</updated>
	<link rel="self" type="application/atom+xml" href="http://old.nabble.com/Security---Forensics-f419.xml" />
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Security---Forensics-f419.html" />
	<subtitle type="html">Detailed discussions of computer security forensics.</subtitle>
	
<entry>
	<id>tag:old.nabble.com,2006:post-20442663</id>
	<title>On-Demand Penetration Testing Webcasts with Ed Skoudis of SANS</title>
	<published>2008-11-11T07:48:14Z</published>
	<updated>2008-11-11T07:48:14Z</updated>
	<author>
		<name>Norwich University</name>
	</author>
	<content type="html">As a security pro, it's important to periodically stop, take a break, and refuel your brain. Once per month, Core Security Technologies does the same thing and invites industry thought leaders to share their insights through educational webcasts offering security testing tips, tricks and strategies. 
&lt;br&gt;&lt;br&gt;We'd like to share one of our favorite webcast series with you: &amp;quot;Penetration Testing Ninjitsu&amp;quot; with Ed Skoudis of SANS and InGuardians.
&lt;br&gt;&lt;br&gt;&amp;gt; Click here to access this on-demand, three-part webcast series:
&lt;br&gt;&lt;a href=&quot;http://www.coresecurity.com/Form/generic/campaign/secfocus&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.coresecurity.com/Form/generic/campaign/secfocus&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;--------------------------------------------------------------------
&lt;br&gt;About &amp;quot;Penetration Testing Ninjitsu Parts I-III&amp;quot;
&lt;br&gt;--------------------------------------------------------------------
&lt;br&gt;These in-depth, technical presentations by Ed Skoudis look at the art and science of using penetration testing to gain visibility into your organization's security posture.
&lt;br&gt;&lt;br&gt;-- Part I: A brief introduction to the value of penetration testing + an overview of pen testing techniques using the Windows command shell.
&lt;br&gt;&lt;br&gt;-- Part II: An introduction to techniques for performing the functions of Netcat - such as moving files, scanning ports and creating backdoors - without using Netcat.
&lt;br&gt;&lt;br&gt;-- Part III: This installment explores what can happen after the initial vulnerability is compromised and a threat becomes truly invasive - and how to proactively assess your systems against such attacks.
&lt;br&gt;&lt;br&gt;&amp;gt; Click here to access the &amp;quot;Penetration Testing Ninjitsu&amp;quot; series: 
&lt;br&gt;&lt;a href=&quot;http://www.coresecurity.com/Form/generic/campaign/secfocus&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.coresecurity.com/Form/generic/campaign/secfocus&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Core Security provides comprehensive security testing software solutions based on independent, trusted vulnerability research and leading-edge threat expertise. Unlike many vendor webcasts, these are focused on educating the security community rather than selling a specific product.
&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/On-Demand-Penetration-Testing-Webcasts-with-Ed-Skoudis-of-SANS-tp20442663p20442663.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-18309034</id>
	<title>CfP: Int. Workshop on Information Credibility on the Web (WICOW2008) at CIKM2008</title>
	<published>2008-07-06T19:22:34Z</published>
	<updated>2008-07-06T19:22:34Z</updated>
	<author>
		<name>Adammo</name>
	</author>
	<content type="html">(+apologies for cross-posting+)
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;****CALL FOR PAPERS****
&lt;br&gt;&lt;br&gt;2nd Workshop on Information Credibility on the Web
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (WICOW 2008)
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; in conjunction with 17th ACM CIKM 2008 
&lt;br&gt;&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; October 30, 2008, Napa Valley, California
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://www.dl.kuis.kyoto-u.ac.jp/wicow2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.dl.kuis.kyoto-u.ac.jp/wicow2&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;* AIM OF THE WORKSHOP *
&lt;br&gt;&lt;br&gt;The aim of this workshop is to provide a forum for discussion about issues
&lt;br&gt;related to information credibility and its evaluation.
&lt;br&gt;As computers and computer networks become more sophisticated, a huge
&lt;br&gt;amount of information, such as that found in Web documents, has been
&lt;br&gt;accumulated and circulated. Such information gives people a framework for organizing their daily
&lt;br&gt;lives. A well-functioning society needs technology that can be used to
&lt;br&gt;manage this wealth of information and, in particular, investigate its credibility.
&lt;br&gt;This technology would be able to handle a wide range of tasks:
&lt;br&gt;extracting credible information related to a given topic,
&lt;br&gt;organizing this information, detecting its provenance, clarifying
&lt;br&gt;background, facts, and various related opinions and the distribution of
&lt;br&gt;them, and so on. Especially, as the Web is becoming a major source of
&lt;br&gt;information nowadays, it is necessary to provide efficient and reliable
&lt;br&gt;methods for evaluation of Web content's trustworthiness. 
&lt;br&gt;&lt;br&gt;* TOPICS *
&lt;br&gt;&lt;br&gt;We invite submissions on any aspects of information credibility on the
&lt;br&gt;Web. Topics include, but are not limited to: 
&lt;br&gt;&lt;br&gt;- Information credibility evaluation and its applications
&lt;br&gt;- Content analysis for credibility evaluation
&lt;br&gt;- Sentiment analysis of content
&lt;br&gt;- Credibility of Web search results
&lt;br&gt;- Search models and applications for trustworthy content
&lt;br&gt;- Conflicting opinion detection and analysis
&lt;br&gt;- Credibility evaluation of user-generated content (e.g., Wikipedia)
&lt;br&gt;- Information credibility evaluation in social networks
&lt;br&gt;- Analysis of information dissemination
&lt;br&gt;- Estimation of author and publishing venue reputation
&lt;br&gt;- Spatial and temporal aspects in information credibility
&lt;br&gt;- Estimation of information age, provenance and validity
&lt;br&gt;- Sociological and psychological aspects of information credibility
&lt;br&gt;- Users study for information credibility
&lt;br&gt;- Risk assessment of information credibility
&lt;br&gt;- Multimedia content credibility
&lt;br&gt;- Persuasive technologies
&lt;br&gt;- Information credibility in online advertising and Internet monetization
&lt;br&gt;- Object identification on the Web
&lt;br&gt;&lt;br&gt;* IMPORTANT DATES *
&lt;br&gt;&lt;br&gt;- July 20, 2008 - Paper submission
&lt;br&gt;- August 10, 2008 - Notification of acceptance
&lt;br&gt;- August 15, 2008 - Camera-ready paper submission (hard deadline for publication in proceedings)
&lt;br&gt;- October 30, 2008 - Workshop
&lt;br&gt;&lt;br&gt;* SUBMISSION *
&lt;br&gt;&lt;br&gt;Submissions should be sent in English in PDF format via the submission website. Papers should adhere 
&lt;br&gt;to ACM formatting guidelines and should have length of 6 to 8 pages.
&lt;br&gt;They must be original and have not been submitted for publication elsewhere. We
&lt;br&gt;encourage also position papers outlining interesting research directions. 
&lt;br&gt;&lt;br&gt;The accepted papers are going to appear in CIKM Workshops Proceedings published by ACM either as full 
&lt;br&gt;(up to 8 pages) or short papers (up to 4 pages) depending on the review
&lt;br&gt;results. At least one author of each accepted submission should register
&lt;br&gt;by the end of the early registration period in order for the paper to be
&lt;br&gt;included in the proceedings.
&lt;br&gt;&lt;br&gt;* ORGANIZATION *
&lt;br&gt;&lt;br&gt;General Chairs: 
&lt;br&gt;&lt;br&gt;- Katsumi Tanaka &amp;nbsp;Kyoto University, Japan
&lt;br&gt;- Takashi Matsuyama &amp;nbsp;Kyoto University, Japan
&lt;br&gt;- Ee-Peng Lim &amp;nbsp;Singapore Management University, Singapore
&lt;br&gt;&lt;br&gt;PC Chair: 
&lt;br&gt;&lt;br&gt;- Adam Jatowt &amp;nbsp;Kyoto University, Japan
&lt;br&gt;&lt;br&gt;Program Committee: 
&lt;br&gt;&lt;br&gt;- see website
&lt;br&gt;&lt;br&gt;* CONTACT *
&lt;br&gt;&lt;br&gt;Adam Jatowt
&lt;br&gt;email: adam [at] dl [dot] kuis [dot] kyoto-u [dot] ac [dot] jp
&lt;br&gt;phone/fax: +81-75-231-4282</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/CfP%3A-Int.-Workshop-on-Information-Credibility-on-the-Web-%28WICOW2008%29-at-CIKM2008-tp18309034p18309034.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-17330352</id>
	<title>CCE training opportunities in June...</title>
	<published>2008-05-18T11:11:01Z</published>
	<updated>2008-05-18T11:11:01Z</updated>
	<author>
		<name>Gary Kessler-2</name>
	</author>
	<content type="html">Hi all!
&lt;br&gt;&lt;br&gt;Champlain College, in partnership with the International Society of Forensic Computer Examiners (ISFCE), is going to be offering two Certified Computer Examiner (CCE) Bootcamp courses in June:
&lt;br&gt;&lt;br&gt;&amp;nbsp; o &amp;nbsp;June 9-13 in Burlington, Vermont
&lt;br&gt;&amp;nbsp; o &amp;nbsp;June 23-27 at Bunker Hill Community College in Boston
&lt;br&gt;&lt;br&gt;More information can be found at &lt;a href=&quot;http://c3di.champlain.edu/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://c3di.champlain.edu/&lt;/a&gt;&amp;nbsp;and clicking on Training Opportunities.
&lt;br&gt;&lt;br&gt;Do let me know if you have any questions! Feel free to share with any other interested parties.
&lt;br&gt;&lt;br&gt;Thanks!
&lt;br&gt;/gary kessler
&lt;br&gt;&lt;br&gt;==========================================================================
&lt;br&gt;Gary C. Kessler &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=17330352&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;gary.kessler@...&lt;/a&gt;
&lt;br&gt;Dir., Center for Digital Investigation &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Project Director
&lt;br&gt;Associate Professor &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Information Security
&lt;br&gt;Computer &amp; Digital Forensics program &amp;nbsp; &amp;nbsp; &amp;nbsp; Vt. Information Technology Ctr.
&lt;br&gt;&lt;br&gt;Champlain College &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Office: +1 802-865-6460
&lt;br&gt;West Hall, Room 107 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Fax: +1 802-865-6446
&lt;br&gt;163 South Willard Street &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Cell: +1 802-238-8913
&lt;br&gt;Burlington, VT 05401 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Skype: gary.c.kessler
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://c3di.champlain.edu&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://c3di.champlain.edu&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=17330352&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;kumquat@...&lt;/a&gt;
&lt;br&gt;&lt;a href=&quot;http://digitalforensics.champlain.edu&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://digitalforensics.champlain.edu&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://www.garykessler.net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.garykessler.net&lt;/a&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;PGP Public Keys: &lt;a href=&quot;http://www.garykessler.net/kumquat_pubkey.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.garykessler.net/kumquat_pubkey.html&lt;/a&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://digitalforensics.champlain.edu/gck/GaryKessler.asc&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://digitalforensics.champlain.edu/gck/GaryKessler.asc&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/CCE-training-opportunities-in-June...-tp17330352p17330352.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-17330464</id>
	<title>CfP hack.lu 2008</title>
	<published>2008-05-15T23:57:54Z</published>
	<updated>2008-05-15T23:57:54Z</updated>
	<author>
		<name>info-1366</name>
	</author>
	<content type="html">Call for Papers Hack.lu 2008
&lt;br&gt;&lt;br&gt;The purpose of the hack.lu convention is to give an open and free 
&lt;br&gt;playground where people can discuss the implication of new technologies 
&lt;br&gt;in society.
&lt;br&gt;&lt;br&gt;hack.lu is a balanced mix convention where technical and non-technical 
&lt;br&gt;people can meet each others and share freely all kind of information.
&lt;br&gt;&lt;br&gt;The convention will be held in the Grand-Duchy of Luxembourg in October 
&lt;br&gt;2008 (22-24.10.2008).
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Scope
&lt;br&gt;&lt;br&gt;======
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Topics of interest include, but are not limited to :
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;* Software Engineering and Security
&lt;br&gt;* Honeypots/Honeynets
&lt;br&gt;* Spyware, Phishing and Botnets (Distributed attacks)
&lt;br&gt;* Newly discovered vulnerabilities in software and hardware
&lt;br&gt;* Electronic/Digital Privacy
&lt;br&gt;* Wireless Network and Security
&lt;br&gt;* Attacks on Information Systems and/or Digital Information Storage
&lt;br&gt;* Electronic Voting
&lt;br&gt;* Free Software and Security
&lt;br&gt;* Assessment of Computer, Electronic Devices and Information Systems
&lt;br&gt;* Standards for Information Security
&lt;br&gt;* Legal and Social Aspect of Information Security
&lt;br&gt;* Software Engineering and Security
&lt;br&gt;* Security in Information Retrieval
&lt;br&gt;* Network security
&lt;br&gt;* Forensics and Anti-Forensics
&lt;br&gt;* Mobile communications security and vulnerabilities
&lt;br&gt;&lt;br&gt;&lt;br&gt;Deadlines
&lt;br&gt;&lt;br&gt;=========
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;The following dates are important if you want to participate in the CfP
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Abstract submission : no later than 1 July 2008
&lt;br&gt;Full paper submission : no later than 1st August 2008
&lt;br&gt;Notification date : around end of August
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Submission guideline (for standard paper track)
&lt;br&gt;&lt;br&gt;====================
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Authors should submit a paper in English up to 5.000 words, using a 
&lt;br&gt;non-proprietary and open electronic format.
&lt;br&gt;&lt;br&gt;The program committee will review all papers and the author of each 
&lt;br&gt;paper will be notified of the result, by electronic means.
&lt;br&gt;&lt;br&gt;Abstract is up to 400 words. Submissions must be sent via the 
&lt;br&gt;&lt;a href=&quot;http://www.hack.lu/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.hack.lu/&lt;/a&gt;&amp;nbsp;website.
&lt;br&gt;&lt;br&gt;&lt;br&gt;Submissions should also include the following:
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;1. Presenter, and geographical location (country of origin/passport)and 
&lt;br&gt;contact info.
&lt;br&gt;2. Employer and/or affiliations.
&lt;br&gt;3. Brief biography, list of publications or papers.
&lt;br&gt;4. Any significant presentation and/or educational experience/background.
&lt;br&gt;5. Reason why this material is innovative or significant or an important 
&lt;br&gt;tutorial.
&lt;br&gt;6. Optionally, any samples of prepared material or outlines ready.
&lt;br&gt;7. Information about if yes or no the submission has already been 
&lt;br&gt;presented and where.
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;The information will be used only for the sole purpose of the hack.lu 
&lt;br&gt;convention including the information on the public website.
&lt;br&gt;&lt;br&gt;If you want to remain anonymous, you have the right to use a nickname.
&lt;br&gt;&lt;br&gt;&lt;br&gt;(Accepted) Speakers' Privileges
&lt;br&gt;&lt;br&gt;====================
&lt;br&gt;&lt;br&gt;&lt;br&gt;* Accommodation will be provided (3 nights)
&lt;br&gt;* Travel expenses will be covered
&lt;br&gt;* Conference speakers night
&lt;br&gt;&lt;br&gt;&lt;br&gt;Publication and rights
&lt;br&gt;&lt;br&gt;======================
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Authors keep the full rights on their publication/papers but give an 
&lt;br&gt;unrestricted right to redistribute their papers for the hack.lu convention
&lt;br&gt;and its related electronic/paper publication.
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Sponsoring
&lt;br&gt;&lt;br&gt;==========
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;If you want to support the initiative and gain visibility by sponsoring, 
&lt;br&gt;please contact us by writing an e-mail to info(AT)hack.lu
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Web site
&lt;br&gt;&lt;br&gt;======
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.hack.lu/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.hack.lu/&lt;/a&gt;&lt;br&gt;&lt;br&gt;Barcamp and interactive session
&lt;br&gt;&lt;br&gt;====================
&lt;br&gt;&lt;br&gt;During the conference, there is a continuous interactive session. You 
&lt;br&gt;are also very welcome to participate to submit small ideas, presentation 
&lt;br&gt;or poster. The review process is simplified and open to anyone willing 
&lt;br&gt;to take an active role during the conference. You can submit your 
&lt;br&gt;proposal using the same web interface for the barcamp but you don't 
&lt;br&gt;require to submit a full paper.
&lt;br&gt;&lt;br&gt;Submissions are done via the hack.lu website (&lt;a href=&quot;http://www.hack.lu/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.hack.lu/&lt;/a&gt;)
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;The hack.lu conference is organized by the ASBL CSRRT-LU (Computer 
&lt;br&gt;Security Research and Response Team Luxembourg)
&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/CfP-hack.lu-2008-tp17330464p17330464.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-17230951</id>
	<title>Re: Verify alternation and tracing the source of digital photos</title>
	<published>2008-05-13T12:37:55Z</published>
	<updated>2008-05-13T12:37:55Z</updated>
	<author>
		<name>mark_thurber</name>
	</author>
	<content type="html">Unless you have a MD5 or SHA value of the original it is a pretty daunting task. I came across this article from wired while doing a research paper. Here is the link. &lt;a href=&quot;http://www.wired.com/gadgets/digitalcameras/news/2007/03/72883&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.wired.com/gadgets/digitalcameras/news/2007/03/72883&lt;/a&gt;&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-Verify-alternation-and-tracing-the-source-of-digital-photos-tp17230951p17230951.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-17082749</id>
	<title>[Fwd:  NZ cops get 'COFEE' to capture PC evidence]</title>
	<published>2008-05-03T08:32:32Z</published>
	<updated>2008-05-03T08:32:32Z</updated>
	<author>
		<name>atrav</name>
	</author>
	<content type="html">Interesting news from New Zeland, I wonder how to get a copy. ;o)
&lt;br&gt;-Aron-
&lt;br&gt;&lt;br&gt;-------- Original Message --------
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.stuff.co.nz/4507443a28.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.stuff.co.nz/4507443a28.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;NZ cops get 'COFEE' to capture PC evidence
&lt;br&gt;NZPA | Saturday, 03 May 2008
&lt;br&gt;&lt;br&gt;New Zealand police have been given a small plug-in device that
&lt;br&gt;investigators can use to quickly extract forensic data from computers
&lt;br&gt;that may have been used in crimes.
&lt;br&gt;&lt;br&gt;&lt;br&gt;The COFEE, which stands for Computer Online Forensic Evidence
&lt;br&gt;Extractor, is a prototype of a USB &amp;quot;thumb drive&amp;quot; that Microsoft has
&lt;br&gt;quietly distributed to a few law-enforcement agencies around the
&lt;br&gt;world.
&lt;br&gt;&lt;br&gt;A spokesman at police national headquarters said today: &amp;quot;Police have
&lt;br&gt;been issued with the COFEE tool by Microsoft and the E-Crime Lab's
&lt;br&gt;digital forensic analysts have been trained in the use of it&amp;quot;.
&lt;br&gt;&lt;br&gt;New Zealand police had an excellent relationship with the software
&lt;br&gt;company, which had provided specialist training to digital forensic
&lt;br&gt;analysts and investigators, he said.
&lt;br&gt;&lt;br&gt;Overseas, experts in computer forensics have said the preconfigured,
&lt;br&gt;automated tool can carry out in 20 minutes, with the click of one
&lt;br&gt;button, 150 complex commands that previously required a manual process
&lt;br&gt;taking three to four hours.
&lt;br&gt;&lt;br&gt;Microsoft general counsel Brad Smith confirmed the device dramatically
&lt;br&gt;cut the time required to gather the digital evidence which is becoming
&lt;br&gt;more important in real-world crime, as well as cybercrime.
&lt;br&gt;&lt;br&gt;It can decrypt passwords and analyse a computer's internet activity,
&lt;br&gt;as well as data stored in the computer.
&lt;br&gt;&lt;br&gt;The tiny device also eliminates the need to seize a computer itself,
&lt;br&gt;which typically involves disconnecting from a network, turning off the
&lt;br&gt;power and potentially losing data. Instead, the investigator can scan
&lt;br&gt;for evidence on site.
&lt;br&gt;&lt;br&gt;It was provided for free, Mr Smith told the Seattle Times newspaper,
&lt;br&gt;because the software company was working to help ensure that the
&lt;br&gt;internet stayed safe.
&lt;br&gt;&lt;br&gt;&amp;quot;It's basically a thumb drive that is like a Swiss army knife for law
&lt;br&gt;enforcement officials that are investigating computer crimes.
&lt;br&gt;&lt;br&gt;&amp;quot;If you're a law enforcement official and let's say you have access to
&lt;br&gt;a computer that might be used, for example, by a child predator, a lot
&lt;br&gt;of times they have information on their hard disk that's encrypted,
&lt;br&gt;and you've got that information off in order to have a successful
&lt;br&gt;investigation and prosecution.
&lt;br&gt;&lt;br&gt;&amp;quot;In the past, people would have to literally unplug the computer, they
&lt;br&gt;would lose whatever was in RAM. They'd have to transport it somewhere
&lt;br&gt;else, and it would take at least four hours, often more to get at the
&lt;br&gt;heart of the information.&amp;quot;
&lt;br&gt;&lt;br&gt;COFEE was developed by Anthony Fung, a former Hong Kong police officer
&lt;br&gt;working as a senior investigator on Microsoft's internet safety team.
&lt;br&gt;&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-Fwd%3A--NZ-cops-get-%27COFEE%27-to-capture-PC-evidence--tp17082749p17082749.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-15279353</id>
	<title>Verify alternation and tracing the source of digital photos</title>
	<published>2008-02-01T02:00:40Z</published>
	<updated>2008-02-01T02:00:40Z</updated>
	<author>
		<name>Frankie Li-2</name>
	</author>
	<content type="html">Hi List,
&lt;br&gt;&lt;br&gt;A case of digital photos circulated on the Internet formus, I need your 
&lt;br&gt;helps in find out answers for 2 answers:
&lt;br&gt;&lt;br&gt;1. &amp;nbsp; &amp;nbsp;Are there any tools that we could used to verify if a digital photo 
&lt;br&gt;has been altered?
&lt;br&gt;&lt;br&gt;2. &amp;nbsp; &amp;nbsp;As those photos are posted on various formus, how to trace back the 
&lt;br&gt;original source of the photos? &amp;nbsp;I think even though we could obtain all logs 
&lt;br&gt;(for timeline analysis) from the forums that those pictures are found, but 
&lt;br&gt;we could not rule out that some more sources are missed.
&lt;br&gt;&lt;br&gt;Thanks for answering in advance.
&lt;br&gt;&lt;br&gt;&lt;br&gt;Frankie 
&lt;br&gt;&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Verify-alternation-and-tracing-the-source-of-digital-photos-tp15279353p15279353.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-14164444</id>
	<title>Advice on transferring forensic image</title>
	<published>2007-12-04T04:35:16Z</published>
	<updated>2007-12-04T04:35:16Z</updated>
	<author>
		<name>Stefan Kelm</name>
	</author>
	<content type="html">Folks,
&lt;br&gt;&lt;br&gt;one of my cases has been going on for almost half a year
&lt;br&gt;now. Unfortunately, I now do have the need to transfer
&lt;br&gt;the forensic dd image to another target disk which will
&lt;br&gt;then become the case disk.
&lt;br&gt;&lt;br&gt;Is there anything other than the usual stuff (securely
&lt;br&gt;erase the 'new' disk, create checksums before copying,
&lt;br&gt;transfer the image using dcfldd, create checksums after
&lt;br&gt;copying, securely erase the 'old' disk, document the whole
&lt;br&gt;process) which needs to be done?
&lt;br&gt;&lt;br&gt;Am I missing anything important here?
&lt;br&gt;&lt;br&gt;Cheers,
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Stefan.
&lt;br&gt;&lt;br&gt;--------------------------------------------------------
&lt;br&gt;T.I.S.P. &amp;nbsp;- &amp;nbsp;Lassen Sie Ihre Qualifikation zertifizieren
&lt;br&gt;vom 25.-29.02.2008 - &lt;a href=&quot;http://www.secorvo.de/college/tisp/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.secorvo.de/college/tisp/&lt;/a&gt;&lt;br&gt;--------------------------------------------------------
&lt;br&gt;Stefan Kelm
&lt;br&gt;Security Consultant
&lt;br&gt;&lt;br&gt;Secorvo Security Consulting GmbH
&lt;br&gt;Ettlinger Strasse 12-14, D-76137 Karlsruhe
&lt;br&gt;Tel. +49 721 255171-304, Fax +49 721 255171-100
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=14164444&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;stefan.kelm@...&lt;/a&gt;, &lt;a href=&quot;http://www.secorvo.de/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.secorvo.de/&lt;/a&gt;&lt;br&gt;PGP: 87AE E858 CCBC C3A2 E633 D139 B0D9 212B
&lt;br&gt;&lt;br&gt;Mannheim HRB 108319, Geschaeftsfuehrer: Dirk Fox
&lt;br&gt;&lt;br&gt;-----------------------------------------------------------------
&lt;br&gt;Uncover stealthy Trojans and malware in corporate web traffic
&lt;br&gt;Anti-virus and URL filtering solutions provide only a limited solution to evasive crimeware.
&lt;br&gt;Qualify for a free audit for enterprises
&lt;br&gt;www.finjan.com/RUSafe
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Advice-on-transferring-forensic-image-tp14164444p14164444.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13959326</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-26T13:17:27Z</published>
	<updated>2007-11-26T13:17:27Z</updated>
	<author>
		<name>David Kovar-2</name>
	</author>
	<content type="html">Greetings,
&lt;br&gt;&lt;br&gt;First off, use a hardware write blocker if you really want to be &amp;nbsp;
&lt;br&gt;certain nothing is going back to the drive.
&lt;br&gt;&lt;br&gt;Then, you can cover all the bases quite neatly by making multiple &amp;nbsp;
&lt;br&gt;forensic copies of the evidence disk. Allow one to mount &amp;quot;normally&amp;quot;. &amp;nbsp;
&lt;br&gt;Mount one with a write blocker. Mount one with a different kernel. &amp;nbsp;
&lt;br&gt;Mount one .... Etc. Compare and contrast ...
&lt;br&gt;&lt;br&gt;-David
&lt;br&gt;&lt;br&gt;On Nov 24, 2007, at 9:49 PM, Krassimir Tzvetanov wrote:
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Well this is a little one sided.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; When you are preserving a hard disk you want a snapshot in the moment
&lt;br&gt;&amp;gt; it was seized. This would mean that you should not do any alteration
&lt;br&gt;&amp;gt; after that point and I'll ask you to consider two cases that will show
&lt;br&gt;&amp;gt; you where I come from.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; 1. The journal replay may overwrite some chunks of data you may want
&lt;br&gt;&amp;gt; to have linked the way they were. I.e. somebody did &amp;quot;rm -rf /&amp;quot; the
&lt;br&gt;&amp;gt; moment the agents were serving a no know warrant (and if they turned
&lt;br&gt;&amp;gt; off the machine the files will be still linked).
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; 2. The kernel of the system you are running may have a bug that may
&lt;br&gt;&amp;gt; result in a different behavior than the system being investigated. (or
&lt;br&gt;&amp;gt; vice versa the system may had &amp;quot;special patches&amp;quot; applied that might
&lt;br&gt;&amp;gt; cause your data replay to corrupt data.
&lt;br&gt;&amp;gt; Even further think about a patch that ignores certain records of the
&lt;br&gt;&amp;gt; journal file and those records when applied by a &amp;quot;unpatched kernel&amp;quot;
&lt;br&gt;&amp;gt; unlink certain files (or overwrite them with random data).
&lt;br&gt;&amp;gt; You should also do separate analysis on the journal itself to
&lt;br&gt;&amp;gt; determine what contents it contains.
&lt;br&gt;&amp;gt; Having said all that I do not reject the ability to present as a
&lt;br&gt;&amp;gt; separate evidence replayed journal (*and note you did that*) to the
&lt;br&gt;&amp;gt; investigators/court.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Regards,
&lt;br&gt;&amp;gt; Krassi
&lt;/div&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13959326.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13959592</id>
	<title>RE: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-26T13:13:03Z</published>
	<updated>2007-11-26T13:13:03Z</updated>
	<author>
		<name>Robinson, Sonja-2</name>
	</author>
	<content type="html">Tableau makes good write blockers for many different types of
&lt;br&gt;connections. 
&lt;br&gt;&lt;br&gt;-----Original Message-----
&lt;br&gt;From: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13959592&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;listbounce@...&lt;/a&gt; [mailto:&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13959592&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;listbounce@...&lt;/a&gt;]
&lt;br&gt;On Behalf Of Matthew Pepe
&lt;br&gt;Sent: Saturday, November 24, 2007 8:24 PM
&lt;br&gt;To: Terry Roebuck
&lt;br&gt;Cc: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13959592&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;forensics@...&lt;/a&gt;
&lt;br&gt;Subject: Re: Converting an external hard drive enclosure into a write
&lt;br&gt;blocker?
&lt;br&gt;&lt;br&gt;The easiest thing to do is to use a bridge whose firmware can be
&lt;br&gt;modified to take a different action upon the issuance of a write (or
&lt;br&gt;write-related) command. &amp;nbsp;Operating systems will react differently
&lt;br&gt;depending upon whether the device returns an error code, success code,
&lt;br&gt;or remains quiet. &amp;nbsp;The bottom line is that you need to intercept
&lt;br&gt;packetized commands - write enable is not based off of a pin pulled high
&lt;br&gt;or low. For more information, check out the ATA/ATAPI5 documents from
&lt;br&gt;the T13 working group.
&lt;br&gt;&lt;br&gt;- Matt
&lt;br&gt;&lt;br&gt;&lt;br&gt;On Nov 20, 2007, at 11:11 AM, Terry Roebuck wrote:
&lt;br&gt;&lt;br&gt;&amp;gt; A*nix mount with DD would be my option of choice, but for windows, I 
&lt;br&gt;&amp;gt; hesitatingly ask could you not modify an IDE cable to make any 
&lt;br&gt;&amp;gt; connected drive 'read-only' (might require a resistor - not sure if 
&lt;br&gt;&amp;gt; you can just clip a wire? - maybe some one with better EE skills could
&lt;br&gt;&lt;br&gt;&amp;gt; answer that?)
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13959592.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13958917</id>
	<title>Call for Papers -- Journal of Digital Forensics Practice</title>
	<published>2007-11-26T07:56:03Z</published>
	<updated>2007-11-26T07:56:03Z</updated>
	<author>
		<name>Gary Kessler-2</name>
	</author>
	<content type="html">Hi all!
&lt;br&gt;&lt;br&gt;My apologies for any duplicate posts!
&lt;br&gt;&lt;br&gt;&lt;br&gt;Attached is a Call for Papers for the next issue of the Journal of Digital Forensics Practice. We are specifically seeking practitioner articles for this peer-reviewed, high-quality publication.
&lt;br&gt;&lt;br&gt;Feel free to contact me or editor-in-chief Marc Rogers (&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13958917&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;rogersmk@...&lt;/a&gt;) with any questions!
&lt;br&gt;&lt;br&gt;Later!
&lt;br&gt;/kess
&lt;br&gt;&lt;br&gt;&lt;br&gt;==========================================================================
&lt;br&gt;Gary C. Kessler &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13958917&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;gary.kessler@...&lt;/a&gt;
&lt;br&gt;Associate Professor &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Project Director
&lt;br&gt;Dir., Center for Digital Investigation &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Information Security
&lt;br&gt;Prog. Dir., Computer &amp; Digital Forensics &amp;nbsp; Vt. Information Technology Ctr.
&lt;br&gt;&lt;br&gt;Champlain College &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Office: +1 802-865-6460
&lt;br&gt;West Hall, Room 107 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Fax: +1 802-865-6446
&lt;br&gt;163 South Willard Street &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Cell: +1 802-238-8913
&lt;br&gt;Burlington, VT 05401 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Skype: gary.c.kessler
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://c3di.champlain.edu&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://c3di.champlain.edu&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13958917&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;kumquat@...&lt;/a&gt;
&lt;br&gt;&lt;a href=&quot;http://digitalforensics.champlain.edu&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://digitalforensics.champlain.edu&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://www.garykessler.net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.garykessler.net&lt;/a&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;PGP Public Keys: &lt;a href=&quot;http://www.garykessler.net/kumquat_pubkey.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.garykessler.net/kumquat_pubkey.html&lt;/a&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://digitalforensics.champlain.edu/gck/GaryKessler.asc&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://digitalforensics.champlain.edu/gck/GaryKessler.asc&lt;/a&gt;&lt;br&gt;&lt;br /&gt; &lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;JDFP-CFP.doc&lt;/strong&gt; (86K) &lt;a href=&quot;http://old.nabble.com/attachment/13958917/0/JDFP-CFP.doc&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Call-for-Papers----Journal-of-Digital-Forensics-Practice-tp13958917p13958917.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13958831</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-26T07:05:12Z</published>
	<updated>2007-11-26T07:05:12Z</updated>
	<author>
		<name>Terry Roebuck</name>
	</author>
	<content type="html">A*nix read only mount would be my option of choice, but for windows, I 
&lt;br&gt;hesitatingly ask could you not modify an IDE cable to make any connected 
&lt;br&gt;drive 'read-only' (might require a resistor - not sure if you can just 
&lt;br&gt;clip a wire? - maybe some one with better EE skills could answer that?)
&lt;br&gt;&lt;br&gt;Stefan Kelm wrote:
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt;&amp;gt;you can mount the storage as read-only - any unix filesystem will
&lt;br&gt;&amp;gt;&amp;gt;support read-only mount, and provided your root account isnt
&lt;br&gt;&amp;gt;&amp;gt;compromised, no one can remount it as write. Root cant write to
&lt;br&gt;&amp;gt;&amp;gt;read-only mounted filesystems without remount either.
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt;mount -r /dev/da2 /readonly in BSD land..
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; &amp;nbsp;
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;Beware, however, that on journaling file systems such as
&lt;br&gt;&amp;gt;ReiserFS or EXT3 you might incidentially change the file
&lt;br&gt;&amp;gt;system although it is mounted read-only:
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;&lt;a href=&quot;http://www.mail-archive.com/reiserfs-list@namesys.com/msg20263.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.mail-archive.com/reiserfs-list@.../msg20263.html&lt;/a&gt;&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;Cheers,
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;	Stefan.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;--------------------------------------------------------
&lt;br&gt;&amp;gt;Stefan Kelm
&lt;br&gt;&amp;gt;Security Consultant
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;Secorvo Security Consulting GmbH
&lt;br&gt;&amp;gt;Ettlinger Strasse 12-14, D-76137 Karlsruhe
&lt;br&gt;&amp;gt;Tel. +49 721 255171-304, Fax +49 721 255171-100
&lt;br&gt;&amp;gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13958831&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;stefan.kelm@...&lt;/a&gt;, &lt;a href=&quot;http://www.secorvo.de/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.secorvo.de/&lt;/a&gt;&lt;br&gt;&amp;gt;PGP: 87AE E858 CCBC C3A2 E633 D139 B0D9 212B
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;Mannheim HRB 108319, Geschaeftsfuehrer: Dirk Fox
&lt;br&gt;&amp;gt; &amp;nbsp;
&lt;br&gt;&amp;gt;
&lt;/div&gt;&lt;br&gt;-- 
&lt;br&gt;&lt;br&gt;Terry Roebuck
&lt;br&gt;Dept. of Computer Science
&lt;br&gt;&lt;a href=&quot;http://www.cs.usask.ca/people/faculty.shtml&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.cs.usask.ca/people/faculty.shtml&lt;/a&gt;&lt;br&gt;University of Saskatchewan
&lt;br&gt;306 966 2532 (office)
&lt;br&gt;306 966 4884 (dept office)
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13958831&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;terry.roebuck@...&lt;/a&gt; 
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13958831.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13958781</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-24T23:00:44Z</published>
	<updated>2007-11-24T23:00:44Z</updated>
	<author>
		<name>John Nemeth</name>
	</author>
	<content type="html">On Apr 12, &amp;nbsp;4:47am, Terry Roebuck wrote:
&lt;br&gt;}
&lt;br&gt;} A*nix mount with DD would be my option of choice, but for windows, I 
&lt;br&gt;} hesitatingly ask could you not modify an IDE cable to make any connected 
&lt;br&gt;} drive 'read-only' (might require a resistor - not sure if you can just 
&lt;br&gt;} clip a wire? - maybe some one with better EE skills could answer that?)
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;As I pointed out sometime in the last couple of weeks when this
&lt;br&gt;question was first asked, the difference between read and write is the
&lt;br&gt;command sent to the drive. &amp;nbsp;There is nothing you can do to the cable to
&lt;br&gt;stop writing that won't also stop reading. &amp;nbsp;You have to have an
&lt;br&gt;intelligent device that will monitor the commands sent to the drive and
&lt;br&gt;abort any write commands.
&lt;br&gt;&lt;br&gt;}-- End of excerpt from Terry Roebuck
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13958781.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13958736</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-24T21:49:07Z</published>
	<updated>2007-11-24T21:49:07Z</updated>
	<author>
		<name>Krassimir Tzvetanov</name>
	</author>
	<content type="html">Well this is a little one sided.
&lt;br&gt;&lt;br&gt;When you are preserving a hard disk you want a snapshot in the moment
&lt;br&gt;it was seized. This would mean that you should not do any alteration
&lt;br&gt;after that point and I'll ask you to consider two cases that will show
&lt;br&gt;you where I come from.
&lt;br&gt;&lt;br&gt;1. The journal replay may overwrite some chunks of data you may want
&lt;br&gt;to have linked the way they were. I.e. somebody did &amp;quot;rm -rf /&amp;quot; the
&lt;br&gt;moment the agents were serving a no know warrant (and if they turned
&lt;br&gt;off the machine the files will be still linked).
&lt;br&gt;&lt;br&gt;2. The kernel of the system you are running may have a bug that may
&lt;br&gt;result in a different behavior than the system being investigated. (or
&lt;br&gt;vice versa the system may had &amp;quot;special patches&amp;quot; applied that might
&lt;br&gt;cause your data replay to corrupt data.
&lt;br&gt;Even further think about a patch that ignores certain records of the
&lt;br&gt;journal file and those records when applied by a &amp;quot;unpatched kernel&amp;quot;
&lt;br&gt;unlink certain files (or overwrite them with random data).
&lt;br&gt;You should also do separate analysis on the journal itself to
&lt;br&gt;determine what contents it contains.
&lt;br&gt;Having said all that I do not reject the ability to present as a
&lt;br&gt;separate evidence replayed journal (*and note you did that*) to the
&lt;br&gt;investigators/court.
&lt;br&gt;&lt;br&gt;Regards,
&lt;br&gt;Krassi
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13958736.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13958952</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-24T17:23:59Z</published>
	<updated>2007-11-24T17:23:59Z</updated>
	<author>
		<name>Matthew Pepe</name>
	</author>
	<content type="html">The easiest thing to do is to use a bridge whose firmware can be &amp;nbsp;
&lt;br&gt;modified to take a different action upon the issuance of a write (or &amp;nbsp;
&lt;br&gt;write-related) command. &amp;nbsp;Operating systems will react differently &amp;nbsp;
&lt;br&gt;depending upon whether the device returns an error code, success code, &amp;nbsp;
&lt;br&gt;or remains quiet. &amp;nbsp;The bottom line is that you need to intercept &amp;nbsp;
&lt;br&gt;packetized commands - write enable is not based off of a pin pulled &amp;nbsp;
&lt;br&gt;high or low. For more information, check out the ATA/ATAPI5 documents &amp;nbsp;
&lt;br&gt;from the T13 working group.
&lt;br&gt;&lt;br&gt;- Matt
&lt;br&gt;&lt;br&gt;&lt;br&gt;On Nov 20, 2007, at 11:11 AM, Terry Roebuck wrote:
&lt;br&gt;&lt;br&gt;&amp;gt; A*nix mount with DD would be my option of choice, but for windows, I &amp;nbsp;
&lt;br&gt;&amp;gt; hesitatingly ask could you not modify an IDE cable to make any &amp;nbsp;
&lt;br&gt;&amp;gt; connected drive 'read-only' (might require a resistor - not sure if &amp;nbsp;
&lt;br&gt;&amp;gt; you can just clip a wire? - maybe some one with better EE skills &amp;nbsp;
&lt;br&gt;&amp;gt; could answer that?)
&lt;br&gt;&lt;br&gt;&lt;br /&gt; &lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;smime.p7s&lt;/strong&gt; (3K) &lt;a href=&quot;http://old.nabble.com/attachment/13958952/0/smime.p7s&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13958952.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13931473</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-21T13:08:03Z</published>
	<updated>2007-11-21T13:08:03Z</updated>
	<author>
		<name>Valdis.Kletnieks</name>
	</author>
	<content type="html">On Fri, 16 Nov 2007 22:14:07 EST, Max Gribov said:
&lt;br&gt;&amp;gt; Tom,
&lt;br&gt;&amp;gt; you can mount the storage as read-only - any unix filesystem will 
&lt;br&gt;&amp;gt; support read-only mount, and provided your root account isnt 
&lt;br&gt;&amp;gt; compromised, no one can remount it as write. Root cant write to 
&lt;br&gt;&amp;gt; read-only mounted filesystems without remount either.
&lt;br&gt;&lt;br&gt;Note that most journaled file systems (on Linux, this includes ext3, reiserfs,
&lt;br&gt;jfs, and xfs) will insist on replaying the journal and thus making changes
&lt;br&gt;to the disk, even when mounting as read-only.
&lt;br&gt;&lt;br&gt;You'd really want to have some other utility that captures the journal
&lt;br&gt;datastream before you do the mount, and then a utility to reverse-apply
&lt;br&gt;the changes. In some cases, this may not be doable, as the journal doesn't
&lt;br&gt;record what the status was *before* the event - for instance, a file permission
&lt;br&gt;change event may only have the *new* value listed, so you can't roll it back.
&lt;br&gt;&lt;br&gt;There's also another issue - if you *do* create a &amp;quot;mount without journal
&lt;br&gt;replay&amp;quot;, you're quite likely going to screw things up gloriously, as the
&lt;br&gt;whole *point* of the journal is to gloss over inconsistent data that hasn't
&lt;br&gt;been fully synced to disk. &amp;nbsp;You don't replay the journal, you may find some
&lt;br&gt;parts of the filesystem (those that are affected by live journal entries)
&lt;br&gt;won't be accurate, or may even crash the system. &amp;nbsp;Of course, there's a very
&lt;br&gt;high probability that &amp;quot;the files that the hacker was working on when we
&lt;br&gt;pulled the plug&amp;quot; are *exactly* the pieces most likely to be zorkumblattum
&lt;br&gt;if you don't replay the journal....
&lt;br&gt;&lt;br&gt;And I won't even get into the forensics-relevant semantics of ext3's
&lt;br&gt;data=journaled/ordered/writeback options, other than to note that they *do*
&lt;br&gt;have forensics implications....
&lt;br&gt;&lt;br /&gt; &lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;attachment0&lt;/strong&gt; (234 bytes) &lt;a href=&quot;http://old.nabble.com/attachment/13931473/0/attachment0&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13931473.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13931456</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-20T08:11:26Z</published>
	<updated>2007-11-20T08:11:26Z</updated>
	<author>
		<name>Terry Roebuck</name>
	</author>
	<content type="html">A*nix mount with DD would be my option of choice, but for windows, I 
&lt;br&gt;hesitatingly ask could you not modify an IDE cable to make any connected 
&lt;br&gt;drive 'read-only' (might require a resistor - not sure if you can just 
&lt;br&gt;clip a wire? - maybe some one with better EE skills could answer that?)
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13931456.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13931443</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-20T00:27:03Z</published>
	<updated>2007-11-20T00:27:03Z</updated>
	<author>
		<name>Stefan Kelm</name>
	</author>
	<content type="html">&amp;gt; you can mount the storage as read-only - any unix filesystem will
&lt;br&gt;&amp;gt; support read-only mount, and provided your root account isnt
&lt;br&gt;&amp;gt; compromised, no one can remount it as write. Root cant write to
&lt;br&gt;&amp;gt; read-only mounted filesystems without remount either.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; mount -r /dev/da2 /readonly in BSD land..
&lt;br&gt;&lt;br&gt;Beware, however, that on journaling file systems such as
&lt;br&gt;ReiserFS or EXT3 you might incidentially change the file
&lt;br&gt;system although it is mounted read-only:
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.mail-archive.com/reiserfs-list@namesys.com/msg20263.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.mail-archive.com/reiserfs-list@.../msg20263.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;Cheers,
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Stefan.
&lt;br&gt;&lt;br&gt;--------------------------------------------------------
&lt;br&gt;Stefan Kelm
&lt;br&gt;Security Consultant
&lt;br&gt;&lt;br&gt;Secorvo Security Consulting GmbH
&lt;br&gt;Ettlinger Strasse 12-14, D-76137 Karlsruhe
&lt;br&gt;Tel. +49 721 255171-304, Fax +49 721 255171-100
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13931443&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;stefan.kelm@...&lt;/a&gt;, &lt;a href=&quot;http://www.secorvo.de/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.secorvo.de/&lt;/a&gt;&lt;br&gt;PGP: 87AE E858 CCBC C3A2 E633 D139 B0D9 212B
&lt;br&gt;&lt;br&gt;Mannheim HRB 108319, Geschaeftsfuehrer: Dirk Fox
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13931443.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13849722</id>
	<title>RE: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-19T11:06:11Z</published>
	<updated>2007-11-19T11:06:11Z</updated>
	<author>
		<name>Kian Stipp</name>
	</author>
	<content type="html">&lt;a href=&quot;http://irongeek.com/i.php?page=security/thumbscrew-software-usb-write-blocke&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://irongeek.com/i.php?page=security/thumbscrew-software-usb-write-blocke&lt;/a&gt;&lt;br&gt;r
&lt;br&gt;&lt;br&gt;&amp;quot;If you want to go the cheapest route, use a linux system with auto mounting
&lt;br&gt;disabled and buy some USB or Firewire drive enclosures. If you go this route
&lt;br&gt;make sure you create a documented procedure for acquiring evidence and
&lt;br&gt;follow it every time. You might even go as far as to record the history of
&lt;br&gt;your shell commands as part of your digital case file.&amp;quot;- warquel Re:
&lt;br&gt;Forensic write blockers &amp;lt; Reply #1 on: July 05, 2007, 12:28:52 AM &amp;gt;
&lt;br&gt;&lt;a href=&quot;http://www.ethicalhacker.net/index.php?option=com_smf&amp;Itemid=&amp;topic=1405.msg&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.ethicalhacker.net/index.php?option=com_smf&amp;Itemid=&amp;topic=1405.msg&lt;/a&gt;&lt;br&gt;5441
&lt;br&gt;&lt;br&gt;Hope this helps!
&lt;br&gt;&lt;br&gt;Kian
&lt;br&gt;White Hat Group
&lt;br&gt;&lt;br&gt;-----Original Message-----
&lt;br&gt;From: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13849722&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;listbounce@...&lt;/a&gt; [mailto:&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13849722&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;listbounce@...&lt;/a&gt;] On
&lt;br&gt;Behalf Of Tom Yarrish
&lt;br&gt;Sent: Tuesday, November 13, 2007 7:00 PM
&lt;br&gt;To: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13849722&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;forensics@...&lt;/a&gt;
&lt;br&gt;Subject: Converting an external hard drive enclosure into a write blocker?
&lt;br&gt;&lt;br&gt;-----BEGIN PGP SIGNED MESSAGE-----
&lt;br&gt;Hash: SHA1
&lt;br&gt;&lt;br&gt;Hey all,
&lt;br&gt;I wanted to find out if there was a method to convert an external &amp;nbsp;
&lt;br&gt;hard drive enclosure into a &amp;quot;cheap&amp;quot; write blocker device? &amp;nbsp;I'm not &amp;nbsp;
&lt;br&gt;looking for something to use from a forensic standpoint. &amp;nbsp;Basically &amp;nbsp;
&lt;br&gt;if I want to put a hard drive into an enclosure and pull data/burn &amp;nbsp;
&lt;br&gt;data to DVD/whatever off of it, but prevent anything from being &amp;nbsp;
&lt;br&gt;written to the drive, I can do that.
&lt;br&gt;&lt;br&gt;Thanks ahead of time,
&lt;br&gt;Tom
&lt;br&gt;-----BEGIN PGP SIGNATURE-----
&lt;br&gt;Version: GnuPG v1.4.7 (Darwin)
&lt;br&gt;&lt;br&gt;iD8DBQFHOmStZWzkfeDiTw4RAqcdAJ9FZ+QX3tnajnV4yaUPhK/R/xcqogCfV9Br
&lt;br&gt;h+Fb956D4hQWWJ2roctoIT8=
&lt;br&gt;=EOp6
&lt;br&gt;-----END PGP SIGNATURE-----
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13849722.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13849633</id>
	<title>RE: [Fwd: AOL file structure and utilities]</title>
	<published>2007-11-18T05:24:39Z</published>
	<updated>2007-11-18T05:24:39Z</updated>
	<author>
		<name>Greg Kelley</name>
	</author>
	<content type="html">We have used ePreserver Forensic for pfc files. 
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.connectedsw.com/Overview/36400&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.connectedsw.com/Overview/36400&lt;/a&gt;. 
&lt;br&gt;&lt;br&gt;Greg Kelley, EnCE
&lt;br&gt;Vestige, Ltd
&lt;br&gt;&lt;br&gt;-----Original Message----- 
&lt;br&gt;From: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13849633&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;listbounce@...&lt;/a&gt; on behalf of James G. McIntyre 
&lt;br&gt;Sent: Fri 11/16/2007 12:01 PM 
&lt;br&gt;To: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13849633&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;forensics@...&lt;/a&gt; 
&lt;br&gt;Cc: 
&lt;br&gt;Subject: [Fwd: AOL file structure and utilities]
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Anyone know of any docs or utilities for analyzing AOL files, for
&lt;br&gt;example
&lt;br&gt;pfc and feedbag etc. ?
&lt;br&gt;&lt;br&gt;Any assistance would be appreciated.
&lt;br&gt;&lt;br&gt;Jim Mc....
&lt;br&gt;&lt;br&gt;&lt;br&gt;--
&lt;br&gt;&lt;br&gt;&lt;br&gt;--
&lt;br&gt;James G. McIntyre
&lt;br&gt;Senior Consultant
&lt;br&gt;SANS/GIAC - GCIA Certified Intrusion Analyst
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - GCFW Certified Firewall Analyst
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - GAWN Auditing Wireless Networks
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - GWAS Web Application Security
&lt;br&gt;HP-UX Certified System Administrator
&lt;br&gt;&lt;br&gt;McIntyre &amp; Associates, Inc.
&lt;br&gt;Virginia Tech Corporate Research Center
&lt;br&gt;2020 Kraft Drive, Suite 3005
&lt;br&gt;Blacksburg, VA &amp;nbsp;24060
&lt;br&gt;540-552-9090
&lt;br&gt;www.mcintyresecurity.com
&lt;br&gt;&lt;br&gt;PROPRIETARY NOTICE
&lt;br&gt;This e-mail and its attachments contain proprietary information that is
&lt;br&gt;intended only for the individual or entity indicated. &amp;nbsp;If you are not
&lt;br&gt;the
&lt;br&gt;intended recipient, you are hereby notified that the disclosure,
&lt;br&gt;copying,
&lt;br&gt;distribution or use of the contents of this transmission is strictly
&lt;br&gt;prohibited, and no privilege or protection has been waived. &amp;nbsp;If you have
&lt;br&gt;received this communication in error, please notify the sender
&lt;br&gt;immediately
&lt;br&gt;and then delete the message from your computer.
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-Fwd%3A-AOL-file-structure-and-utilities--tp13805290p13849633.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13849704</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-17T14:19:18Z</published>
	<updated>2007-11-17T14:19:18Z</updated>
	<author>
		<name>forensics-4</name>
	</author>
	<content type="html">If it is a USB enclosure and you have Windows XP service Pack 2 use
&lt;br&gt;the USB write Protect.
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.m2cfg.com/usb_writeblock.htm&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.m2cfg.com/usb_writeblock.htm&lt;/a&gt;&lt;br&gt;&lt;br&gt;Turn write block on before plugging in the drive.
&lt;br&gt;&lt;br&gt;Thanks
&lt;br&gt;&lt;br&gt;Mike
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13849704.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13849605</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-16T23:58:09Z</published>
	<updated>2007-11-16T23:58:09Z</updated>
	<author>
		<name>Pavel Gladyshev</name>
	</author>
	<content type="html">&lt;br&gt;If your computer is running Windows XP Service Pack 2, see 
&lt;br&gt;&lt;a href=&quot;http://www.accessdata.com/media/en_US/print/papers/wp.USB_Write_Protect.en_us.pdf&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.accessdata.com/media/en_US/print/papers/wp.USB_Write_Protect.en_us.pdf&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Tom Yarrish wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; -----BEGIN PGP SIGNED MESSAGE-----
&lt;br&gt;&amp;gt; Hash: SHA1
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Hey all,
&lt;br&gt;&amp;gt; I wanted to find out if there was a method to convert an external hard 
&lt;br&gt;&amp;gt; drive enclosure into a &amp;quot;cheap&amp;quot; write blocker device? &amp;nbsp;I'm not looking 
&lt;br&gt;&amp;gt; for something to use from a forensic standpoint. &amp;nbsp;Basically if I want 
&lt;br&gt;&amp;gt; to put a hard drive into an enclosure and pull data/burn data to 
&lt;br&gt;&amp;gt; DVD/whatever off of it, but prevent anything from being written to the 
&lt;br&gt;&amp;gt; drive, I can do that.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Thanks ahead of time,
&lt;br&gt;&amp;gt; Tom
&lt;br&gt;&amp;gt; -----BEGIN PGP SIGNATURE-----
&lt;br&gt;&amp;gt; Version: GnuPG v1.4.7 (Darwin)
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; iD8DBQFHOmStZWzkfeDiTw4RAqcdAJ9FZ+QX3tnajnV4yaUPhK/R/xcqogCfV9Br
&lt;br&gt;&amp;gt; h+Fb956D4hQWWJ2roctoIT8=
&lt;br&gt;&amp;gt; =EOp6
&lt;br&gt;&amp;gt; -----END PGP SIGNATURE-----
&lt;br&gt;&amp;gt;
&lt;/div&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13849605.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13849585</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-16T19:25:15Z</published>
	<updated>2007-11-16T19:25:15Z</updated>
	<author>
		<name>John Nemeth</name>
	</author>
	<content type="html">On Apr 5, &amp;nbsp;3:35pm, Tom Yarrish wrote:
&lt;br&gt;} 
&lt;br&gt;} I wanted to find out if there was a method to convert an external &amp;nbsp;
&lt;br&gt;} hard drive enclosure into a &amp;quot;cheap&amp;quot; write blocker device? &amp;nbsp;I'm not &amp;nbsp;
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;The only difference between read and write is the command issued.
&lt;br&gt;You would need an intelligent adapter that sits between the cable
&lt;br&gt;coming into the enclosure and the drive which analyses all commands and
&lt;br&gt;aborts any write commands.
&lt;br&gt;&lt;br&gt;}-- End of excerpt from Tom Yarrish
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13849585.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13849677</id>
	<title>Re: Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-16T19:14:07Z</published>
	<updated>2007-11-16T19:14:07Z</updated>
	<author>
		<name>Max Gribov</name>
	</author>
	<content type="html">Tom,
&lt;br&gt;you can mount the storage as read-only - any unix filesystem will 
&lt;br&gt;support read-only mount, and provided your root account isnt 
&lt;br&gt;compromised, no one can remount it as write. Root cant write to 
&lt;br&gt;read-only mounted filesystems without remount either.
&lt;br&gt;&lt;br&gt;mount -r /dev/da2 /readonly in BSD land..
&lt;br&gt;&lt;br&gt;Id say thats the easiest route without buying specialized hardware.
&lt;br&gt;&lt;br&gt;Sorry if this is something you already tried/thought about..
&lt;br&gt;&lt;br&gt;Tom Yarrish wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; -----BEGIN PGP SIGNED MESSAGE-----
&lt;br&gt;&amp;gt; Hash: SHA1
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Hey all,
&lt;br&gt;&amp;gt; I wanted to find out if there was a method to convert an external hard 
&lt;br&gt;&amp;gt; drive enclosure into a &amp;quot;cheap&amp;quot; write blocker device? &amp;nbsp;I'm not looking 
&lt;br&gt;&amp;gt; for something to use from a forensic standpoint. &amp;nbsp;Basically if I want 
&lt;br&gt;&amp;gt; to put a hard drive into an enclosure and pull data/burn data to 
&lt;br&gt;&amp;gt; DVD/whatever off of it, but prevent anything from being written to the 
&lt;br&gt;&amp;gt; drive, I can do that.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Thanks ahead of time,
&lt;br&gt;&amp;gt; Tom
&lt;br&gt;&amp;gt; -----BEGIN PGP SIGNATURE-----
&lt;br&gt;&amp;gt; Version: GnuPG v1.4.7 (Darwin)
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; iD8DBQFHOmStZWzkfeDiTw4RAqcdAJ9FZ+QX3tnajnV4yaUPhK/R/xcqogCfV9Br
&lt;br&gt;&amp;gt; h+Fb956D4hQWWJ2roctoIT8=
&lt;br&gt;&amp;gt; =EOp6
&lt;br&gt;&amp;gt; -----END PGP SIGNATURE-----
&lt;/div&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13849677.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13805290</id>
	<title>[Fwd: AOL file structure and utilities]</title>
	<published>2007-11-16T09:01:43Z</published>
	<updated>2007-11-16T09:01:43Z</updated>
	<author>
		<name>James G. McIntyre</name>
	</author>
	<content type="html">&lt;br&gt;Anyone know of any docs or utilities for analyzing AOL files, for example
&lt;br&gt;pfc and feedbag etc. ?
&lt;br&gt;&lt;br&gt;Any assistance would be appreciated.
&lt;br&gt;&lt;br&gt;Jim Mc....
&lt;br&gt;&lt;br&gt;&lt;br&gt;--
&lt;br&gt;&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;James G. McIntyre
&lt;br&gt;Senior Consultant
&lt;br&gt;SANS/GIAC - GCIA Certified Intrusion Analyst
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - GCFW Certified Firewall Analyst
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - GAWN Auditing Wireless Networks
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - GWAS Web Application Security
&lt;br&gt;HP-UX Certified System Administrator
&lt;br&gt;&lt;br&gt;McIntyre &amp; Associates, Inc.
&lt;br&gt;Virginia Tech Corporate Research Center
&lt;br&gt;2020 Kraft Drive, Suite 3005
&lt;br&gt;Blacksburg, VA &amp;nbsp;24060
&lt;br&gt;540-552-9090
&lt;br&gt;www.mcintyresecurity.com
&lt;br&gt;&lt;br&gt;PROPRIETARY NOTICE
&lt;br&gt;This e-mail and its attachments contain proprietary information that is
&lt;br&gt;intended only for the individual or entity indicated. &amp;nbsp;If you are not the
&lt;br&gt;intended recipient, you are hereby notified that the disclosure, copying,
&lt;br&gt;distribution or use of the contents of this transmission is strictly
&lt;br&gt;prohibited, and no privilege or protection has been waived. &amp;nbsp;If you have
&lt;br&gt;received this communication in error, please notify the sender immediately
&lt;br&gt;and then delete the message from your computer.
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-Fwd%3A-AOL-file-structure-and-utilities--tp13805290p13805290.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13805268</id>
	<title>Patchlevel 2 release open computer forensics architecture.</title>
	<published>2007-11-16T00:36:49Z</published>
	<updated>2007-11-16T00:36:49Z</updated>
	<author>
		<name>Rob Meijer-4</name>
	</author>
	<content type="html">The new 2.0.6pl2 release of the open computer forensics architecture
&lt;br&gt;(ocfa) has been put on sourceforge. The most important patches are:
&lt;br&gt;&lt;br&gt;* More strict configure scripts.
&lt;br&gt;&amp;nbsp; Fixes in configure for 64 bit (suse) platforms.
&lt;br&gt;* Aditional rulelist for SLES 9, to work around the
&lt;br&gt;&amp;nbsp; problem that unzip is compiled without large file
&lt;br&gt;&amp;nbsp; support. As a workaround 7z module is used.
&lt;br&gt;* Workaround for 7z bug that makes it produce its input file
&lt;br&gt;&amp;nbsp; as output if the file names ends with 'aa'
&lt;br&gt;* Added workaround for indexer memory allocation problem.
&lt;br&gt;&amp;nbsp; Clucene grows its memory usage to about 4 times the size of
&lt;br&gt;&amp;nbsp; the largest file it is given to index, the workaround now makes
&lt;br&gt;&amp;nbsp; sure the indexer does not get and/or process large files.
&lt;br&gt;&lt;br&gt;The indexer problem solution, being a workaround is something we will take
&lt;br&gt;as a main priority for upcomming releases. We are considdering dropping
&lt;br&gt;the clucene based indexer and moving to the java version of lucene.
&lt;br&gt;The upcomming 2.0.8 release will include some enhancements (xml based
&lt;br&gt;serialisation for messaging) that should allow more easy integration of
&lt;br&gt;other programming languages based modules, that should help us move more
&lt;br&gt;cleanly to the java implementation of lucene.
&lt;br&gt;&lt;br&gt;CarvFs/LibEwf integration has run into an unexpected delay as a result of
&lt;br&gt;composit memory consumption of carvfs/libewf in situations where numerous
&lt;br&gt;encase images are mounted into the repository and are then iterated.
&lt;br&gt;&lt;br&gt;Rob Meijer
&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Patchlevel-2-release-open-computer-forensics-architecture.-tp13805268p13805268.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13805317</id>
	<title>Re: Log in as administrator with live data collection CD?</title>
	<published>2007-11-15T16:33:24Z</published>
	<updated>2007-11-15T16:33:24Z</updated>
	<author>
		<name>H Carvey</name>
	</author>
	<content type="html">Matt and Kelly,
&lt;br&gt;&lt;br&gt;&amp;gt; I guess there is one point here that leads to
&lt;br&gt;&amp;gt; possible issues a cd to forensically collect 
&lt;br&gt;&amp;gt; evidence for law enforcement would require that
&lt;br&gt;&amp;gt; you collect the data with a device that could 
&lt;br&gt;&amp;gt; not write to the hard disk, 
&lt;br&gt;&lt;br&gt;What if you could collect the data you needed, but know and be able to show that the likelihood of you changing data is low to unlikely? &amp;nbsp;
&lt;br&gt;&lt;br&gt;&amp;gt; The issue with a disk that would collect 
&lt;br&gt;&amp;gt; real-time as the OS was logged in with a 
&lt;br&gt;&amp;gt; administrator would give you the ability to 
&lt;br&gt;&amp;gt; change the data 
&lt;br&gt;&lt;br&gt;It may give you the ability, but that doesn't mean that you're going to destroy or create evidence. &amp;nbsp;In the real world, LEOs have the ability all the time to plant or modify evidence...but that doesn't mean that they do. 
&lt;br&gt;&lt;br&gt;&amp;gt;&amp;gt; I could use PSexec or runas or something to log
&lt;br&gt;&amp;gt;&amp;gt; in as administrator, but I have a concern that 
&lt;br&gt;&amp;gt;&amp;gt; this may alter important information on the 
&lt;br&gt;&amp;gt;&amp;gt; computer. 
&lt;br&gt;&lt;br&gt;Of course it will...any time you interact with a live machine, you're going to alter something. &amp;nbsp;The question isn't one of altering data on the system, but can you show that you understand that, and do you have documentation of your actions?
&lt;br&gt;&lt;br&gt;LEOs interact with crime scenes and evidence all the time. &amp;nbsp;However, they have processes and documentation...why should the digital world be any different?
&lt;br&gt;&lt;br&gt;&amp;gt;&amp;gt; The question I have is, what is the best policy
&lt;br&gt;&amp;gt;&amp;gt; when creating a forensic boot disk? 
&lt;br&gt;&lt;br&gt;Okay, I'm confused...you started out asking about a &amp;quot;live data collection forensic CD&amp;quot;, and know int the same paragraph you're referring to a forensic boot disk. &amp;nbsp;You're aware, I'm sure, that a bootdisk obviates the need for a &amp;quot;live data collection forensic CD&amp;quot;.
&lt;br&gt;&lt;br&gt;&amp;gt;&amp;gt; Is it best to wait for the information or have 
&lt;br&gt;&amp;gt;&amp;gt; the CD log in as local administrator to collect
&lt;br&gt;&amp;gt;&amp;gt; information in a timely fashion before shutting
&lt;br&gt;&amp;gt;&amp;gt; down? I do have the local admin password so 
&lt;br&gt;&amp;gt;&amp;gt; that is not an issue. I am talking about 
&lt;br&gt;&amp;gt;&amp;gt; windows boxes.
&lt;br&gt;&lt;br&gt;I would think that it would be best to document what you do thoroughly. &amp;nbsp;Do some testing to show due diligence, and then document what you do.
&lt;br&gt;&lt;br&gt;Harlan
&lt;br&gt;&lt;a href=&quot;http://windowsir.blogspot.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://windowsir.blogspot.com&lt;/a&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Log-in-as-administrator-with-live-data-collection-CD--tp13684809p13805317.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13805281</id>
	<title>Converting an external hard drive enclosure into a write blocker?</title>
	<published>2007-11-13T18:59:56Z</published>
	<updated>2007-11-13T18:59:56Z</updated>
	<author>
		<name>Tom Yarrish</name>
	</author>
	<content type="html">-----BEGIN PGP SIGNED MESSAGE-----
&lt;br&gt;Hash: SHA1
&lt;br&gt;&lt;br&gt;Hey all,
&lt;br&gt;I wanted to find out if there was a method to convert an external &amp;nbsp;
&lt;br&gt;hard drive enclosure into a &amp;quot;cheap&amp;quot; write blocker device? &amp;nbsp;I'm not &amp;nbsp;
&lt;br&gt;looking for something to use from a forensic standpoint. &amp;nbsp;Basically &amp;nbsp;
&lt;br&gt;if I want to put a hard drive into an enclosure and pull data/burn &amp;nbsp;
&lt;br&gt;data to DVD/whatever off of it, but prevent anything from being &amp;nbsp;
&lt;br&gt;written to the drive, I can do that.
&lt;br&gt;&lt;br&gt;Thanks ahead of time,
&lt;br&gt;Tom
&lt;br&gt;-----BEGIN PGP SIGNATURE-----
&lt;br&gt;Version: GnuPG v1.4.7 (Darwin)
&lt;br&gt;&lt;br&gt;iD8DBQFHOmStZWzkfeDiTw4RAqcdAJ9FZ+QX3tnajnV4yaUPhK/R/xcqogCfV9Br
&lt;br&gt;h+Fb956D4hQWWJ2roctoIT8=
&lt;br&gt;=EOp6
&lt;br&gt;-----END PGP SIGNATURE-----
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Converting-an-external-hard-drive-enclosure-into-a-write-blocker--tp13805281p13805281.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13805257</id>
	<title>Re: Forensics on Terminal Server Client</title>
	<published>2007-11-13T08:59:39Z</published>
	<updated>2007-11-13T08:59:39Z</updated>
	<author>
		<name>TheGesus</name>
	</author>
	<content type="html">If you dump one of the *.bmc files it's pretty obvious from the number
&lt;br&gt;of repeating byte patterns that it's not compressed (or encrypted).
&lt;br&gt;&lt;br&gt;And if you compress one of the files, it will compress nicely, which
&lt;br&gt;is a fairly good indicator that they're not compressed to begin with.
&lt;br&gt;&lt;br&gt;On Nov 10, 2007 3:28 PM, Mike Theriault &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13805257&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;Mike_Theriault@...&lt;/a&gt;&amp;gt; wrote:
&lt;br&gt;&amp;gt; It's probably compressed so in that case you probably wont find any header information.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Mike Theriault
&lt;br&gt;&amp;gt; Security Enginer
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Forensics-on-Terminal-Server-Client-tp13558955p13805257.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13697242</id>
	<title>Re: Log in as administrator with live data collection CD?</title>
	<published>2007-11-11T08:08:09Z</published>
	<updated>2007-11-11T08:08:09Z</updated>
	<author>
		<name>Kelly Keeton</name>
	</author>
	<content type="html">I guess there is one point here that leads to possible issues a cd to
&lt;br&gt;forensically collect evidence for law enforcement would require that
&lt;br&gt;you collect the data with a device that could not write to the hard
&lt;br&gt;disk, or alter data in any way. The issue with a disk that would
&lt;br&gt;collect real-time as the OS was logged in with a administrator would
&lt;br&gt;give you the ability to change the data prior to collection, thusly
&lt;br&gt;you don't have credibility on the collection of the data in its
&lt;br&gt;original form.
&lt;br&gt;&lt;br&gt;as for your 20 min problem, I assume that your hitting a timeout of
&lt;br&gt;file access due to permissions, so you might want to code in a error
&lt;br&gt;routine so that your not waiting on windows API to time out.
&lt;br&gt;&lt;br&gt;I created a super &amp;quot;slurp&amp;quot; tool a while back primarily used for backup
&lt;br&gt;of data in a flash, also for non-legal investigation work.
&lt;br&gt;&lt;br&gt;On Nov 7, 2007 5:41 AM, Matthew Webster &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13697242&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;awakenings@...&lt;/a&gt;&amp;gt; wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Hello,
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; &amp;nbsp; &amp;nbsp; I am almost finished creating a live data collection forensic CD, but I've noticed it is slow (20 minutes when it should be 3-5 minutes) when running on computers that are not logged in as administrator. &amp;nbsp;I could use PSexec or runas or something to log in as administrator, but I have a concern that this may alter important information &amp;nbsp;on the computer. &amp;nbsp;The question I have is, what is the best policy when creating a forensic boot disk? &amp;nbsp;Is it best to wait for the information or have the CD log in as local administrator to collect information in a timely fashion before shutting down? &amp;nbsp;I do have the local admin password so that is not an issue. &amp;nbsp;I am talking about windows boxes.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Thanks,
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Matt
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Log-in-as-administrator-with-live-data-collection-CD--tp13684809p13697242.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13697230</id>
	<title>RE: Forensics on Terminal Server Client</title>
	<published>2007-11-10T12:28:39Z</published>
	<updated>2007-11-10T12:28:39Z</updated>
	<author>
		<name>Mike Theriault</name>
	</author>
	<content type="html">It's probably compressed so in that case you probably wont find any header information.
&lt;br&gt;&lt;br&gt;Mike Theriault
&lt;br&gt;Security Enginer</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Forensics-on-Terminal-Server-Client-tp13558955p13697230.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13684929</id>
	<title>CanSecWest 2008 CFP (deadline Nov 30, conf Mar 26-28) and PacSec Dojo's</title>
	<published>2007-11-08T20:24:13Z</published>
	<updated>2007-11-08T20:24:13Z</updated>
	<author>
		<name>Dragos Ruiu</name>
	</author>
	<content type="html">I'd like to congratulate Adam Laurie for winning the second Powerbook
&lt;br&gt;from the Pwn_to_Own contest as the prize for the best speaker rated
&lt;br&gt;by the audience for his presentation on RFID at CanSecWest 2007.
&lt;br&gt;We will have a similar prize for the best speaker at CanSecWest 2008,
&lt;br&gt;prize TBD (but we promise it will be cool - depending on what we find
&lt;br&gt;trawling though the electronics shops in Akihabara this year :).
&lt;br&gt;&lt;br&gt;**
&lt;br&gt;&lt;br&gt;The Security Masters Dojo courses available at PacSec in Tokyo
&lt;br&gt;on November 27/28 2007 have been updated. The final list is:
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;Ultimate Web Hacking &amp;nbsp;- Yeng-Min Chen (Japanese)
&lt;br&gt;&amp;nbsp; &amp;nbsp;Reverse Engineering &amp;nbsp;- Yuji Ukai (Japanese)
&lt;br&gt;&amp;nbsp; &amp;nbsp;The Exploit Laboratory - Saumil Shah (English)
&lt;br&gt;&amp;nbsp; &amp;nbsp;Advanced Honeypot Tactics - Thorsten Holz (English)
&lt;br&gt;&amp;nbsp; &amp;nbsp;Advanced Linux Hardening - Andrea Barisani (English)
&lt;br&gt;&amp;nbsp; &amp;nbsp;Bugfinding with the Immunity Debugger - Nicolas Waisman &amp; Kostya 
&lt;br&gt;Kortchinski (English)
&lt;br&gt;&amp;nbsp; &amp;nbsp;Practical 802.11 Wi-Fi (In)Security - Cedric Blancher (English)
&lt;br&gt;&lt;br&gt;**
&lt;br&gt;&lt;br&gt;CanSecWest 2008 CALL FOR PAPERS
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;VANCOUVER, Canada -- The ninth annual CanSecWest applied technical
&lt;br&gt;&amp;nbsp; &amp;nbsp;security conference - where the eminent figures in the
&lt;br&gt;&amp;nbsp; &amp;nbsp;international security industry will get together share best
&lt;br&gt;&amp;nbsp; &amp;nbsp;practices and technology - will be held in downtown Vancouver at
&lt;br&gt;&amp;nbsp; &amp;nbsp;the the Mariott Renaissance Harbourside on March 26-28, 2008. &amp;nbsp;The
&lt;br&gt;&amp;nbsp; &amp;nbsp;most significant new discoveries about computer network hack
&lt;br&gt;&amp;nbsp; &amp;nbsp;attacks and defenses, commercial security solutions, and pragmatic
&lt;br&gt;&amp;nbsp; &amp;nbsp;real world security experience will be presented in a series of
&lt;br&gt;&amp;nbsp; &amp;nbsp;informative tutorials.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;The CanSecWest meeting provides international researchers a
&lt;br&gt;&amp;nbsp; &amp;nbsp;relaxed, comfortable environment to learn from informative
&lt;br&gt;&amp;nbsp; &amp;nbsp;tutorials on key developments in security technology, and
&lt;br&gt;&amp;nbsp; &amp;nbsp;collaborate and socialize with their peers in one of the world's
&lt;br&gt;&amp;nbsp; &amp;nbsp;most scenic cities - a short drive away from one of North
&lt;br&gt;&amp;nbsp; &amp;nbsp;America's top skiing areas.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;The CanSecWest conference will also feature the availability of
&lt;br&gt;&amp;nbsp; &amp;nbsp;the Security Masters Dojo expert network security sensei
&lt;br&gt;&amp;nbsp; &amp;nbsp;instructors, and their advanced, and intermediate, hands-on
&lt;br&gt;&amp;nbsp; &amp;nbsp;training courses - featuring small class sizes and practical
&lt;br&gt;&amp;nbsp; &amp;nbsp;application excercises to maximize information transfer.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;We would like to announce the opportunity to submit papers, and/or
&lt;br&gt;&amp;nbsp; &amp;nbsp;lightning talk proposals for selection by the CanSecWest technical
&lt;br&gt;&amp;nbsp; &amp;nbsp;review committee. This year we will be doing one hour talks, and
&lt;br&gt;&amp;nbsp; &amp;nbsp;some shorter 20/30 minute talk sessions.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;Please make your paper proposal submissions before November 30th,
&lt;br&gt;&amp;nbsp; &amp;nbsp;2007.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;Some invited papers have been confirmed, but a limited number of
&lt;br&gt;&amp;nbsp; &amp;nbsp;speaking slots are still available. The conference is responsible
&lt;br&gt;&amp;nbsp; &amp;nbsp;for travel and accomodations for the speakers. If you have a
&lt;br&gt;&amp;nbsp; &amp;nbsp;proposal for a tutorial session then please email a synopsis of
&lt;br&gt;&amp;nbsp; &amp;nbsp;the material and your biography, papers and, speaking background
&lt;br&gt;&amp;nbsp; &amp;nbsp;to &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13684929&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;_secwest08_@...&lt;/a&gt; (please remove _'s). Only 
&lt;br&gt;&amp;nbsp; &amp;nbsp;slides will be needed for the March paper deadline, full text does 
&lt;br&gt;&amp;nbsp; &amp;nbsp;not have to be submitted - but will be accepted if available.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;The CanSecWest 2008 conference consists of tutorials on technical
&lt;br&gt;&amp;nbsp; &amp;nbsp;details about current issues, innovative techniques and best
&lt;br&gt;&amp;nbsp; &amp;nbsp;practices in the information security realm. The audiences are a
&lt;br&gt;&amp;nbsp; &amp;nbsp;multi-national mix of professionals involved on a daily basis with
&lt;br&gt;&amp;nbsp; &amp;nbsp;security work: security product vendors, programmers, security
&lt;br&gt;&amp;nbsp; &amp;nbsp;officers, and network administrators. We give preference to
&lt;br&gt;&amp;nbsp; &amp;nbsp;technical details and new education for a technical audience.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;The conference itself is a single track series of presentations in
&lt;br&gt;&amp;nbsp; &amp;nbsp;a lecture theater environment. The presentations offer speakers
&lt;br&gt;&amp;nbsp; &amp;nbsp;the opportunity to showcase on-going research and collaborate with
&lt;br&gt;&amp;nbsp; &amp;nbsp;peers while educating and highlighting advancements in security
&lt;br&gt;&amp;nbsp; &amp;nbsp;products and techniques. The focus is on innovation, tutorials,
&lt;br&gt;&amp;nbsp; &amp;nbsp;and education instead of product pitches. Some commercial content
&lt;br&gt;&amp;nbsp; &amp;nbsp;is tolerated, but it needs to be backed up by a technical
&lt;br&gt;&amp;nbsp; &amp;nbsp;presenter - either giving a valuable tutorial and best practices
&lt;br&gt;&amp;nbsp; &amp;nbsp;instruction or detailing significant new technology in the
&lt;br&gt;&amp;nbsp; &amp;nbsp;products.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;Paper proposals should consist of the following information:
&lt;br&gt;&amp;nbsp; &amp;nbsp; 1. Presenter, and geographical location (country of
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;origin/passport) and contact info (e-mail, postal address,
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;phone, fax).
&lt;br&gt;&amp;nbsp; &amp;nbsp; 2. Employer and/or affiliations.
&lt;br&gt;&amp;nbsp; &amp;nbsp; 3. Brief biography, list of publications and papers.
&lt;br&gt;&amp;nbsp; &amp;nbsp; 4. Any significant presentation and educational
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;experience/background.
&lt;br&gt;&amp;nbsp; &amp;nbsp; 5. Topic synopsis, Proposed paper title, and a one paragraph
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;description.
&lt;br&gt;&amp;nbsp; &amp;nbsp; 6. Reason why this material is innovative or significant or an
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;important tutorial.
&lt;br&gt;&amp;nbsp; &amp;nbsp; 7. Optionally, any samples of prepared material or outlines
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ready.
&lt;br&gt;&amp;nbsp; &amp;nbsp; 8. Will you have full text available or only slides?
&lt;br&gt;&amp;nbsp; &amp;nbsp; 9. Please list any other publications or conferences where this
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;material has been or will be published/submitted.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;Please include the plain text version of this information in your
&lt;br&gt;&amp;nbsp; &amp;nbsp;email as well as any file, pdf, odt, docx, ppt, or html attachments.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;Please forward the above information to &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13684929&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;_secwest08_@...&lt;/a&gt; 
&lt;br&gt;&amp;nbsp; &amp;nbsp;(remove _'s) to be considered for placement on the speaker
&lt;br&gt;&amp;nbsp; &amp;nbsp;roster, or have your lightning talk scheduled.
&lt;br&gt;&lt;br&gt;You can find more information at:
&lt;br&gt;&lt;a href=&quot;http://pacsec.jp&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://pacsec.jp&lt;/a&gt;&amp;nbsp;and &lt;a href=&quot;http://cansecwest.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://cansecwest.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;The Vancouver Dojos will be held on March 24/25 and will
&lt;br&gt;be announced shortly.
&lt;br&gt;&lt;br&gt;cheers.
&lt;br&gt;--dr
&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;World Security Pros. Cutting Edge Training, Tools, and Techniques
&lt;br&gt;Tokyo, Japan &amp;nbsp; &amp;nbsp;November 29/30 - 2007 &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://pacsec.jp&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://pacsec.jp&lt;/a&gt;&lt;br&gt;pgpkey &lt;a href=&quot;http://dragos.com/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://dragos.com/&lt;/a&gt;&amp;nbsp;kyxpgp
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/CanSecWest-2008-CFP-%28deadline-Nov-30%2C-conf-Mar-26-28%29-and-PacSec-Dojo%27s-tp13684929p13684929.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13684809</id>
	<title>Log in as administrator with live data collection CD?</title>
	<published>2007-11-07T05:41:08Z</published>
	<updated>2007-11-07T05:41:08Z</updated>
	<author>
		<name>Matthew Webster-2</name>
	</author>
	<content type="html">Hello,
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; I am almost finished creating a live data collection forensic CD, but I've noticed it is slow (20 minutes when it should be 3-5 minutes) when running on computers that are not logged in as administrator. &amp;nbsp;I could use PSexec or runas or something to log in as administrator, but I have a concern that this may alter important information &amp;nbsp;on the computer. &amp;nbsp;The question I have is, what is the best policy when creating a forensic boot disk? &amp;nbsp;Is it best to wait for the information or have the CD log in as local administrator to collect information in a timely fashion before shutting down? &amp;nbsp;I do have the local admin password so that is not an issue. &amp;nbsp;I am talking about windows boxes.
&lt;br&gt;&lt;br&gt;Thanks,
&lt;br&gt;&lt;br&gt;Matt
&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Log-in-as-administrator-with-live-data-collection-CD--tp13684809p13684809.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13684830</id>
	<title>CFP: 2008 ADFSL Conference on Digital Forensics, Security and Law</title>
	<published>2007-11-06T18:06:37Z</published>
	<updated>2007-11-06T18:06:37Z</updated>
	<author>
		<name>Glenn Dardick</name>
	</author>
	<content type="html">=======================================================================
&lt;br&gt;* * * &amp;nbsp;C A L L &amp;nbsp; F O R &amp;nbsp; P A P E R S &amp;nbsp; A N D &amp;nbsp; P R O P O S A L S &amp;nbsp;* * *
&lt;br&gt;=======================================================================
&lt;br&gt;Dear colleagues: 
&lt;br&gt;&lt;br&gt;The ADFSL 2008 Conference on Digital Forensics, Security and Law will be
&lt;br&gt;held in Oklahoma City, Oklahoma USA on April 23-25, 2008 and is calling
&lt;br&gt;for papers and proposals in, or related to, the following areas.
&lt;br&gt;&lt;br&gt;CURRICULUM	
&lt;br&gt;1) &amp;nbsp;Digital forensics curriculum	
&lt;br&gt;2) &amp;nbsp;Cyber law curriculum	
&lt;br&gt;3) &amp;nbsp;Information assurance curriculum	
&lt;br&gt;4) &amp;nbsp;Accounting digital forensics curriculum	
&lt;br&gt;&lt;br&gt;TEACHING METHODS	
&lt;br&gt;5) &amp;nbsp;Digital forensics teaching methods	
&lt;br&gt;6) &amp;nbsp;Cyber law teaching methods	
&lt;br&gt;7) &amp;nbsp;Information assurance teaching methods	
&lt;br&gt;8) &amp;nbsp;Accounting digital forensics teaching methods	
&lt;br&gt;&lt;br&gt;CASES	
&lt;br&gt;9) &amp;nbsp;Digital forensics case studies	
&lt;br&gt;10) Cyber law case studies	
&lt;br&gt;11) Information assurance case studies	
&lt;br&gt;12) Accounting digital forensics case studies	
&lt;br&gt;&lt;br&gt;INFORMATION TECHNOLOGY	
&lt;br&gt;13) Digital forensics and information technology	
&lt;br&gt;14) Cyber law and information technology	
&lt;br&gt;15) Information assurance and information technology	
&lt;br&gt;16) Accounting digital forensics information technology	
&lt;br&gt;&lt;br&gt;NETWORKS AND THE INTERNET	
&lt;br&gt;17) Digital forensics and the Internet	
&lt;br&gt;18) Cyber law and the Internet	
&lt;br&gt;19) Information assurance and Internet	
&lt;br&gt;20) Digital forensics accounting and the Internet	
&lt;br&gt;&lt;br&gt;ANTI-FORENSICS AND COUNTER ANTI-FORENSICS	
&lt;br&gt;21) Stegonography	
&lt;br&gt;22) Stylometrics and Author Attribution	
&lt;br&gt;23) Anonymity and Proxies 	
&lt;br&gt;24) Encryption and Decryption	
&lt;br&gt;&lt;br&gt;INTERNATIONAL ISSUES	
&lt;br&gt;25) International issues in digital forensics	
&lt;br&gt;26) International issues in cyber law	
&lt;br&gt;27) International issues in information assurance	
&lt;br&gt;28) International issues in accounting digital forensics	
&lt;br&gt;&lt;br&gt;THEORY	
&lt;br&gt;29) Theory development in digital forensics	
&lt;br&gt;30) Theory development in information security	
&lt;br&gt;31) Methodologies for digital forensic research	
&lt;br&gt;32) Analysis techniques for digital forensic and security research	
&lt;br&gt;&lt;br&gt;The deadline for submissions is midnight EST, January 15, 2008.
&lt;br&gt;Abstracts may be submitted for review. Papers whose abstracts are
&lt;br&gt;accepted pending final paper review must have the final paper submitted
&lt;br&gt;by midnight EST, March 1, 2008.
&lt;br&gt;&lt;br&gt;Submission Types
&lt;br&gt;&lt;br&gt;Short briefing papers: Such papers need not be extensive. A technology
&lt;br&gt;or a management briefing on an aspect of digital forensics, information
&lt;br&gt;assurance, and/or cyber law would be enough. Such papers will be
&lt;br&gt;presented by the author in a round table discussion format at the
&lt;br&gt;conference. Typical length would be around 1500-2000 words. 
&lt;br&gt;&lt;br&gt;Research papers: Such papers need to be extensive. Usually a research
&lt;br&gt;question or an argument is posed and subsequently conducted. Empirical
&lt;br&gt;work (quantitative or qualitative) would be necessary. Research papers
&lt;br&gt;will be presented by the authors in a regular conference session.
&lt;br&gt;Typical length would be around 5000-6000 words. All research papers will
&lt;br&gt;be considered for publication in the Journal of Digital Forensics,
&lt;br&gt;Security and Law (JDFSL). 
&lt;br&gt;&lt;br&gt;Case Studies: Case studies are typically descriptions of a given digital
&lt;br&gt;forensics situation. Names of organizations/actors can be kept anonymous
&lt;br&gt;to maintain confidentiality. Case studies will be presented by the
&lt;br&gt;authors at the conference. Typical length would be around 5000-6000
&lt;br&gt;words. All case studies will be considered for publication in the
&lt;br&gt;Journal of Digital Forensics, Security and Law (JDFSL).	
&lt;br&gt;&lt;br&gt;Panels: Panels and workshop proposals are welcome. These would typically
&lt;br&gt;be around 1000 words long and cover a current technology or a
&lt;br&gt;controversial issue. 	
&lt;br&gt;&lt;br&gt;The primary audience will include individuals who are interested in
&lt;br&gt;developing curriculum and teaching methods as well as conducting
&lt;br&gt;research related to the areas of digital forensics, security and law.
&lt;br&gt;This conference will be of value to both academic and practitioner
&lt;br&gt;audiences. 	
&lt;br&gt;All submissions are double blind peer reviewed.	
&lt;br&gt;&lt;br&gt;ADDITIONAL INFORMATION FOR THE CONFERENCE IS AT:	
&lt;br&gt;&lt;a href=&quot;http://www.digitalforensics-conference.org&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.digitalforensics-conference.org&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;REGISTRATION INFORMATION IS AT:	
&lt;br&gt;&lt;a href=&quot;http://www.digitalforensics-conference.org/registration.htm&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.digitalforensics-conference.org/registration.htm&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;The Chair of the conference is Dr. David P. Biros.	
&lt;br&gt;Dr. Biros may be reached via email at &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13684830&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;david.biros@...&lt;/a&gt;	
&lt;br&gt;&lt;br&gt;Association for Digital Forensics, Security and Law	
&lt;br&gt;Website: &lt;a href=&quot;http://www.adfsl.org&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.adfsl.org&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;Journal of Digital Forensics, Security and Law	
&lt;br&gt;Website: &lt;a href=&quot;http://www.jdfsl.org&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.jdfsl.org&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/CFP%3A-2008-ADFSL-Conference-on-Digital-Forensics%2C-Security-and-Law-tp13684830p13684830.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-13685309</id>
	<title>Call For Papers - DFRWS 2008</title>
	<published>2007-11-06T04:38:35Z</published>
	<updated>2007-11-06T04:38:35Z</updated>
	<author>
		<name>Baker, Dave</name>
	</author>
	<content type="html">&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Call for Papers
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; The 8th Annual DFRWS Conference (DFRWS 2008)
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; August 11-13, 2007 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Baltimore, MD, USA 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;www.dfrws.org 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; dfrws2008 &amp;lt;at&amp;gt; dfrws &amp;lt;dot&amp;gt; org
&lt;br&gt;&amp;nbsp;
&lt;br&gt;DFRWS brings together leading researchers, developers, practitioners,
&lt;br&gt;and educators interested in advancing the state of the art in digital
&lt;br&gt;forensics from around the world. As the most established venue in
&lt;br&gt;the field, DFRWS is the preferred place to present both cutting-
&lt;br&gt;edge research and perspectives on best practices for all aspects
&lt;br&gt;of digital forensics. As an independent organization, we promote
&lt;br&gt;open community discussions and disseminate the results of our work
&lt;br&gt;to the widest audience.
&lt;br&gt;&amp;nbsp;
&lt;br&gt;We invite original contributions as research papers, panel proposals,
&lt;br&gt;Work-in-Progress talks, and demo proposals. All papers are evaluated
&lt;br&gt;through a double-blind peer-review process, and those accepted will
&lt;br&gt;be published in printed proceedings by Elsevier.
&lt;br&gt;&amp;nbsp;
&lt;br&gt;Topics of Interest
&lt;br&gt;------------------
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Incident response and live analysis 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Network-based forensics, including &amp;nbsp;network traffic analysis,
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; traceback and attribution
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Event reconstruction methods and tools 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; File system and memory analysis 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Application analysis 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Embedded systems 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Small scale and mobile devices 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Large-scale investigations 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Digital evidence storage and preservation
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Data mining and information discovery
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Data hiding and recovery 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; File extraction from data blocks (&amp;quot;file carving&amp;quot;)
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Multimedia analysis 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Tool testing and development 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Digital evidence and the law 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Anti-forensics and anti-anti-forensics
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Case studies and trend reports 
&lt;br&gt;* &amp;nbsp; &amp;nbsp; &amp;nbsp; Non-traditional approaches to forensic analysis 
&lt;br&gt;&lt;br&gt;The above list is only suggestive. We welcome new, original ideas
&lt;br&gt;from people in academia, industry, government, and law enforcement
&lt;br&gt;who are interested in sharing their results, knowledge, and experience.
&lt;br&gt;Authors are encouraged to demonstrate the applicability of their
&lt;br&gt;work to practical issues. &amp;nbsp;Questions about submission topics can
&lt;br&gt;be sent via email to: dfrws2008 &amp;lt;at&amp;gt; dfrws &amp;lt;dot&amp;gt; org.
&lt;br&gt;&amp;nbsp;
&lt;br&gt;Important Dates
&lt;br&gt;---------------
&lt;br&gt;Submission deadline: &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;March 17, 2008
&lt;br&gt;Author notification &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; April 28, 2008
&lt;br&gt;Final drafts due &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;May 12, 2008
&lt;br&gt;&lt;br&gt;Publication Criteria 
&lt;br&gt;--------------------
&lt;br&gt;Research papers must be original contributions, not substantially
&lt;br&gt;duplicate previous work, and must not be under simultaneous publication
&lt;br&gt;review elsewhere. The review process will be &amp;quot;double-blind&amp;quot; (the
&lt;br&gt;reviewers will not know who the authors are, and the authors will
&lt;br&gt;not know who the reviewers are). Therefore, the version submitted
&lt;br&gt;for review should not contain the names or affiliations of the
&lt;br&gt;authors. When referring to their own previous work, authors should
&lt;br&gt;use the third person instead of the first person (i.e. &amp;quot;Smith and
&lt;br&gt;Jones [2] previously determined...&amp;quot; instead of &amp;quot;We [2] previously
&lt;br&gt;determined..&amp;quot;). Authors are expected to present their work in person
&lt;br&gt;at the workshop and must have at least one registration per paper
&lt;br&gt;in order to be included in the proceedings.
&lt;br&gt;&lt;br&gt;Papers must be written in English and should not exceed 10
&lt;br&gt;single-spaced, two-column pages with 1 inch margins and 10pt font.
&lt;br&gt;Authors will be given 30 minutes to present their paper.
&lt;br&gt;&lt;br&gt;Panel proposals should be one to three pages and clearly describe
&lt;br&gt;the topic, its relevance and a list of potential panelists and their
&lt;br&gt;biographies. &amp;nbsp;Panels will be evaluated based on the topic relevance
&lt;br&gt;and diversity of the panelists.
&lt;br&gt;&lt;br&gt;Proposals for demonstrations of proof of concept and research-based
&lt;br&gt;tools are also welcome. Proposals should describe the tool, its
&lt;br&gt;relevance to the forensics field and space/equipment needs (e.g.,
&lt;br&gt;power, networking, etc.) and be submitted.
&lt;br&gt;&lt;br&gt;Submission instructions for papers, panels, demos, and WiPs (work
&lt;br&gt;in progress session) will be posted at the DFRWS web site at
&lt;br&gt;&lt;a href=&quot;http://www.dfrws.org/2008/cfp.shtml&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.dfrws.org/2008/cfp.shtml&lt;/a&gt;.
&lt;br&gt;&lt;br&gt;Student scholarship program 
&lt;br&gt;---------------------------
&lt;br&gt;A limited number of scholarships may be awarded to students presenting
&lt;br&gt;a paper at the conference. The intent is to help alleviate the
&lt;br&gt;financial burden due to the cost of hotel expenses and conference
&lt;br&gt;registration. Full details will be posted at the DFRWS website
&lt;br&gt;&lt;a href=&quot;http://www.dfrws.org/2008/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.dfrws.org/2008/&lt;/a&gt;.
&lt;br&gt;&amp;nbsp;
&lt;br&gt;Organizing Committee 
&lt;br&gt;--------------------
&lt;br&gt;Conference Chair: &amp;nbsp; &amp;nbsp; Brian Carrier (Basis Technology) 
&lt;br&gt;Technical Program: &amp;nbsp; &amp;nbsp;Frank Adelstein (ATC-NY) 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Wietse Venema (IBM) 
&lt;br&gt;Local Arrangements: &amp;nbsp; Eoghan Casey (Stroz Friedberg)
&lt;br&gt;Proceedings: &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Vassil Roussev (University of New Orleans) 
&lt;br&gt;Publicity/Sponsors: &amp;nbsp; Daryl Pfeif (Digital Forensics Solutions) &amp;nbsp;
&lt;br&gt;Keynote: &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Golden Richard (University of New Orleans)
&lt;br&gt;Finances: &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Rick Smith (ATC-NY)
&lt;br&gt;Forensic Challenge: &amp;nbsp; Matthew Geiger (CERT)
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Marcus Rogers (Purdue University)
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Dave Baker (Mitre) &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Todd Shipley
&lt;br&gt;&lt;br&gt;&amp;nbsp;--------------------------------------------------------------------
&lt;br&gt;&amp;nbsp;David W. Baker &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=13685309&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;bakerd@...&lt;/a&gt;
&lt;br&gt;&amp;nbsp;Associate Department Head
&lt;br&gt;&amp;nbsp;G025 - Secure Operations &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;(703) 983-3658
&lt;br&gt;&amp;nbsp;The MITRE Corporation &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (703) 983-1002 (F)
&lt;br&gt;&amp;nbsp;Mailstop T240 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (877) 682-0632 (P)
&lt;br&gt;&amp;nbsp;7515 Colshire Drive &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; McLean, VA, 22102
&lt;br&gt;&amp;nbsp;--------------------------------------------------------------------
&lt;br&gt;&lt;br /&gt; &lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;smime.p7s&lt;/strong&gt; (4K) &lt;a href=&quot;http://old.nabble.com/attachment/13685309/0/smime.p7s&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Call-For-Papers---DFRWS-2008-tp13685309p13685309.html" />
</entry>

</feed>
