Is anyone tracking the number of forged certs issued by @startssl? One vuln in one CA puts the whole system at risk:
http://oalmanna.blogspot.in/2016/03/startssl-domain-validation.html …
-
-
Replying to @MalwareJake
@MalwareJake@startssl Or did they validate? The email address entered is in the WHOIS database. We may never know..pic.twitter.com/FNOiQLvSDU
2 replies 1 retweet 0 likes -
Replying to @wdormann
@wdormann@MalwareJake@startssl i'm not "legally" authorized to demonstrate this vulnerability for any other domain name that i don't own.2 replies 0 retweets 1 like -
Replying to @osamaalmann
@AsoomAlma
@MalwareJake@startssl Using an email in the WHOIS isn't a valid test. Couldn't you have used a different email that you own?2 replies 0 retweets 0 likes -
Replying to @MalwareJake
@MalwareJake@wdormann I genuinely, didn't think of that during the test.1 reply 0 retweets 0 likes -
Replying to @osamaalmann
@AsoomAlma
@MalwareJake All we can do at this point is to take@startssl 's word on what verification was happening on the server side.1 reply 0 retweets 0 likes
@AsoomAlma @MalwareJake Per @startssl, the only reason the email was accepted was because it was listed in the WHOIS database.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.