[cabfpub] Discussion Draft for Revisions to Bylaws

Dean Coclin Dean_Coclin at symantec.com
Wed Nov 27 00:42:14 UTC 2013

The CABF hasn't traditionally dealt with secure email, only web SSL and Code
signing.  So that's why I assume Ben didn't include that. Are you suggesting
an expanded scope?

-----Original Message-----
From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org] On
Behalf Of Gervase Markham
Sent: Tuesday, November 26, 2013 3:32 PM
To: ben at digicert.com; 'CABFPub'
Subject: Re: [cabfpub] Discussion Draft for Revisions to Bylaws

On 25/11/13 05:44, Ben Wilson wrote:
> (3)          Browser/Platform Provider: The member organization manages
> a root store as a major provider of a software product used by the 
> general public: (a) to browse the Web securely or (b) to authenticate 
> digitally signed code.

Works for me, although we should probably complete the set by adding "or
(c) to authenticate digitally signed email".

Public mailing list
Public at cabforum.org
-------------- 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/20131126/498852c6/attachment-0001.p7s>

More information about the Public mailing list