Release 2018-01-17
Jump to navigation
Jump to search
Truxton 2.1.15.0
Improvements
- USB Vendor and Product names added to timeline events
- Added volume paths to prefetch file details
- Unix password files are now expanded
- Outlook for Mac messages are now expanded
- When exporting files from Truxton, the timestamps of the files are now set to the times in Truxton (and from the original media) instead of the current time.
- A new report of "File Type Breakdown" was added
- We now parse the latest version of XRY XML reports
- Unidentified files report modified to show Normal files only.
- Samsung Smart Switch backups are now expanded
- New Android MMS/SMS database is now expanded
New File Types
- Samba Database
- Unix etc password
- Unix password shadow
- Outlook Mac Message (OLK)
- Outlook Mac Attachment
- OpenGL Texture
- Unity Shader Cache
- Disney Application Database
- Disney Itinerary Database
- Evite Database
- Android Media Database
- Android Calendar Database
- Beartooth Database
- Packman Texture
- Asurion Database
- Kochava Database
- Android Partner Database
- Samsung Smart Switch Database
- CSC Database
- Weather Widger Database
- Smart Bonding Service Database
- Android Hyphen Data
- Quram Image
- Android Sprite
- Android PIO Image
- Western Digital MyCloud Database
- Verizon FIOS Database
- Samsung Radio Database
- Rush Limbaugh Database
- LinkedIn Database
- QNAP Photo Database
- TopGolf Database
- Android Hotspot
- Weather Clock Database
- Android Font
Bug Fixes
- Vista/Windows 7 prefetch files weren't being parsed properly. Volume information was being missed.
- Loading a drive letter from the desktop wasn't properly escaped.
- Ordinal suffixing has been fixed in reports. You should no longer see "122th" you should see "122nd" instead.
- Media summary report now includes just the partitions that belonged to the media being loaded, not all partitions from all disk images contained in the media.
- Endless loop while parsing invalid RFC 2047 encoded text
- MIME parsing now completes when there is no body to parse
- Some URLs were being improperly parsed for search terms
- Tar files that contain files larger than 2GB are now expanded correctly.