Explaining the growing array of Chrome SSL warnings ...https://twitter.com/digicert/status/598555115117772801 …
-
-
Replying to @ivanristic
@ivanristic@Cryptoki You call them Chrome bugs, I call them CA bugs. Split the difference? ;)1 reply 0 retweets 2 likes -
Replying to @sleevi_
@sleevi_@ivanristic@Cryptoki I think it's better to just admit Chrome is messed up right now. Firefox was messed up for a *long* time.1 reply 0 retweets 2 likes -
Replying to @BRIAN_____
@BRIAN_____@ivanristic@Cryptoki Understandably, I'll disagree :) Chrome is accurately complaining about things that will cause it problems1 reply 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_@ivanristic@Cryptoki Surely it is not OK to let site X to degrade the security indicators for an unrelated (but same CA) site Y?1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____@ivanristic@Cryptoki When that particular case happens in Chrome, the CA is at fault, so I have a harder time being sympathetic2 replies 0 retweets 0 likes
@sleevi_ @ivanristic @Cryptoki Nobody should be surprised that people have an even harder time sympathizing with that lack of sympathy. :)
-
-
Replying to @BRIAN_____
@BRIAN_____@ivanristic@Cryptoki At some point, people will realize that even if CAs are held to the same standards, not all are equal...0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.