[cabfpub] Chrome security warning discrepancy?

Dean Coclin Dean_Coclin at symantec.com
Mon Jan 26 19:05:23 UTC 2015

I don't think Ben meant to be literal in his comment, but rather was
pointing out that it would be useful for consumers and end users to be able
to use different browsers and see similar and consistent warning
information, similar to international traffic signs. We all know what a red
octagon means even though in Puerto Rico it says, "Pare". When we see it, we
put our foot on the brake.  Could similar behavior be ingrained in end users
if all browsers had consistent security signs? Perhaps more study is


As some of you know, the forum has never been able to place requirements on
browsers, yet the opposite is true. 




From: Tony Rutkowski [mailto:tony at yaanatech.com] 
Sent: Monday, January 26, 2015 10:58 AM
To: Ben Wilson; Stephen Davidson; Dean Coclin; CABFPub (public at cabforum.org)
Subject: Re: [cabfpub] Chrome security warning discrepancy?



You want a widely accepted industry specification,
and this is exactly what the CA/B Forum exists for.

If you look at the RSS Convention, it was done in
1968.  There appear to be only a few dozen signatories
with many notable omissions.  Similarly, few nations
even participate in the related body.

For a browser security indicator, you couldn't even
begin to get Nation States to discuss a subject 
that plainly is not properly a subject of public
international law.

The Forum should be pursuing and evangelizing 
its own work here rather than fantasizing over

--tony, esq.

On 2015-01-25 10:25 AM, Ben Wilson wrote:

Time for an international treaty on browser security indicators?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20150126/d642fd10/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6130 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/public/attachments/20150126/d642fd10/attachment-0001.p7s>

More information about the Public mailing list