upki-openssl should not fail if upki is not fully configured
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 45
- Forks
- 12
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 13
Description
If the upki config does not exist, or the cache directory is empty, we should allow the connection to proceed, otherwise clients will be broken in containers or fresh systems that have not yet initialized the upki store (or systems that removed upki).
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 locating the upki-openssl connection setup and any tests covering missing configuration or an empty cache. Verify the current behavior when the upki config is absent and when the cache directory has no entries. Done means both cases allow the connection to proceed while initialized upki stores continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100