Downloads:
272,147
Downloads of v 1.4.0:
2,750
Last Update:
17 Aug 2019
Package Maintainer(s):
Software Author(s):
- Filippo Valsorda
Tags:
cli foss cross-platform development certificates- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
mkcert
This is not the latest version of mkcert available.
- 1
- 2
- 3
1.4.0 | Updated: 17 Aug 2019
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
272,147
Downloads of v 1.4.0:
2,750
Maintainer(s):
Software Author(s):
- Filippo Valsorda
mkcert 1.4.0
This is not the latest version of mkcert available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Filippo Valsorda. The inclusion of Filippo Valsorda trademark(s), if any, upon this webpage is solely to identify Filippo Valsorda goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install mkcert, run the following command from the command line or from PowerShell:
To upgrade mkcert, run the following command from the command line or from PowerShell:
To uninstall mkcert, 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 mkcert --internalize --version=1.4.0 --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 mkcert -y --source="'INTERNAL REPO URL'" --version="'1.4.0'" [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 mkcert -y --source="'INTERNAL REPO URL'" --version="'1.4.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install mkcert
win_chocolatey:
name: mkcert
version: '1.4.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'mkcert' do
action :install
source 'INTERNAL REPO URL'
version '1.4.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller mkcert
{
Name = "mkcert"
Version = "1.4.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'mkcert':
ensure => '1.4.0',
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 as a trusted package on 17 Aug 2019.
mkcert
is a simple CLI tool for making locally-trusted development certificates. It requires no configuration.
mkcert
automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert does not automatically configure servers to use the certificates, though, that's up to you.
$ mkcert -install
Created a new local CA at "/Users/filippo/Library/Application Support/mkcert" 💥
The local CA is now installed in the system trust store! ⚡️
The local CA is now installed in the Firefox trust store (requires restart)! 🦊
$ mkcert example.com "*.example.org" myapp.dev localhost 127.0.0.1 ::1
Using the local CA at "/Users/filippo/Library/Application Support/mkcert" ✨
Created a new certificate valid for the following names 📜
- "example.com"
- "*.example.org"
- "myapp.dev"
- "localhost"
- "127.0.0.1"
- "::1"
The certificate is at "./example.com+5.pem" and the key at "./example.com+5-key.pem" ✅
md5: 740AD5379222687DB917F4A0FA66847C | sha1: 9BA4A5564FE1BB8331F6489EA5F135999BEBCFC2 | sha256: CAD9EA757779C4874266FE61D163762A591C4C9A6D82E0C4458430735F79A144 | sha512: A0B2A6DF219AE6D79F7BCD6A9338C50678CE8DA9527AC3E8E1C296CF2403FE6972ACCC5CB4AA3C49F1F323DC691B2BC710486A4367B35F0CF41F4B99C1C1C42A
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
Package can be verified like this:
1. Go to
x64: https://github.com//FiloSottile/mkcert/releases/download/v1.4.0/mkcert-v1.4.0-windows-amd64.exe
to download the installer.
2. You can use one of the following methods to obtain the SHA256 checksum:
- Use powershell function 'Get-FileHash'
- Use Chocolatey utility 'checksum.exe'
checksum64: CAD9EA757779C4874266FE61D163762A591C4C9A6D82E0C4458430735F79A144
File 'license.txt' is obtained from:
https://raw.githubusercontent.com/FiloSottile/mkcert/master/LICENSE
Copyright (c) 2018 The mkcert Authors. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
* Neither the name of Google Inc. nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Log in or click on link to see number of positives.
- mkcert.1.4.0.nupkg (40c00aca1e01) - ## / 60
- mkcert.exe (cad9ea757779) - ## / 70
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 |
---|---|---|---|---|
mkcert 1.4.4 | 182805 | Wednesday, April 27, 2022 | Approved | |
mkcert 1.4.3 | 59121 | Thursday, November 26, 2020 | Approved | |
mkcert 1.4.2 | 2726 | Monday, October 26, 2020 | Approved | |
mkcert 1.4.1 | 17076 | Sunday, November 10, 2019 | Approved | |
mkcert 1.4.0 | 2750 | Saturday, August 17, 2019 | Approved | |
mkcert 1.3.0 | 4055 | Sunday, February 3, 2019 | Approved | |
mkcert 1.2.0.20190119 | 685 | Saturday, January 19, 2019 | Approved | |
mkcert 1.2.0 | 1289 | Monday, January 7, 2019 | Approved | |
mkcert 1.1.2 | 900 | Tuesday, September 11, 2018 | Approved | |
mkcert 1.1.1 | 394 | Thursday, August 23, 2018 | Approved | |
mkcert 1.1.0 | 346 | Friday, August 17, 2018 | Approved |
This package has no dependencies.
Ground Rules:
- This discussion is only about mkcert and the mkcert 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 mkcert, 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.