docs/security: file:line citations and the measurement note are out of date
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bash, shell
- Domain
- documentation
Research direction
Start with docs/security.md, the canonical English file, and verify each measurement against the named source files and functions, including scripts/internal/remote-sync.mjs, scripts/remote.sh, scripts/internal/sync-cipher.mjs, docs/design/remote-sync.md, and docs/spec/ref/age-v1-profile.md. Update the stale claims and replace drifting line citations with function names or pinned commits, then bring docs/security.ja.md into sync. Done when the measurements and citations match the sources.
Written by the indexing model from the issue text.
Description
docs/security.md and docs/security.ja.md cite source locations as file:line, and the citations have drifted since they were written.
What is stale
- The measurement note says it was taken on
integration/remoteat commit452da72and that the only files that branch changes are the two security docs. Neither is true any more. - Many
file:linecitations point at the wrong lines. Examples found while reading (current line in parentheses):scripts/internal/remote-sync.mjs:1686(now about 2371),:1699(about 2384);scripts/remote.sh:1280(about 1697),:1758(about 2381),:1076cmd_unlock(about 1489),:1729_remote_configure_keyed_team(about 2348);scripts/internal/sync-cipher.mjs:718-725openEnvelope(about 792),:277-281(about 317);docs/design/remote-sync.md:83-85(about 87);docs/spec/ref/age-v1-profile.md:342-345does not match the quoted sentence. Theserver/src/citations still match. sync-cipher.mjsis described as 819 lines; it is 893.- "last touched on 2026-07-27, by commit 1a56d8e" for
docs/spec/ref/age-v1-profile.mdis out of date (last touched 2026-09-16).
Proposed fix
Re-measure the claims, then cite function names (or a pinned commit) instead of line numbers, so the citations survive edits. The English file is canonical; the Japanese file follows it.
Not urgent for 1.6.0; tracked here so it is done after GA.
- Dominant language
- Shell
- Stars
- 1.5k
- Forks
- 156
- Avg merge
- 16h 32m
- Merged PRs (30d)
- 213
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 fujibee/agmsg
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
[P2] app: peer-message previews pass C0/DEL control bytes to pty_injectPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
lobaro/restic-backup-docker#114 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
community-scripts/ProxmoxVE#18529 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
conda-forge/poppler-feedstock#198 ·