Downloads:

53,134

Downloads of v 0.2.0:

49,503

Last Update:

22 Mar 2017

Package Maintainer(s):

Software Author(s):

  • Rob Reynolds

Tags:

checksum md5 sha1 sha2 sha256 sha512 hash

checksum

0.2.0 | Updated: 22 Mar 2017

Downloads:

53,134

Downloads of v 0.2.0:

49,503

Maintainer(s):

Software Author(s):

  • Rob Reynolds

checksum 0.2.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

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

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade checksum -y --source="'STEP 3 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 checksum -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure checksum installed
  win_chocolatey:
    name: checksum
    state: present
    version: 0.2.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'checksum' do
  action    :install
  version  '0.2.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: checksum,
    Version: 0.2.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller checksum
{
   Name     = 'checksum'
   Ensure   = 'Present'
   Version  = '0.2.0'
   Source   = 'STEP 3 URL'
}

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


package { 'checksum':
  provider => 'chocolatey',
  ensure   => '0.2.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install checksum version="0.2.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator flcdrg on 31 Oct 2019.

Description

checksum - Command line file checksum validator.

Determine a checksum for a file

checksum checks a file and returns a checksum for md5, sha1, and sha2 (sha256 and sha512).

To use checksum you would simply provide a file path and it will return the sum for the file.

Examples

  • checksum -f="relative\path"
  • checksum "relative\path"
  • checksum -f="c:\absolute\path" -t=sha256

Validate a file against an existing signature

You can also check against an existing signature.
To validate against an existing signature (hash) you would simply provide the file and the expected signature. When checking a signature, if the signature is valid it exits with 0, otherwise it exits with a non-zero exit code.

Examples

  • checksum -f="c:\absolute\path" -c=8AC4EA9A7B18E67EA97088220C40041B355A2C3049AA4E290D1F65A94BEFA9EF
  • checksum -f="c:\absolute\path" -c=8AC4EA9A7B18E67EA97088220C40041B355A2C3049AA4E290D1F65A94BEFA9EF -t sha256

SYNOPSIS

checksum [-t=sha1|sha256|sha512|md5] [-c=signature] [-f=]filepath

OPTIONS

-?, --help, -h
  Prints out the options.
-f, --file=VALUE
  REQUIRED: file - The is the name of the file. The file should exist
-t, --type, --hashtype=VALUE
  Optional: hashtype - 'md5', 'sha1', 'sha256', or 'sha512'. Defaults to 'md5' or is determined by length of passed check value.
-c, --check=VALUE
  Optional: check - the signature you want to check. Not case sensitive.

tools\checksum.exe
md5: 5CA71CBFF5A8DE7E5E30B6E94CD42069 | sha1: 991701A32492D743430627CBFBD56D6884C32588 | sha256: 23FBD1EE66FCE6872E97B2FE84C409AB30A74FE8720B722BC6F8BAE6E7764C04 | sha512: 77E31EC0DCA4E4895D3A4C0E84C6C1516D94089763F1735CAC150EFCD4EEC36107BB810E24D94C1208B7A80881D858DBFE887B32DA6F6D8F0C48F21C2525D0BE

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.

Version Downloads Last Updated Status
checksum 0.1.0 1605 Monday, September 5, 2016 Approved
checksum 0.0.3 732 Monday, September 28, 2015 Approved
checksum 0.0.2 972 Sunday, March 2, 2014 Approved
checksum 0.0.1 322 Saturday, March 1, 2014 Approved

This package has no dependencies.

Discussion for the checksum Package

Ground Rules:

  • This discussion is only about checksum and the checksum 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 checksum, 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