[C-safe-secure-studygroup] C-safe-secure-studygroup Digest, Vol 2, Issue 2

Andrew Banks andrew at andrewbanks.com
Tue Jan 3 16:32:36 UTC 2017


Fine by me...

Andrew

-----Original Message-----
From: C-safe-secure-studygroup [mailto:c-safe-secure-studygroup-bounces at lists.trustable.io] On Behalf Of c-safe-secure-studygroup-request at lists.trustable.io
Sent: 03 January 2017 15:21
To: c-safe-secure-studygroup at lists.trustable.io
Subject: C-safe-secure-studygroup Digest, Vol 2, Issue 2
Importance: Low

Send C-safe-secure-studygroup mailing list submissions to
	c-safe-secure-studygroup at lists.trustable.io

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup

or, via email, send a message with subject or body 'help' to
	c-safe-secure-studygroup-request at lists.trustable.io

You can reach the person managing the list at
	c-safe-secure-studygroup-owner at lists.trustable.io

When replying, please edit your Subject line so it is more specific than "Re: Contents of C-safe-secure-studygroup digest..."


Today's Topics:

   1. Re: Can we make this list public, please? (Barton Miller)
   2. Re: Can we make this list public, please? (Wheeler, David A)
   3. Re: Can we make this list public, please? (Clive Pygott)


----------------------------------------------------------------------

Message: 1
Date: Tue, 03 Jan 2017 09:07:57 -0600
From: Barton Miller <bart at cs.wisc.edu>
To: Joe Jarzombek <Joe.Jarzombek at synopsys.com>,
	c-safe-secure-studygroup at lists.trustable.io
Subject: Re: [C-safe-secure-studygroup] Can we make this list public,
	please?
Message-ID: <52164ECE-C053-4505-94D4-9681549C8E77 at cs.wisc.edu>
Content-Type: text/plain; charset="utf-8"

+1

> On Jan 3, 2017, at 8:36 AM, Joe Jarzombek via C-safe-secure-studygroup <c-safe-secure-studygroup at lists.trustable.io> wrote:
> 
> +1
> 
> Joe J
> 
> Sent from my Android phone using Symantec TouchDown (www.symantec.com)
> 
> -----Original Message-----
> From: Robert Seacord via C-safe-secure-studygroup 
> [c-safe-secure-studygroup at lists.trustable.io]
> Received: Tuesday, 03 Jan 2017, 7:26AM
> To: Paul Sherwood [paul.sherwood at codethink.co.uk]; 
> c-safe-secure-studygroup at lists.trustable.io 
> [c-safe-secure-studygroup at lists.trustable.io]
> Subject: Re: [C-safe-secure-studygroup] Can we make this list public, please?
> 
> i have no objections.  we can also add this to the agenda for tomorrow. 
> 
> rCs
> 
>> On Tue, Jan 3, 2017 at 7:34 AM, Paul Sherwood via C-safe-secure-studygroup <c-safe-secure-studygroup at lists.trustable.io> wrote:
>> Hi all,
>> picking up on David's comment [1] that we should aim to negotiate early with ISO if we hope to achieve wide adoption by avoiding a paid-for output, please can we consider having the existence and archives of this list open to public view? That way, the body of work of these discussions is clearly free without need for negotiation, and I think this would set the scene for discussions with other bodies (MISRA, for example).
>> 
>> Does anyone object to this?
>> 
>> Can we get a round of +/- 1 votes?
>> 
>> br
>> Paul
>> 
>> [1] 
>> https://lists.trustable.io/cgi-bin/mailman/private/c-safe-secure-stud
>> ygroup/2016-December/000018.html
>> 
>> _______________________________________________
>> C-safe-secure-studygroup mailing list 
>> C-safe-secure-studygroup at lists.trustable.io
>> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-stu
>> dygroup
> 
> _______________________________________________
> C-safe-secure-studygroup mailing list
> C-safe-secure-studygroup at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-stud
> ygroup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.trustable.io/cgi-bin/mailman/private/c-safe-secure-studygroup/attachments/20170103/bf8a5115/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 3 Jan 2017 10:15:49 -0500
From: "Wheeler, David A" <dwheeler at ida.org>
To: Paul Sherwood <paul.sherwood at codethink.co.uk>,
	"c-safe-secure-studygroup at lists.trustable.io"
	<c-safe-secure-studygroup at lists.trustable.io>
Subject: Re: [C-safe-secure-studygroup] Can we make this list public,
	please?
Message-ID:
	<9F8E44BC27E22046B84EC1B9364C66A1B5A3CCA41D at EXCH07-4850.ida.org>
Content-Type: text/plain; charset="utf-8"

+1 for public view.  As has often been noted, sunlight is the best disinfectant.

