Forensic Live CD issues - Revision history

.FUF: /* Journaling file system updates */

2012-10-07T09:28:40Z

‎Journaling file system updates

2012-07-28T13:40:47Z

2012-07-28T13:37:49Z

moved Forensic Linux Live CD issues to Forensic Live CD issues: No need for this article to be Linux specific.

2012-07-28T13:36:49Z

2011-12-25T19:44:20Z

‎Problems: Removed first sentence (was re-statement explaining what a Live CD is and can be used for).

2010-06-06T16:48:07Z

‎The problem: Typo error: "not exception" -> no exception.

2010-05-22T12:12:37Z

‎Swap space activation

2010-05-22T12:01:49Z

‎Incorrect write-blocking approach

2010-05-22T11:50:30Z

‎Incorrect mount policy

2010-05-22T11:48:46Z

‎Root file system spoofing

@@ Line 66: / Line 66: @@
   |  SPADA
   |  4
   |}

@@ Line 1: / Line 1: @@
 == The problem ==
-[[Tools#Forensics_Live_CDs | Forensic Linux Live CD distributions]] are widely used during computer forensic investigations. Currently, many vendors of such Live CD distributions spread false claims that their distributions "do not touch anything", "write protect everything" and so on. Community-developed distributions are no exception here, unfortunately. Finally, it turns out that many forensic Linux Live CD distributions are not tested properly and there are no suitable test cases developed.
+[[Live CD|Forensic Live CDs]] are widely used during computer forensic investigations. Currently, many vendors of such Live CD distributions spread false claims that their distributions "do not touch anything", "write protect everything" and so on. Unfortunately, community-developed distributions are no exception here. Finally, it turns out that many Linux-based forensic Live CDs are not tested properly and there are no suitable test cases published.
 == Another side of the problem ==
-Another side of the problem of insufficient testing of forensic Live CD distributions is that many users do not know what happens "under the hood" of such distributions and cannot adequately test them.
+Another side of the problem of insufficient testing of forensic Live CDs is that many users do not know what happens "under the hood" of the provided operating system and cannot adequately test them.
 === Example ===

← Older revision		Revision as of 13:36, 28 July 2012
Line 130:		Line 130:
	* [http://www.computer-forensics-lab.org/pdf/Linux_for_computer_forensic_investigators_2.pdf Linux for computer forensic investigators: problems of booting trusted operating system]		* [http://www.computer-forensics-lab.org/pdf/Linux_for_computer_forensic_investigators_2.pdf Linux for computer forensic investigators: problems of booting trusted operating system]
	* [http://www.computer-forensics-lab.org/pdf/Linux_for_computer_forensic_investigators.pdf Linux for computer forensic investigators: «pitfalls» of mounting file systems]		* [http://www.computer-forensics-lab.org/pdf/Linux_for_computer_forensic_investigators.pdf Linux for computer forensic investigators: «pitfalls» of mounting file systems]
		+
		+	[[Category:Live CD]]

@@ Line 15: / Line 15: @@
 == Problems ==
-Here is a list of common problems of forensic Linux Live CD distributions that can be used by developers and users for testing purposes. Each problem is followed by an up to date list of distributions affected.
+Each problem is followed by an up to date list of distributions affected.
 === Journaling file system updates ===

@@ Line 1: / Line 1: @@
 == The problem ==
-[[Tools#Forensics_Live_CDs | Forensic Linux Live CD distributions]] are widely used during computer forensic investigations. Currently, many vendors of such Live CD distributions spread false claims that their distributions "do not touch anything", "write protect everything" and so on. Community-developed distributions are not exception here, unfortunately. Finally, it turns out that many forensic Linux Live CD distributions are not tested properly and there are no suitable test cases developed.
+[[Tools#Forensics_Live_CDs | Forensic Linux Live CD distributions]] are widely used during computer forensic investigations. Currently, many vendors of such Live CD distributions spread false claims that their distributions "do not touch anything", "write protect everything" and so on. Community-developed distributions are no exception here, unfortunately. Finally, it turns out that many forensic Linux Live CD distributions are not tested properly and there are no suitable test cases developed.
 == Another side of the problem ==

@@ Line 114: / Line 114: @@
 === Swap space activation ===
-''Feel free to add information about swap space activation during the boot on some distributions''
+''Feel free to add information about swap space activation during the boot in some distributions''
 === Incorrect mount policy ===

← Older revision		Revision as of 12:01, 22 May 2010
Line 123:		Line 123:

	=== Incorrect write-blocking approach ===		=== Incorrect write-blocking approach ===
		+
		+	Some forensic Linux Live CD distributions rely on [[hdparm]] and [[blockdev]] programs to mount file systems in read-only mode (by setting the underlying block device to read-only mode). Unfortunately, setting the block device to read-only mode does not guarantee that [http://archives.free.net.ph/message/20090721.105120.99250e3f.en.html no write commands will be passed to the drive].

	== External links ==		== External links ==

← Older revision		Revision as of 11:50, 22 May 2010
Line 117:		Line 117:

	=== Incorrect mount policy ===		=== Incorrect mount policy ===
−
−	~~==== HAL ====~~

	==== rebuildfstab and scanpartitions scripts ====		==== rebuildfstab and scanpartitions scripts ====

@@ Line 76: / Line 76: @@
 Currently, Casper may select fake root file system image on evidentiary media (e.g. [[Hard Drive|HDD]]), because there are no authenticity checks performed (except optional UUID check for a possible live file system), and this fake root file system image may be used to execute malicious code during the boot with root privileges. Knoppix-based forensic Live CD distributions are vulnerable to the same attack.
-List of Ubuntu-based and Debian-based distributions that allow root file system spoofing:
+List of Ubuntu-based distributions that allow root file system spoofing:
 {| class="wikitable" border="1"