On Wed, 2019-06-19 at 13:05 +0700, Bagas Sanjaya wrote:
> It can be prevented by using wildcard certificates
That is another terrible idea, if that one certificate is compromised
then the attacker can impersonate any subdomain for the entire validity
period. Moving towards individual certs and ke
On 19/06/19 12.38, Paul Wise wrote:
On Wed, Jun 19, 2019 at 12:51 PM Bagas Sanjaya wrote:
Unlike LE, we (debian.org) have to create Certificate Signing Requests (CSR)
which will be sent to those CA.
As a member of the Debian sysadmin team I can tell you that this is
never going to happen. Ma
On Wed, Jun 19, 2019 at 12:51 PM Bagas Sanjaya wrote:
> Unlike LE, we (debian.org) have to create Certificate Signing Requests (CSR)
> which will be sent to those CA.
As a member of the Debian sysadmin team I can tell you that this is
never going to happen. Manually doing TLS is way too much wor
Dear debian.org webmasters,
Currently debian.org use SSL certificate from Let's Encrypt (LE). That
is not bad, however there are cases when scammers get SSL certificate
from LE to secure their (untrustworthy?) sites. Even LE said that scam
prevention are outside their scope, due to their natur
4 matches
Mail list logo
