mimblewimble/grin

Fence off txhashset validation in its own process

Open

#2,741 opened on Apr 10, 2019

View on GitHub
 (11 comments) (0 reactions) (0 assignees)Rust (991 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (4,876 stars)
PR merge metrics
 (Avg merge 6d 11h) (25 merged PRs in 30d)

Description

When downloaded from the network on sync, a txhashset archive should be handled with more care than we do now, as it could be forged to mess things up in all sorts of ways. We should fence this off in a different process until the validation code is completely happy with what we were provided. Something like chroot, that limits the hard drive visibility of the forked process would also be great but may be hard to achieve across platforms.

Contributor guide

Research direction
Investigate how to spawn a separate process in Rust for txhashset validation, and explore cross platform sandboxing techniques like chroot (Linux) or equivalent on Windows/macOS.
Tech stack
rust
Domain
backendsecurity
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40