Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

docs/ci: ssh-authz grace-time wording, stale architecture doc, pin sshpiperd checksum

Closed
#3,085 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, go

Research direction

Read docs/SENTINEL-SSH-AUTHZ.md and docs/architecture/ssh-live-authorization.md, then inspect .github/workflows/ssh-ban.yml and scripts/ci/build-fetches.allow. Check the sshpiperd release checksums.txt for the download checksum and see whether the inventory gate requires its fingerprint. Done means the grace-time wording, Component 3 description, and checksum pin are updated.

Written by the indexing model from the issue text.

Description

documentation

Docs and workflow follow-ups from the review of #3075 (merged).

  • docs/SENTINEL-SSH-AUTHZ.md: state that the 90s login grace (--login-grace-time 90s, #3074) applies to all unauthenticated connections, not just approval ones.
  • docs/architecture/ssh-live-authorization.md Component 3 is stale: it still describes approval_id in sshpiperd meta.
  • .github/workflows/ssh-ban.yml: the sshpiperd download is by tag only; pin its sha256 from the release checksums.txt (and add the fingerprint to scripts/ci/build-fetches.allow if the inventory gate requires it).
Dominant language
Go
Stars
296
Forks
38
Avg merge
7h 44m
Merged PRs (30d)
631

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from FootprintAI/Containarium

All issues in FootprintAI/Containarium

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.