Relay support for IP address certificates?

Open
#4,697 0 comments 1 reaction 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
networking

Research direction

Start by reading the relay documentation and locating the relay code that handles certificate provisioning and renewal; the issue does not name specific files or tests. Determine whether numerical IP address certificates are supported and whether automated renewal is in scope. Done means documenting the current support and, if support is absent, defining the changes needed for IP certificate issuance and renewal.

Written by the indexing model from the issue text.

Description

c-iroh-relay

Hello!

Opening this issue to ask if the current relay code has support for numerical IP address certificates. Does it support this use, perhaps even automated renewal of these types of certs? Lets Encrypt started providing this possibility to the general public earlier this year: https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability

I tried looking around in the issues and the relay documentation but I couldn't find anything about it.

As for why, I think for resilience reasons supporting IP address certs makes a lot of sense. It would enable relay operators to be more resistant to the vagaries of changing legal regimes. It would also provide a much more stable foundation for projects to build petname systems on-top of Iroh if the relay infrastructure wasn't, at the final count, reliant on modern day DNS.

I was inspired to open this issue today because of the ongoing outage Codeberg is going through atm, where the rights to their domain name were suddenly revoked over night:

https://status.codeberg.eu/status/codeberg

Dominant language
Rust
Stars
13k
Forks
771
Avg merge
4d 7h
Merged PRs (30d)
20

Getting set up

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 n0-computer/iroh

All issues in n0-computer/iroh

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.