Align on mesh security proposal
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- distributed-systems, documentation
Research direction
Start with the design doc’s Edge Types and Transport Security sections, then compare their claims with the code at 8a3e83e. Check the three disputed properties and the linked tracking issue #75. Done means the doc clearly separates what ships today from what is planned, without presenting unimplemented behavior as current.
Written by the indexing model from the issue text.
Description
What would you like to be added
Split the design doc's mesh security sections into what ships today and what is planned.
Why is this needed
The doc reads two ways on the same subject. Edge Types describes shared-key encryption with no per-site authentication, which matches the code. Transport Security describes per-site authenticated envelopes, which is not implemented.
A reader cannot tell which one describes the system. Three properties the doc calls current are not in the code as of 8a3e83e: per-site authenticated state (tracked in #75), key rotation with overlap, and TCP for large state.
From the Grid review, Gaps.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 24
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 79
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from praxis-proxy/grid
-
triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
praxis-proxy/grid#294 ·
Maintainers usually reply within 1 day
-
triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
praxis-proxy/grid#275 ·
Maintainers usually reply within 1 day
-
triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
praxis-proxy/grid#222 ·
Maintainers usually reply within 1 day
-
triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
praxis-proxy/grid#200 ·
Maintainers usually reply within 1 day
-
triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
praxis-proxy/grid#134 ·
Maintainers usually reply within 1 day
All issues in praxis-proxy/grid
Similar issues
-
enhancement user-priority/P3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
element-hq/lk-jwt-service#248 ·
Maintainers usually reply within 1 day
-
agent:triaged bug bughunt pm:pipenv priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SocketDev/socket-patch#1219 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-cli#154 ·
Maintainers usually reply within 3 days