labstack / labstack/armor

Account creation on ACMEv1 is disabled

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.7k
Forks
64
PR merge metrics
No merged PRs in 30d

Description

This version should be included.
acme: https://github.com/golang/crypto/commit/a950601f39e69382d60ea46fa15cecc9d9b70ec6

Fix temporary:

tls:
  address: ":443"
  auto: true
  directory_url: "https://acme-v02.api.letsencrypt.org/directory"

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue names no repository file, test, or entry point. Compare the ACMEv1 behavior with golang/crypto commit a950601f39e69382d60ea46fa15cecc9d9b70ec6 and inspect the shown TLS configuration; done means ACMEv1 account creation works without relying on the ACMEv2 workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.