Currently, only one "depth" of compressed or archived file is supported.
e.g. can read syslog stored in logs.tar. Cannot read syslog.gz in logs.tar, nor logs.tar stored in logs.tar.xz.
e.g. can read syslog stored in syslog.gz. Cannot read syslog.gz stored in syslog.gz.xz. Cannot read a the special gzip+tar file logs.tgz.
Related, only plain text files are extractable from compressed files or archived files. EVTX, Journal files, and utmp files stored as a compressed or archived file are not readable. See FileType
Solution
Refactor BlockReader reading to handle arbitrary "chains" of reads for text files and UTMPX files.
Currently, EvtxReader reads EVTX files using EvtxParser. BlockReader is not used by the EvtxReader. Processing EVTX files that are compressed or archived are outside the scope of this issue.
Problem
Currently, only one "depth" of compressed or archived file is supported. e.g. can read
syslog
stored inlogs.tar
. Cannot readsyslog.gz
inlogs.tar
, norlogs.tar
stored inlogs.tar.xz
. e.g. can readsyslog
stored insyslog.gz
. Cannot readsyslog.gz
stored insyslog.gz.xz
. Cannot read a the special gzip+tar filelogs.tgz
.Related, only plain text files are extractable from compressed files or archived files. EVTX, Journal files, and utmp files stored as a compressed or archived file are not readable. See
FileType
Solution
Refactor
BlockReader
reading to handle arbitrary "chains" of reads for text files and UTMPX files.Currently,
JournalReader
reads Journal files using libsystemd calls for reading.BlockReader
is not used by theJournalReader
. Processing Journal files that are compressed or archived are outside the scope of this issue.Currently,
EvtxReader
reads EVTX files usingEvtxParser
.BlockReader
is not used by theEvtxReader
. Processing EVTX files that are compressed or archived are outside the scope of this issue.Relates to Issue #7.