Downloads:

32,616

Downloads of v 1.2.0.20190119:

483

Last Update:

19 Jan 2019

Package Maintainer(s):

Software Author(s):

  • Filippo Valsorda

Tags:

cli foss cross-platform development certificates

mkcert

This is not the latest version of mkcert available.

1.2.0.20190119 | Updated: 19 Jan 2019

Downloads:

32,616

Downloads of v 1.2.0.20190119:

483

Maintainer(s):

Software Author(s):

  • Filippo Valsorda

Tags:

cli foss cross-platform development certificates

mkcert 1.2.0.20190119

This is not the latest version of mkcert available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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:

>

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 mkcert -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 mkcert -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 mkcert installed
  win_chocolatey:
    name: mkcert
    state: present
    version: 1.2.0.20190119
    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 'mkcert' do
  action    :install
  version  '1.2.0.20190119'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: mkcert,
    Version: 1.2.0.20190119,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller mkcert
{
   Name     = 'mkcert'
   Ensure   = 'Present'
   Version  = '1.2.0.20190119'
   Source   = 'STEP 3 URL'
}

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


package { 'mkcert':
  provider => 'chocolatey',
  ensure   => '1.2.0.20190119',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install mkcert version="1.2.0.20190119" 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 as a trusted package on 19 Jan 2019.

Description

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" ✅
legal\LICENSE.txt 
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.
legal\VERIFICATION.txt 
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.2.0/mkcert-v1.2.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: D4E8CDD9327FB0532D1AFE465B982AB763B742AF9FCA31220D4E884069CEC269


File 'license.txt' is obtained from:
   https://raw.githubusercontent.com/FiloSottile/mkcert/master/LICENSE
tools\mkcert.exe 
md5: D04692D3647E79FBECDACA46FFB7C940 | sha1: D3FB42B8905701AA9689C20841D04A94DAB63059 | sha256: D4E8CDD9327FB0532D1AFE465B982AB763B742AF9FCA31220D4E884069CEC269 | sha512: 567BA50396E2CA36EFBCBEDC5D088B8A2B365F04B7629BF40D4E57C17F110A96238900D7793FC7DCC45A7331A853E36AF68DE1E9E36B4892C3C864523E3E861D

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.

Version Downloads Last Updated Status
mkcert 1.4.3 4254 Thursday, November 26, 2020 Approved
mkcert 1.4.2 2552 Monday, October 26, 2020 Approved
mkcert 1.4.1 16768 Sunday, November 10, 2019 Approved
mkcert 1.4.0 2553 Saturday, August 17, 2019 Approved
mkcert 1.3.0 3873 Sunday, February 3, 2019 Approved
mkcert 1.2.0.20190119 483 Saturday, January 19, 2019 Approved
mkcert 1.2.0 1076 Monday, January 7, 2019 Approved
mkcert 1.1.2 709 Tuesday, September 11, 2018 Approved
mkcert 1.1.1 194 Thursday, August 23, 2018 Approved
mkcert 1.1.0 154 Friday, August 17, 2018 Approved

This package has no dependencies.

Discussion for the mkcert Package

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.
comments powered by Disqus