I want to be able to reach various appliances in our home network (router, modem, etc.) via HTTPS without having to dismiss those scary warnings all the time.
> why do you want a wildcard certificate!?
Because most of those appliances are not connected to the public internet. They do allow uploading a certificate though.
hmmm ... idk. for LAN-based appliances, which will likely even have invalid names a la
* router.my.home
or
* nas.my.home
or whatever "dummy-tld" + local domain one uses ...
so if i want to use certificates in such an environment, i would create my own CA and import its public cert(s) into my browsers - or OSes - certificate-store.
problem solved!!
and also learned some useful lessons regarding "run your own CA" :)
1. what do you want to do with your certificate?
2. why do you want a wildcard certificate!?
imho. its a lot easier - and also a bit safer - to use certificate(s) with actual names in it.
ps. you are able to specify multiple names for a certificate :)
idk for example so its valid for "domain.tld" and "www.domain.tld" etc.
cheersv