Pressure Increases on Browser Vendors to Act

 
 
By Fahmida Y. Rashid  |  Posted 2011-03-29 Email Print this article Print
 
 
 
 
 
 
 


 

Despite claims by Comodo CEO Melih Abdulhayohlu that Comodo strictly checks and verifies that applicants are who they claim to be, Alden's e-mail hinted that was not always the case. At the time of the Comodo hack on March 15, nine percent of Comodo partners could place SSL certificate orders using their own domain-control processes instead of Comodo's, Alden wrote. Comodo's process consists of sending and confirming the receipt of an e-mail to an address on the domain to be validated or to the address listed on the domain's WHOIS entry.

Alden said the compromised partner was allowed to implement a separate process because the RA "did a good job of validating domain control," had a "good and close relationship" with a small number of customers, and "spoke the same language" as those customers. Comodo had given the partner leeway because it had not considered that attackers might compromise the partner, Alden said.

Comodo now requires all "100 percent" of registration authorities to use the Comodo-driven process or have Comodo handle the validation, Alden said. Abdulhayoglu recently told eWEEK that Comodo requires applicants to verify their identity and domain ownership, such as by submitting a notarized letter.

"In the case of Comodo, [there have been] enough incidents to prove they are not able to run a proper CA and [could put] the whole Internet community in danger," said van Brouwershaven. Comodo reportedly issued bad certificates for Mozilla back in 2008, according to Paul C. Bryan, also on the list.

The issue boils down to a matter of trust. Abdulhayoglu  had frequently railed against other certificate authorities for "weakening the padlock, [SSL certificate on the browser]" because they do not perform any validations and just rubber-stamp applications. For van Brouwershaven and others, the trust issues can be put directly at Comodo's feet.

"Who will trust the CA model in general if we do not pull the root from all the browsers from a CA that is clearly not able to do the job?" van Brouwershaven wrote, noting that the whole model depended on being able to remove problem roots.

Bryan noted there was no incentive for browsers to act, since pulling the root authority would potentially breaking "thousands of so-called secure Web sites."  Such a move would be especially "unattractive to browser vendors, who have consistently avoided adversely affecting the experience of their users," Bryan wrote. For that kind of a boycott to happen, a consortium of browser vendors would have to work together collectively to make such decisions, Bryan said.



 
 
 
 
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel