v1.4.3
astoilkov/jsblocksv1.4.3Nov 25, 2020by FiloSottile
AI Summary
The Extended Key Usage (EKU) logic has been simplified to align with standard certificate generation rules, and builds are now managed via GitHub Actions.
Key Highlights
- Simplified EKU logic for certificates
- Consistent with standard certificate generation
- Releases are now built from GitHub Actions
New Features
- EKU rules: IP/DNS/URI implies serverAuth
- EKU rules: -client flag implies clientAuth
- EKU rules: Email SAN implies emailProtection
Full Release Notes
The EKU logic is now simpler, and it follows the following rules * if an IP address, DNS name, or URI SAN is present, serverAuth is included * if `-client` is used, clientAuth is included * if an email address SAN in present, emailProtection is included Certificate generation based on CSRs is now consistent with standard certificate generation. Releases are now built from GitHub Actions.