[sf-lug] letsencrypt wildcard certs, now covering: sf-lug.org, (and sf-lug.com and balug.org) :-)
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Sat Mar 17 08:29:16 PDT 2018
Be the first on your block to have and use a Letsencrypt.org wildcard cert!
:-)
Yes, sf-lug.org (and sf-lug.com), and likewise balug.org now generally
covered by letsencrypt.org wildcard certs. This does also simplify things
a fair bit - certainly at least on the cert side of things.
Situation earlier yesterday, three certs covering:
www.sf-lug.org
ipv4.sf-lug.org
ipv6.sf-lug.org
sf-lug.org
www.ipv4.sf-lug.org
www.ipv6.sf-lug.org
www.sf-lug.com
sf-lug.com
www.balug.org
archive.balug.org
balug.org
beta.balug.org
ipv4.balug.org
ipv6.balug.org
lists.balug.org
new.balug.org
php.test.balug.org
secure.balug.org
test.balug.org
wiki.balug.org
www.archive.balug.org
www.beta.balug.org
www.ipv4.balug.org
www.ipv6.balug.org
www.new.balug.org
www.php.test.balug.org
www.secure.balug.org
www.test.balug.org
www.wiki.balug.org
Now three certs covering:
*.sf-lug.org
sf-lug.org
*.ipv4.sf-lug.org
*.ipv6.sf-lug.org
*.sf-lug.com
sf-lug.com
*.balug.org
balug.org
*.archive.balug.org
*.beta.balug.org
*.ipv4.balug.org
*.ipv6.balug.org
*.new.balug.org
*.secure.balug.org
*.test.balug.org
*.php.test.balug.org
*.wiki.balug.org
$ nmap -6 -Pn -r -sT -p 443 --script=ssl-cert www.sf-lug.org
www.sf-lug.com www.balug.org | egrep -e '^(Nmap scan report for |Other
addresses for |\| (ssl-cert: Subj|Subject Alt|Not valid a))'
Nmap scan report for www.sf-lug.org (2001:470:1f05:19e::3)
Other addresses for www.sf-lug.org (not scanned): 198.144.194.238
| ssl-cert: Subject: commonName=*.sf-lug.org
| Subject Alternative Name: DNS:*.ipv4.sf-lug.org,
DNS:*.ipv6.sf-lug.org, DNS:*.sf-lug.org, DNS:sf-lug.org
| Not valid after: 2018-06-15T08:09:50
Nmap scan report for www.sf-lug.com (2001:470:1f05:19e::3)
Other addresses for www.sf-lug.com (not scanned): 198.144.194.238
| ssl-cert: Subject: commonName=*.sf-lug.com
| Subject Alternative Name: DNS:*.sf-lug.com, DNS:sf-lug.com
| Not valid after: 2018-06-15T08:20:15
Nmap scan report for www.balug.org (2001:470:1f05:19e::2)
Other addresses for www.balug.org (not scanned): 198.144.194.238
| ssl-cert: Subject: commonName=*.balug.org
| Subject Alternative Name: DNS:*.archive.balug.org, DNS:*.balug.org,
DNS:*.beta.balug.org, DNS:*.ipv4.balug.org, DNS:*.ipv6.balug.org,
DNS:*.new.balug.org, DNS:*.php.test.balug.org, DNS:*.secure.balug.org,
DNS:*.test.balug.org, DNS:*.wiki.balug.org, DNS:balug.org
| Not valid after: 2018-06-15T07:39:09
$
> Date: Wed, 14 Mar 2018 03:20:42 -0700
> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
> To: "Berkeley Unix User Group" <buug at buug.org>
> Subject: wildcard certs arrived to letsencrypt.org
> Looks like wildcard certs have arrived to letsencrypt.org:
> https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578
More information about the sf-lug
mailing list