IPC API for use with containers

Open
  • Is something wrong?
#171 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
api, security

Research direction

No files, tests, or entry points are named in the issue. Start by surveying the repository's certificate and revocation-information interfaces, then determine the IPC boundary and container/host compatibility requirements; done means a defined, usable API for containers to access host-provided certificates and revocation data.

Written by the indexing model from the issue text.

Description

Due to (notably) differences in libc, it’s rarely possible for a library built for the host to run in a container reliably. It would be very nice to have an IPC API that containers could use so that they could use host-provided certificates and revocation information.

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

  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 rustls/upki

All issues in rustls/upki

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.