Vector35 / Vector35/binaryninja-api

hashes for dev

Open
#4,613 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Updates Effort: Low Impact: Low
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

To verify stable builds, hashes.json (and .js) are uploaded to the website. However, no equivalent exists for dev. We have intentionally not given the CI infrastructure the ability to update the website directly as a security boundary, but we could easily set up a secondary domain that only contains dev hashes.

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 examining the existing hashes.json and hashes.js publishing path on the website, then review how the CI infrastructure produces dev builds. Done means dev hashes are available through a secondary domain while preserving the stated security boundary that prevents CI from updating the website directly.

Written by the indexing model from the issue text.

Assessment

Domain
devops, infrastructure, release
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.