When importing a datasource using a FAT32 (no TZ for timestamps) and selecting a timezone for the source dependent on daylight saving time (eg. CET, Europe/Zurich, Europe/Berlin) the daylight saving time is not handled correctly for the week after the daylight change (European time change -> 31 October) as if summer time was still in use.
For testing three files were created on a FAT32 partition using a Windows PC set to the 27.10("avant.txt"), 03.11("milieu.txt") and 10.11("apres.txt") manually, all around 15h30.
The image was then imported using timezone "Europe/Zurich".
As visible the file created in the current week ("milieu.txt") has been imported with a time offset of -1.
Filesystem Metadata as per X-Ways
The test dataset is provided attached as virtual disk.
test_timezones.zip
Tested on Autopsy 4.19.1
When importing a datasource using a FAT32 (no TZ for timestamps) and selecting a timezone for the source dependent on daylight saving time (eg. CET, Europe/Zurich, Europe/Berlin) the daylight saving time is not handled correctly for the week after the daylight change (European time change -> 31 October) as if summer time was still in use.
For testing three files were created on a FAT32 partition using a Windows PC set to the 27.10("avant.txt"), 03.11("milieu.txt") and 10.11("apres.txt") manually, all around 15h30.
The image was then imported using timezone "Europe/Zurich".
As visible the file created in the current week ("milieu.txt") has been imported with a time offset of -1.
Filesystem Metadata as per X-Ways
The test dataset is provided attached as virtual disk.
test_timezones.zip
Tested on Autopsy 4.19.1