Consider just-in-time fetching
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 45
- Forks
- 12
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 13
Description
In our meeting today we discussed whether/how upki could be used in container images where size is important.
- Should a base set of filters be shipped as part of an image?
- Could we do something to ensure that filters are updated over time in environments where there's no init process to trigger timely updates?
- Should there be a mode where upki revocation checks go out and (asynchronously) fetch if necessary?
- A downstream container image could run for a while, so just leaving it with its starter set seems suboptimal (if strictly better than without any upki)
@jnsgruk does this capture your thoughts/goals/concerns?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the current upki behavior for container images, filter updates, and revocation checks; the issue does not name files, tests, or entry points. Compare the proposed base filter set and asynchronous just-in-time fetching with environments lacking an init process, then clarify the desired mode and its acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100