Downloads:
253,380
Downloads of v 0.0.3:
951
Last Update:
28 Sep 2015
Package Maintainer(s):
Software Author(s):
- Rob Reynolds
Tags:
checksum md5 sha1 sha2 sha256 sha512 hash- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
checksum
This is not the latest version of checksum available.
- 1
- 2
- 3
0.0.3 | Updated: 28 Sep 2015
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
253,380
Downloads of v 0.0.3:
951
Maintainer(s):
Software Author(s):
- Rob Reynolds
checksum 0.0.3
This is not the latest version of checksum available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download checksum --internalize --version=0.0.3 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade checksum -y --source="'INTERNAL REPO URL'" --version="'0.0.3'" [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="'INTERNAL REPO URL'" --version="'0.0.3'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install checksum
win_chocolatey:
name: checksum
version: '0.0.3'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'checksum' do
action :install
source 'INTERNAL REPO URL'
version '0.0.3'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller checksum
{
Name = "checksum"
Version = "0.0.3"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'checksum':
ensure => '0.0.3',
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.
This package was approved by moderator gep13 on 22 Dec 2015.
checksum - Command line file checksum validator.
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.
Example: checksum -f="relative\path"
Example: checksum "relative\path"
Example: checksum -f="c:\absolute\path" -t=sha256
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.
Example: checksum "c:\path\to\somefile.exe" -c="thehash"
Example: checksum -f="c:\path\to\somefile.exe" -c="thehash" -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'.
-c, --check=VALUE
Optional: check - the signature you want to check. Not case sensitive.
md5: 0AA5F736E619FDB8664C43779466DD14 | sha1: FE239546417500BA0B324E2C6F205865DE0DE7D8
Log in or click on link to see number of positives.
- checksum.0.0.3.nupkg (10978926afae) - ## / 56
- checksum.exe (69b22ee0c328) - ## / 68
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 |
---|---|---|---|---|
checksum 0.3.1 | 92367 | Friday, January 13, 2023 | Approved | |
checksum 0.2.0 | 156457 | Wednesday, March 22, 2017 | Approved | |
checksum 0.1.0 | 1813 | Monday, September 5, 2016 | Approved | |
checksum 0.0.3 | 951 | Monday, September 28, 2015 | Approved | |
checksum 0.0.2 | 1218 | Sunday, March 2, 2014 | Approved | |
checksum 0.0.1 | 558 | Saturday, March 1, 2014 | Approved |
2014-Present RealDimensions Software, LLC
This package has no dependencies.
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.