> -----Original Message-----
> From: C-safe-secure-studygroup [mailto:c-safe-secure-studygroup- 
> bounces at lists.trustable.io] On Behalf Of Paul Sherwood via 
> C-safe-secure- studygroup
> Sent: Tuesday, January 03, 2017 7:35 AM
> To: c-safe-secure-studygroup at lists.trustable.io
> Subject: [C-safe-secure-studygroup] Can we make this list public, please?
> 
> Hi all,
> picking up on David's comment [1] that we should aim to negotiate 
> early with ISO if we hope to achieve wide adoption by avoiding a 
> paid-for output, please can we consider having the existence and 
> archives of this list open to public view? That way, the body of work 
> of these discussions is clearly free without need for negotiation, and 
> I think this would set the scene for discussions with other bodies (MISRA, for example).
> 
> Does anyone object to this?
> 
> Can we get a round of +/- 1 votes?
> 
> br
> Paul
> 
> [1]
> https://lists.trustable.io/cgi-bin/mailman/private/c-safe-secure-
> studygroup/2016-December/000018.html
> 
> _______________________________________________
> C-safe-secure-studygroup mailing list
> C-safe-secure-studygroup at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-stud
> ygroup

------------------------------

Message: 3
Date: Tue, 3 Jan 2017 15:21:24 +0000
From: Clive Pygott <clivepygott at gmail.com>
To: c-safe-secure-studygroup at lists.trustable.io
Subject: Re: [C-safe-secure-studygroup] Can we make this list public,
	please?
Message-ID:
	<CABXWzyavWm9Eru2F+M1ij+xfQJppa04u6L5qjKKHw=N=wEypLA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

+1   as well

(though I think it should be the accumulated result, currently +7  to save you having to scroll through all posts)

            Clive



On Tue, Jan 3, 2017 at 3:07 PM, Barton Miller via C-safe-secure-studygroup < c-safe-secure-studygroup at lists.trustable.io> wrote:

> +1
>
> On Jan 3, 2017, at 8:36 AM, Joe Jarzombek via C-safe-secure-studygroup 
> < c-safe-secure-studygroup at lists.trustable.io> wrote:
>
> +1
>
> Joe J
>
> Sent from my Android phone using Symantec TouchDown (www.symantec.com)
>
> -----Original Message-----
> *From:* Robert Seacord via C-safe-secure-studygroup [ 
> c-safe-secure-studygroup at lists.trustable.io]
> *Received:* Tuesday, 03 Jan 2017, 7:26AM
> *To:* Paul Sherwood [paul.sherwood at codethink.co.uk]; 
> c-safe-secure-studygroup at lists.trustable.io [c-safe-secure-studygroup@ 
> lists.trustable.io]
> *Subject:* Re: [C-safe-secure-studygroup] Can we make this list 
> public, please?
>
> i have no objections.  we can also add this to the agenda for tomorrow.
>
> rCs
>
> On Tue, Jan 3, 2017 at 7:34 AM, Paul Sherwood via 
> C-safe-secure-studygroup <c-safe-secure-studygroup at lists.trustable.io> wrote:
>
>> Hi all,
>> picking up on David's comment [1] that we should aim to negotiate 
>> early with ISO if we hope to achieve wide adoption by avoiding a 
>> paid-for output, please can we consider having the existence and 
>> archives of this list open to public view? That way, the body of work 
>> of these discussions is clearly free without need for negotiation, 
>> and I think this would set the scene for discussions with other bodies (MISRA, for example).
>>
>> Does anyone object to this?
>>
>> Can we get a round of +/- 1 votes?
>>
>> br
>> Paul
>>
>> [1] https://lists.trustable.io/cgi-bin/mailman/private/c-safe-se
>> cure-studygroup/2016-December/000018.html
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.trustable
>> .io_cgi-2Dbin_mailman_private_c-2Dsafe-2Dsecure-2Dstudygroup_2016-2DD
>> ecember_000018.html&d=DgMFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uxVVCWR8UcUye
>> akFZXcD5bxiMa6Nx1hPouclYdJYz00&m=VuNJKVR5CvOpSNDQUpxaGK3nnUWpX8wty2DC
>> kFgmW4I&s=jS5G6AE9D-Mx8Eiw43iVgYsKPjJmHy1ZV4saKbMDDKE&e=>
>>
>> _______________________________________________
>> C-safe-secure-studygroup mailing list 
>> C-safe-secure-studygroup at lists.trustable.io
>> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-s
>> ecure-studygroup
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.trustable
>> .io_cgi-2Dbin_mailman_listinfo_c-2Dsafe-2Dsecure-2Dstudygroup&d=DgMFa
>> Q&c=DPL6_X_6JkXFx7AXWqB0tg&r=uxVVCWR8UcUyeakFZXcD5bxiMa6Nx1hPouclYdJY
>> z00&m=VuNJKVR5CvOpSNDQUpxaGK3nnUWpX8wty2DCkFgmW4I&s=btdY62SF6WSTzErG7
>> Quij6rVFSUtShHovbOQ9ZT-4i8&e=>
>>
>
> _______________________________________________
> C-safe-secure-studygroup mailing list
> C-safe-secure-studygroup at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-
> safe-secure-studygroup
>
>
> _______________________________________________
> C-safe-secure-studygroup mailing list
> C-safe-secure-studygroup at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-
> safe-secure-studygroup
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.trustable.io/cgi-bin/mailman/private/c-safe-secure-studygroup/attachments/20170103/408eb743/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
C-safe-secure-studygroup mailing list
C-safe-secure-studygroup at lists.trustable.io
https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup


------------------------------

End of C-safe-secure-studygroup Digest, Vol 2, Issue 2
******************************************************




More information about the C-safe-secure-studygroup mailing list