Difference between revisions of "Fls"

From SleuthKitWiki
Jump to: navigation, search
m (Reformatted)
(Undo revision 11347 by Domtheo (talk))
 
(39 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
==mmls==
+
Back to [[Help Documents]]
−
Version 2.09
+
  
−
===Purpose===
 
−
Lists the files and directory names in the image  and  can  display file  names of recently deleted files for the directory using the given inode.  If the inode argument is not given, 2 is used.
 
  
−
Once  the  inode  has  been determined, the file can be recovered using
+
fls lists the files and directory names in a file system.  It will process the contents of a given directory and can display information on deleted files.  
−
icat(1) from The Coroners Toolkit.  The amount of information recovered
+
−
from deleted file entries varies depending on the system.  For example,
+
−
on Linux, a recently deleted file can be  easily  recovered,  while  in
+
−
Solaris not even the inode can be determined.  If you just want to find
+
−
what file name belongs to an inode, it is easier to use find_name(1).
+
  
−
===Usage===
+
* [http://www.sleuthkit.org/sleuthkit/man/fls.html Automatically Updated man Page]
−
fls [-adDFlpruvV]  [-m mnt ] [-z zone ] [-f fstype ] [-s seconds ] [-i imgtype ] [-o imgoffset ] image [images] [ inode ]
+
  
−
===Options===
+
==Output Data==
 +
The default output (i.e. if -l or -m are not given) has one line for each file in the directory.  An NTFS example is:
  
−
{| border="1" cellpadding="5"
+
<code>
−
!Switch
+
r/r 1304-128-1: IO.SYS
−
!Purpose
+
</code>
−
|-
+
−
| -a || Display the "." and ".." directory entries (by default it does not)
+
−
|-
+
−
| -d || Display deleted entries only
+
−
|-
+
−
| -D || Display directory entries only
+
−
|-
+
−
| -f fstype || The type of File System.  Use the -? argument for a list of supported types.  If not given, the default type for  the  platform is used.
+
−
|-
+
−
| -F || Display file (all non-directory) entries only.
+
−
|-
+
−
| -l || Display file details in long format.  The following contents are displayed: file_type inode file_name mod_time acc_time cre_time size  uid gid
+
−
|-
+
−
| -m mnt || Display  files in time machine format.  The output can be merged with the body file from grave-robber(1)  before  mactime(1) is run.  The files will be printed as though the image was mounted at mnt (for example /usr).
+
−
|-
+
−
| -p || Display the full path for each entry.  By default it denotes the directory depth on recursive runs with a ’+’ sign.
+
−
|-
+
−
| -r || Recursively  display  directories.  This will not follow deleted directories, because it can’t.
+
−
|-
+
−
| -s seconds || The time skew of the original system in seconds.  For  example, if the original system was 100 seconds slow, this value would be -100.  This is only used if -l or -m are given.
+
−
|-
+
−
| -i imgtype || Identify the type of image file, such as raw or split.  Raw is the default.
+
−
|-
+
−
| -o imgoffset || The  sector  offset  where  the file system starts in the image. Non-512 byte sectors can be specified using ’@’ (32@2048).
+
−
|-
+
−
| -u || Display undeleted entries only
+
−
|-
+
−
| -v || Verbose output to stderr.
+
−
|-
+
−
| -V || Display version.
+
−
|-
+
−
| -z zone || The ASCII string of the time zone of the original  system.  For example,  EST  or  GMT.  These  strings must be defined by your operating system and may vary.
+
−
|-
+
−
| image [images] || One (or more if split) disk or partition images whose format is given with ’-i’.
+
−
|}
+
  
−
===Example===
+
=== File Type ===
−
To list the partition table of a Windows system using autodetect:
+
The <tt>r/r</tt> value shows the file type.  The first 'r' is the type as saved in the file's [[file name  structure]] and the second 'r' is the type as saved in the file's [[metadata structure]]. For [[allocated files]], these should always be equal.  For [[deleted files]], they could be different if one of the structures was reallocated to a different file type. The types are listed here:
−
To get a list of all files and directories in an image use:
+
* -: Unknown type
−
# fls -r image 2
+
* r: Regular file
−
or just:
+
* d: Directory
−
  # fls -r image
+
* c: Character device
 +
* b: Block device
 +
* l: Symbolic link
 +
* p: Named FIFO
 +
* s: Shadow
 +
* h: Socket
 +
* w: Whiteout
 +
* v: TSK Virtual file / directory (not a real directory, created by TSK for convenience).
 +
Most entries will be 'r' and 'd'. The others are Unix-focused.
  
−
To get the full path of deleted files in a given directory:
+
=== Metadata Address ===
−
  # fls -d -p image 29
+
The <tt>1304-128-1</tt> part of the entry shows the [[Metadata Address]] associated with this name. Because this is an NTFS example, the <tt>-128-1</tt> part exists, which identifies the $Data attribute that this name points to.  Other file systems may have a single number in this field.
  
−
To get the mactime output do:
+
=== File Name ===
−
# fls -m /usr/local image 2
+
Finally, the <tt>IO.SYS</tt> part of the entry is the name of the file for this entry.
  
−
If you have a disk image and the file system starts in sector 63, use:
+
If you use the '-r' option to recursively go into directories, a '+' is added to the front of each entry to show how deep the file is. '++' means that the entry is two directories deep.
−
  # fls -o 63 disk-img.dd
+
  
−
If you have a disk image that is split use:
+
=== Deleted File Names ===
−
  # fls -i "split" -o 63 disk-1.dd disk-2.dd disk-3.dd
+
If the file name in unallocated space of the directory, there will be a '*' between the file type and the metadata address.  
  
−
===History===
+
<code>
−
fls first appeared in TCTUTILs v1.0.
+
r/r * 1304-128-1: IO.SYS
 +
</code>
  
−
===Author===
+
In general, this means that the file is deleted.  But, some file systems keep the directory contents sorted and will move file names around.  This can result in unallocated copies of the file name, even when the file is still allocated.  As of version 3.0.0, TSK suppresses duplicate file names and will suppress a deleted version of a name if an equivalent allocated version exists (equivalent is defined as the same name and pointing to the same metadata address). 
−
Brian Carrier <carrier@sleuthkit.org>
+
 
 +
Sometimes, you will see the text '(realloc)' after the metadata address. 
 +
 
 +
<code>
 +
r/r * 1304-128-1(realloc): IO.SYS
 +
</code>
 +
 
 +
This occurs when the file name is in an unallocated state and the metadata structure is in an allocated state. This can only occur on file systems that separate the file name from the metadata (such as NTFS, Ext2/3, UFS, etc.). Seeing '(realloc)' with versions of TSK 3.0.0 and greater (because of the duplicate name suppression) is generally an indication that the metadata structure has been reallocated to a new file and therefore not likely to be the metadta or file content that originally corresponded to this file name. 
 +
 
 +
=== -l format ===
 +
The '-l' argument causes the "long" format with more details. It is tab-delimited with the following fields:
 +
* file type as reported in file name and metadata structure (see above)
 +
* [[Metadata Address]]
 +
* name
 +
* mtime (last modified time)
 +
* atime (last accessed time)
 +
* ctime (last changed time)
 +
* crtime (created time)
 +
* size (in bytes)
 +
* uid (User ID)
 +
* gid (Group ID)
 +
 
 +
Note that the 2.X versions of TSK do not print the created time.
 +
 
 +
=== -m format ===
 +
The '-m' argument causes the data to be in the [[body file]] format. It is used to make [[timelines]]. An example:
 +
 
 +
# fls -r -m / image.dd > body.txt

Latest revision as of 09:10, 13 January 2014

Back to Help Documents


fls lists the files and directory names in a file system. It will process the contents of a given directory and can display information on deleted files.

Output Data

The default output (i.e. if -l or -m are not given) has one line for each file in the directory. An NTFS example is:

r/r 1304-128-1: IO.SYS

File Type

The r/r value shows the file type. The first 'r' is the type as saved in the file's file name structure and the second 'r' is the type as saved in the file's metadata structure. For allocated files, these should always be equal. For deleted files, they could be different if one of the structures was reallocated to a different file type. The types are listed here:

  • -: Unknown type
  • r: Regular file
  • d: Directory
  • c: Character device
  • b: Block device
  • l: Symbolic link
  • p: Named FIFO
  • s: Shadow
  • h: Socket
  • w: Whiteout
  • v: TSK Virtual file / directory (not a real directory, created by TSK for convenience).

Most entries will be 'r' and 'd'. The others are Unix-focused.

Metadata Address

The 1304-128-1 part of the entry shows the Metadata Address associated with this name. Because this is an NTFS example, the -128-1 part exists, which identifies the $Data attribute that this name points to. Other file systems may have a single number in this field.

File Name

Finally, the IO.SYS part of the entry is the name of the file for this entry.

If you use the '-r' option to recursively go into directories, a '+' is added to the front of each entry to show how deep the file is. '++' means that the entry is two directories deep.

Deleted File Names

If the file name in unallocated space of the directory, there will be a '*' between the file type and the metadata address.

r/r * 1304-128-1: IO.SYS

In general, this means that the file is deleted. But, some file systems keep the directory contents sorted and will move file names around. This can result in unallocated copies of the file name, even when the file is still allocated. As of version 3.0.0, TSK suppresses duplicate file names and will suppress a deleted version of a name if an equivalent allocated version exists (equivalent is defined as the same name and pointing to the same metadata address).

Sometimes, you will see the text '(realloc)' after the metadata address.

r/r * 1304-128-1(realloc): IO.SYS

This occurs when the file name is in an unallocated state and the metadata structure is in an allocated state. This can only occur on file systems that separate the file name from the metadata (such as NTFS, Ext2/3, UFS, etc.). Seeing '(realloc)' with versions of TSK 3.0.0 and greater (because of the duplicate name suppression) is generally an indication that the metadata structure has been reallocated to a new file and therefore not likely to be the metadta or file content that originally corresponded to this file name.

-l format

The '-l' argument causes the "long" format with more details. It is tab-delimited with the following fields:

  • file type as reported in file name and metadata structure (see above)
  • Metadata Address
  • name
  • mtime (last modified time)
  • atime (last accessed time)
  • ctime (last changed time)
  • crtime (created time)
  • size (in bytes)
  • uid (User ID)
  • gid (Group ID)

Note that the 2.X versions of TSK do not print the created time.

-m format

The '-m' argument causes the data to be in the body file format. It is used to make timelines. An example: 

# fls -r -m / image.dd > body.txt
Retrieved from "https://wiki.sleuthkit.org/index.php?title=Fls&oldid=11362"