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 (31,799 stars) (5,222 forks)batch import
help wantedkind/featurelifecycle/frozenpackaging/windowspriority/backlogsig/releasesig/security

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

Tech stack
go
Domain
securityreleasedevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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
code signing certificateWindows installer toolingGo app build process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate existing code signing practices in the minikube repository. Look at the build process for Windows installer in scripts or Makefile. Check if there are any certificates stored securely. Evaluate adding a step to sign the executable during the CI/CD pipeline using a certificate like Azure Key Vault or similar. Coordinate with maintainers about certificate acquisition and cost.