node-easy-cert
node-easy-cert copied to clipboard
add support for extra hostname list for single cert
小部分 mac 用户走 https server 嗅探方案始终遇到超时被判定为未信任,但实际上证书又是信任过的,找到 macos 原生命令用来判断证书是否已信任了,在上层包里已在用户侧验证通过
Hi, `npm audit` reports, your package depends on `node-forge` which had a security vulnerability prior version 0.10.0. Currently the required version of "node-forge" is "^0.6.42" Can you please bump the...
Bumps [node-forge](https://github.com/digitalbazaar/forge) from 0.6.49 to 0.10.0. Changelog Sourced from node-forge's changelog. 0.10.0 - 2020-09-01 Changed BREAKING: Node.js 4 no longer supported. The code may still work, and non-invasive patches to...
https://github.com/ottomao/node-easy-cert/blob/master/src/certGenerator.js#L33 实测1024位部分终端会报异常
Calling ifRootCATrusted method on non-windows platform is possible to throw a ssl verify problem when trusting a self signed certificate. ```javascript const testCmd = `curl https://${DOMAIN_TO_VERIFY_HTTPS}:${port}`; ```
On first creation of the certificate the keys are strings, on re-use the keys are a buffer. In practise it will not matter much, it's just inconsistent :-) ```typescript crtMgr.getCertificate('localhost',...
当hostname为`*.foo.com` 这种时,直接报错,因为写key和crt时文件名包含\*,手动指定文件名后生成的证书能正常使用
It seems like Chrome does not allow certs generated with just common name anymore: https://alexanderzeitler.com/articles/Fixing-Chrome-missing_subjectAltName-selfsigned-cert-openssl/ Does this library support SAN (Subject alternative name) certs?