keystonejs/keystone-classic

Automated letsencrypt issuing bad certificate - Fake LE Root X1

Open

#4,660 创建于 2018年6月18日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)JavaScript (14,656 star) (2,288 fork)batch import
4.x candidatehelp wantedquestion

描述

Expected behavior

Valid letsencrypt certificate should be issued.

Actual/Current behavior

An invalid certificate is issued by Fake LE Root X1

Steps to reproduce the actual/current behavior

  1. Set NODE_ENV=production in .env
  2. Add letsencrypt config as per this article.
  3. Run keystone
  4. Load in browser, no green padlock as certificate is invalid.

If I manually generate the certificate with certbot, then move the keys over, everything works properly.

Environment

Software Version
Keystone 4.0.0-beta.5
Node v6.12.3
Ubuntu 16.04

贡献者指南

技术栈
javascriptnodejs
领域
backenddevops
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Node.jsSSL/TLS basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Investigate the automated letsencrypt certificate generation in Keystone. Examine the relevant code (likely in the keystone SSL module) to identify why a 'Fake LE Root X1' certificate is issued instead of a valid one. Compare with manual certbot certificate generation. Look for misconfiguration, outdated ACME library, or issues with the directory endpoint. Check the Keystone documentation and any related issues for known fixes.