Difference between pages "File Carving" and "File Format Identification"
From Forensics Wiki
(Difference between pages)
Joachim Metz (Talk | contribs) m (→FIle Carving Taxonomy) |
m (→Bibliography) |
||
| Line 1: | Line 1: | ||
| − | + | File Format Identification is the process of figuring out the format of a sequence of bytes. Operating systems typically do this by file extension or by embedded MIME information. Forensic applications need to identify file types by content. | |
| + | =Tools= | ||
| + | ==libmagic== | ||
| + | * Written in C. | ||
| + | * Rules in /usr/share/file/magic and compiled at runtime. | ||
| + | * Powers the Unix “file” command, but you can also call the library directly from a C program. | ||
| + | * http://sourceforge.net/projects/libmagic | ||
| − | = | + | ==DROID== |
| + | * Writen in Java | ||
| + | * Developed by National Archives of the United Kingdom. | ||
| + | * http://droid.sourceforge.net | ||
| − | + | ==TrID== | |
| + | * XML config file | ||
| + | * Closed source; free for non-commercial use | ||
| + | * http://mark0.net/soft-trid-e.html | ||
| − | + | ==Stellent/Oracle Outside-In== | |
| + | * Proprietary but free demo. | ||
| + | * http://www.oracle.com/technology/products/content-management/oit/oit_all.html | ||
| − | + | [[Category:Tools]] | |
| − | + | =Bibliography= | |
| + | Current research papers on the file format identification problem. Most of these papers concern themselves with identifying file format of a few file sectors, rather than an entire file. | ||
| − | + | ; [http://www.dfrws.org/2008/proceedings/p14-calhoun.pdf Predicting the Types of File Fragments], William Calhoun, Drue Coles, DFRWS 2008 [http://www.dfrws.org/2008/proceedings/p14-calhoun_pres.pdf [slides]] | |
| − | + | ; Karresand Martin, Shahmehri Nahid. File type identification of data fragments by their binary structure. In: | |
| − | [[ | + | Proceedings of the IEEE workshop on information assurance; 2006b. p. 140–7. [http://www.itoc.usma.edu/workshop/2006/Program/Presentations/IAW2006-07-3.pdf [slides]] |
| − | + | [[Category:Bibliography]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | [ | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 22:11, 19 October 2008
File Format Identification is the process of figuring out the format of a sequence of bytes. Operating systems typically do this by file extension or by embedded MIME information. Forensic applications need to identify file types by content.
Contents |
Tools
libmagic
- Written in C.
- Rules in /usr/share/file/magic and compiled at runtime.
- Powers the Unix “file” command, but you can also call the library directly from a C program.
- http://sourceforge.net/projects/libmagic
DROID
- Writen in Java
- Developed by National Archives of the United Kingdom.
- http://droid.sourceforge.net
TrID
- XML config file
- Closed source; free for non-commercial use
- http://mark0.net/soft-trid-e.html
Stellent/Oracle Outside-In
- Proprietary but free demo.
- http://www.oracle.com/technology/products/content-management/oit/oit_all.html
Bibliography
Current research papers on the file format identification problem. Most of these papers concern themselves with identifying file format of a few file sectors, rather than an entire file.
- Predicting the Types of File Fragments, William Calhoun, Drue Coles, DFRWS 2008 [slides]
- Karresand Martin, Shahmehri Nahid. File type identification of data fragments by their binary structure. In
Proceedings of the IEEE workshop on information assurance; 2006b. p. 140–7. [slides]