Log2timeline and timezone issue

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Any log2timeline command without specifying timezone; i.e.:

log2timeline -f mft -p -r /media/forensics > newbodyfile.txt

2.  Run l2t_process -b newbodyfile.txt 09-14-2012

Error while getting the offset from UTC to the timezone MDT.
Error message: Invalid offset: MDT

3.

What is the expected output? What do you see instead?
I don't expect to see this error..it seems like log2timeline doesn't understand 
MDT

What version of the product are you using? On what operating system?
log2timeline version 0.64 on Ubuntu Linux 12.04.1

Please provide any additional information below.
Head of the newbodyfile.txt:

11/24/2011,10:21:47,MDT,MACB,FILE,NTFS $MFT,$SI [MACB] 
time,-,MBP,/$MFT,/$MFT,2,/$MFT,0, ,Log2t::input::mft,-

Original issue reported on code.google.com by digital...@gmail.com on 14 Sep 2012 at 5:13

[GoogleCodeExporter]

I'm marking this as not going to be fixed, since the current status of the 
l2t_process is depracation.

That tool is being replaced by the newer l2t_process.py in which this is not a 
problem,

The issue here is that log2timeline without -z uses the local timezone, and the 
short name for some reasons is inconsistent, that is the short names for some 
timezones is not recognized by DateTime library (that produces the short names).

However, this is not an issue in the latest l2t_process.py - hence marked as 
"WontFix"

Original comment by ki...@kiddaland.net on 14 Sep 2012 at 9:33

• Changed state: WontFix