kubernetes/minikube

Add Signing Process for Windows Installer

Open

#4,841 opened on Jul 22, 2019

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Go (5,222 forks)batch import
help wantedkind/featurelifecycle/frozenpackaging/windowspriority/backlogsig/releasesig/security

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

As of now, whenever the minikube installer is run, the following screen comes up which makes it look as if the executable is malicious to a user -

image

This also revolves around having infrastructure/process to sign the executables/installers so that they can be verified.

Not sure if we need to have for other operating systems as well.

-Pranav

Contributor guide

Research direction
Investigate the current build process for the Windows installer, specifically the creation of the .msi file and the executable. Research code signing options for Windows (e.g., using Azure Key Vault, DigiCert, etc.) and propose a method to sign the installer during the CI pipeline. Look into the 'smartsign' or similar tools used by the Kubernetes infra team.
Tech stack
go
Domain
devopsreleasesecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoWindows Development Environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30