A critical vulnerability (CVE-2019-10149) was found in Exim mail server. It allows to execute some code on victim's server with root privileges. This vulnerability affects versions from 4.87 to 4.91. If you are using Exim and haven't ordered managed service, you should urgently upgrade your version of Exim to 4.92.
Letsencrypt is releasing the wildcard certificate free from this month
-
ecigplanete
- Posts: 1
- Joined: Sat Apr 27, 2019 10:55 pm
- Os: Debian 7x
- Web: apache + nginx
Re: Letsencrypt is releasing the wildcard certificate free from this month
+1 thanks a lot
-
royalpublishing
- Posts: 3
- Joined: Thu May 09, 2019 3:43 pm
- Os: Ubuntu 18x
- Web: apache
Re: Letsencrypt is releasing the wildcard certificate free from this month
So as of 0.9.8-24, there's support for it and a screenshot of a checkbox, but how do you actually request a wildcard cert for a specific web domain? Is there a specific procedure outlined anywhere?
With some trial and error, it appears that putting *.domain.tld in the alias field alone will allow you to register a wildcard cert successfully, but the second you try to add an additional alias in there, such as www.domain.tld, you get an Error 15.
From my little experience so far with Vesta, as a workaround, it looks like normally we use that field to add alternate subject names for the certificates, for instance to also be able to have a mail server certificate at mail.domain.tld, but is the alias field really the best place place to be doing this since you are also adding aliases for apache simultaneously? What if you don't want apache listening for mail.domain.tld or *.domain.tld domain (if that's even an acceptable alias parameter in apache)?
Anybody have any input?
With some trial and error, it appears that putting *.domain.tld in the alias field alone will allow you to register a wildcard cert successfully, but the second you try to add an additional alias in there, such as www.domain.tld, you get an Error 15.
From my little experience so far with Vesta, as a workaround, it looks like normally we use that field to add alternate subject names for the certificates, for instance to also be able to have a mail server certificate at mail.domain.tld, but is the alias field really the best place place to be doing this since you are also adding aliases for apache simultaneously? What if you don't want apache listening for mail.domain.tld or *.domain.tld domain (if that's even an acceptable alias parameter in apache)?
Anybody have any input?