Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand

Downloads:

83

Downloads of v 2.0.0.50:

25

Last Update:

22 May 2023

Package Maintainer(s):

Software Author(s):

  • Joakim Schicht

Tags:

logfileparser logfile parser ntfs digital forensics incident response dfir

LogFileParser

  • 1
  • 2
  • 3

2.0.0.50 | Updated: 22 May 2023

Downloads:

83

Downloads of v 2.0.0.50:

25

Maintainer(s):

Software Author(s):

  • Joakim Schicht

LogFileParser 2.0.0.50

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Exemption for this package version only:

See note in description.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install LogFileParser, run the following command from the command line or from PowerShell:

>

To upgrade LogFileParser, run the following command from the command line or from PowerShell:

>

To uninstall LogFileParser, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade logfileparser -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade logfileparser -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install logfileparser
  win_chocolatey:
    name: logfileparser
    version: '2.0.0.50'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'logfileparser' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.0.0.50'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller logfileparser
{
    Name     = "logfileparser"
    Version  = "2.0.0.50"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'logfileparser':
  ensure   => '2.0.0.50',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator gep13 on 23 May 2023.

Description

Background

NTFS is designed as a recoverable filesystem. This done through logging of all transactions that alters volume structure. So any change to a file on the volume will require something to be logged to the $LogFile too, so that it can be reversed in case of system failure at any time. Therefore a lot of information is written to this file, and since it is circular, it means new transactions are overwriting older records in the file. Thus it is somewhat limited how much historical data can be retrieved from this file. Again, that would depend on the type of volume, and the size of the $LogFile. On the systemdrive of a frequently used system, you will likely only get a few hours of history, whereas an external/secondary disk with backup files on, would likely contain more historical information. And a 2MB file will contain far less history than a 256MB one. So in what size range can this file be configured to? Anything from 256 KB and up. Configure the size to 2 GB can be done like this, "chkdsk D: /L:2097152". How a large sized logfile impacts on performance is beyond the scope of this text. Setting it lower than 2048 is normally not possible. However it is possble by patching untfs.dll: http://code.google.com/p/mft2csv/wiki/Tiny_NTFS

Features

  • Decode and dump $LogFile records and transaction entries.
  • Decode NTFS attribute changes.
  • Optionally resolve all datarun list information available in $LogFile. Option: "Reconstruct data runs".
  • Recover transactions from slack space within $LogFile.
  • Choose to reconstruct missing or damaged headers of transactions found in slack. Option: "Rebuild header".
  • Optionally also finetune result with a LSN error level value. Option: "LSN error level".
  • Logs to csv and imports to sqlite database with several tables.
  • Optionally import csv output of mft2csv into db.
  • Choose among 6 different timestamp formats.
  • Choose timestamp precision: None, MilliSec and NanoSec.
  • Choose Precision separator at millisec.
  • Choose Precision separator at nanosec.
  • Choose region adjustment for timestamps. Default is to present timestamps in UTC 0.0.
  • Choose output separator. Option: "Set separator".
  • Configurable UNICODE or ANSI output. Option "Unicode".
  • Configurable MFT record size (1024 or 4096). Option "MFT record size".
  • Optionally decode individual transactions or partial transactions (fragment).
  • Option to reconstruct RCRD's from single or multiple transactions (fragments).
  • Option to configure broken $LogFile. Useful with carved RCRD's as input.
  • Option to skip fixups (for broken $LogFile, typically carved from memory).
  • Detailed verbose output into debug.log.
  • Configurable comma separated list of lsn's to trigger ultra verbose information about specific transactions into debug.log.
  • Configuration for 32-bit OS.
  • Configuration for binary data extraction of resident data updates.
  • Autogenerated sql for importing out put into MySql database.
  • Option to skip all sqlite3 stuff to speed up total parsing.
  • Optional command line mode. Supports errorlevel suitable for batch scripting.

Note on VirusTotal detections

This application is a compiled AutoIt script.
AutoIt scripts packaged in this way are often incorrectly flagged as malware.
This is issue is documented in the AutoIt Wiki here: https://www.autoitscript.com/wiki/AutoIt_and_Malware


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'

$ToolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$ZipPath = (Get-ChildItem -Path $ToolsDir -Filter 'LogFileParser_*.zip').FullName
Get-ChocolateyUnzip -FileFullPath $ZipPath -Destination $ToolsDir
Remove-Item -Path $ZipPath -Force

if (Get-OSArchitectureWidth -Compare 64) {
  New-Item -Path "$ToolsDir\LogFileParser64.exe.gui" -ItemType 'File'
} else {
  New-Item -Path "$ToolsDir\LogFileParser64.exe.ignore" -ItemType 'File'
}
tools\LICENSE.txt
From: https://github.com/jschicht/LogFileParser/blob/master/LICENSE.md

LICENSE

MIT License

Copyright (c) 2022 Joakim Schicht

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\LogFileParser.exe.gui
 
tools\LogFileParser_v2.0.0.50.zip
md5: FC7E09E20759F1DC635E9DEEA242B407 | sha1: 9A63EF475E4F01DB90B181A916D2BB6EEF5F9077 | sha256: 92FE01FFCC76CE9AB5C579DFA37F9CFCB5D705250C99C09B948F66702EAE1EEC | sha512: 828621A415BB29992D6E2E2C2B16A51ED41B897A6E2D3AFC775509FEA88E5DEB6FAC9B9EDC33FA7EC0358512698421467568395357CEEA6B4439FC9BD35E2064
tools\sqlite3.exe.ignore
 
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Download zip package:
    URL: https://github.com/jschicht/LogFileParser/releases/download/v2.0.0.50/LogFileParser_v2.0.0.50.zip

Compare the SHA256 hash of the downloaded zip package with that of the embedded zip package:
    SHA256: 92FE01FFCC76CE9AB5C579DFA37F9CFCB5D705250C99C09B948F66702EAE1EEC

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
LogFileParser 2.0.0.49 58 Sunday, January 22, 2023 Exempted

This package has no dependencies.

Discussion for the LogFileParser Package

Ground Rules:

  • This discussion is only about LogFileParser and the LogFileParser package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or LogFileParser, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus