Outer Web | Explore

Explore >> Select a destination

You are here		dylanbeattie.net Generating self-signed HTTPS certificates with subjectAltNames : dylanbeattie.net
\|	\|	vninja.net macOS: Catalina Chrome Self-signed Certificate Issues · vNinja.net	3.6 parsecs away Travel
\|	\|	Way back in 2017, the [CA/Browser Forum](https://cabforum.org/about-us/) voted on [Ballot 193 - 825-day Certificate Lifetimes](https://cabforum.org/2017/03/17/ballot-193-825-day-certificate-lifetimes/), which passed. In short, this means that CA issued certificates issued after March 1st 2018 can not have a validity period longer than 825 days. macOS Catalina implements this change, as described in [Requirements for trusted certificates in iOS 13 and macOS 10.15](https://support.apple.com/en-us/HT210176)...	3.6 parsecs away Travel
\|	\|	com.micahrl.me Deploying SSL certificates	2.3 parsecs away Travel
\|	\|	All rituals restricted. All rites reserved.	2.3 parsecs away Travel
\|	\|	markentier.tech Self-signed certificates with mkcert \| markentier.tech	3.7 parsecs away Travel
\|	\|	In a previous sticky I briefly put down how to get a quick'n'dirty self-signed TLS1 certificate, but also mentioned mkce... \| markentier.tech	3.7 parsecs away Travel
\|	\|	securitylab.github.com Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests \| GitHub Security Lab	31.8 parsecs away Travel
\|		In this article, well discuss some common security malpractices for GitHub Actions and workflows, and how to best avoid them. Our examples are based on real-world GitHub workflow implementation vulnerabilities the GitHub Security Lab has reported to maintainers.	31.8 parsecs away Travel