MozillaSecurity / MozillaSecurity/ffpuppet

Generate NSS Cert DB once and include it in project release

Open
#184 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
33
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Rather than generating a new certificate every launch instance and updating the cert9.db, we should generate a single NSS cert database with our certificate and include that in the project release. This would avoid requiring users to have access to certutil which is particularly an issue on Windows.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating where each launch generates cert9.db and where project releases package runtime files; inspect the certutil dependency, especially on Windows. Done means a single NSS certificate database is included in the release and launches no longer require users to run certutil or generate a new database.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.