Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.

Comodo Caught Breaking New CAA Standard One Day After It Went Into Effect

posted by Fnord666 on Wednesday September 13 2017, @12:06PM   Printer-friendly
from the oh-did-that-start-today? dept.

MrPlow writes:

Submitted via IRC for SoyCow1937

One day after the CAA (Certificate Authority Authorization) standard became obligatory on September 8, a German security researcher caught Comodo breaking the rules and issuing an SSL certificate it was not supposed to issue.

CAA allows website owners to specify what Certificate Authorities (CAs) are allowed to issue certificates in their name. Site owners can set up a CAA rule for their domain by adding a text field in DNS entries such as the one below:

bleepingcomputer.com. CAA 0 issue "symantec.com"

This small rule tells any Certificate Authority that only Symantec can issue SSL certificates for the BleepingComputer.com domain.

According to the rules of the CAA standard approved by the CA/Browser Forum in Ballot 187, this April, Certificate Authorities such as Comodo have to check a CAA field in DNS records before issuing new SSL certificates.

On Monday, German security researcher Hanno Böck shared with the infosec community that he managed to obtain an SSL certificate from Comodo — now revoked — for his own website, even if the CAA field limited SSL issuance only to Let's Encrypt.

Source: https://www.bleepingcomputer.com/news/security/comodo-caught-breaking-new-caa-standard-one-day-after-it-went-into-effect/

Original Submission

 
This discussion has been archived. No new comments can be posted.
Comodo Caught Breaking New CAA Standard One Day After It Went Into Effect | Log In/Create an Account | Top | 18 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Wednesday September 13 2017, @12:32PM

    by Anonymous Coward on Wednesday September 13 2017, @12:32PM (#567193)

    So only "symantec.com" is allowed to issue the certs... but what defines "symantec.com"?

    The very same DNS server that also served this line.