Consider just-in-time fetching
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
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.
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?
- Dominant language
- Rust
- Stars
- 181
- Forks
- 14
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 21
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
- 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 rustls/upki
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
rustls/upki#276 · 1 reaction ·
Maintainers usually reply within 1 day
-
OneCRL supportOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
rustls/upki#229 · 1 comment · 8 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rustls/upki#199 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
rustls/upki#171 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Eyevinn/open-live-ingest#36 · 1 comment ·
Maintainers usually reply within 1 day
-
app
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug bug jury peripheral:i2s
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
esp-rs/esp-hal#6828 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ライブラリを追加Openpriority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#13015 ·
Maintainers usually reply within 1 day