Relay support for IP address certificates?
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
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:
- Dominant language
- Rust
- Stars
- 13k
- Forks
- 771
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 n0-computer/iroh
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
n0-computer/iroh#4709 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
n0-computer/iroh#4689 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
n0-computer/iroh#4669 · 1 comment ·
Maintainers usually reply within 1 day
-
Example for restricting the trusted CA rootsPossibly taken A pull request linked to this issue is open or already merged. Openready-for-pr
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
n0-computer/iroh#4637 ·
Maintainers usually reply within 1 day
-
c-iroh-relay wire-breaking
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
n0-computer/iroh#4585 · 2 comments ·
Maintainers usually reply within 1 day
All issues in n0-computer/iroh
Similar issues
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
sims1253/r-typeshed#140 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/craft-libs#2867 ·
Maintainers usually reply within 1 day
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100