HelloZeroNet / HelloZeroNet/ZeroNet

All the ZeroNet forks and releases should be signed

Open
#2,816 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
18.8k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

I can't believe in the day of state MITM that ZeroNet ships unsigned releases or binaries - they all should be signed with an originator's key.

That includes the releases on zeronet.io

Forkers - pleases get an openpgp key and put a link to your keys in your READMEs then sign your releases.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names releases on zeronet.io, fork READMEs, binaries, and OpenPGP keys, but no repository files or tests. Start by mapping how releases are produced and published, then define the signing scope and verification path; done means the agreed releases and fork guidance are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python
Domain
release, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.