为什么 browsers 警告关于 self-signed certificates?

self-signed certificate 有否链接到 trusted Certificate Authority. browser cannot 验证该公共键 belongs 到 claimed identity. 此是正确行为 — 为 production, use certificate 从 trusted CA (Let's Encrypt, etc.).

什么键大小应该 I use 为 RSA?

2048 bits 是最小值 acceptable 大小 today. 4096 bits provides larger 安全 margin 但是 slower 为键 generation 和 handshake. 为新 systems, 考虑 ECDSA P-256 哪个 provides equivalent 安全到 3072-位 RSA 在 much smaller 键 sizes.

生成 RSA key pair and inspect self-signed certificate fields

Create RSA 键对为 testing, 和理解结构的 self-signed X.509 certificate 为本地 development.

1

Self-signed certificates 是 used 为本地 TLS testing 和内部 services. 它们是不 trusted 通过 browsers (否 CA 签名) 但结构是 identical 到公共 certificates. Understanding fields helps 调试 TLS issues.
2

RSA 工具 →
生成 an RSA key pair (2048 or 4096 bits). The tool outputs the public and private keys in PEM format. Use this for local testing only — never for production TLS.
3

UUID / ULID 生成器 →
生成 a UUID to use as a serial number or unique identifier for the certificate entity.
4

self-signed X.509 certificate contains: version, serial 数字, subject (CN, O, OU), issuer (相同 as subject 为 self-signed), validity (notBefore/notAfter), 公共键, 和签名. 签名是 computed 通过 subject's own 私有键, 哪个是为什么 browsers 拒绝它.

常见问题

为什么 browsers 警告关于 self-signed certificates?: self-signed certificate 有否链接到 trusted Certificate Authority. browser cannot 验证该公共键 belongs 到 claimed identity. 此是正确行为 — 为 production, use certificate 从 trusted CA (Let's Encrypt, etc.).
什么键大小应该 I use 为 RSA?: 2048 bits 是最小值 acceptable 大小 today. 4096 bits provides larger 安全 margin 但是 slower 为键 generation 和 handshake. 为新 systems, 考虑 ECDSA P-256 哪个 provides equivalent 安全到 3072-位 RSA 在 much smaller 键 sizes.

解决此任务的工作流

生成 UUID 并编码为 Base58

生成随机 UUID 并编码为 Base58，得到更短、URL 友好的标识符。

管道

生成 UUID 并 Base64 编码

生成 UUID 后 Base64 编码用于紧凑存储。

管道

常见问题

解决此任务的工作流

相关工具