Re: [Security-sig] Unified TLS API for Python: Draft 3

2017-02-10 Thread Wes Turner
On Fri, Feb 10, 2017 at 11:22 AM, Cory Benfield wrote: > > On 10 Feb 2017, at 17:20, Wes Turner wrote: > > I learned about oscrypto: > > - oscrypto: "TLS (SSL) sockets, key generation, encryption, decryption, > signing, verification and KDFs using the OS

Re: [Security-sig] Unified TLS API for Python: Draft 3

2017-02-10 Thread Cory Benfield
> On 10 Feb 2017, at 17:20, Wes Turner wrote: > > I learned about oscrypto: > > - oscrypto: "TLS (SSL) sockets, key generation, encryption, decryption, > signing, verification and KDFs using the OS crypto libraries. Does not > require a compiler, and relies on the OS

Re: [Security-sig] Unified TLS API for Python: Draft 3

2017-02-10 Thread Wes Turner
On Fri, Jan 27, 2017 at 9:30 AM, Wes Turner wrote: > > > On Fri, Jan 27, 2017 at 3:10 AM, Cory Benfield wrote: > >> >> On 26 Jan 2017, at 21:17, Donald Stufft wrote: >> >> >> On Jan 26, 2017, at 4:18 AM, Cory Benfield

Re: [Security-sig] Unified TLS API for Python: Draft 3

2017-01-27 Thread Wes Turner
On Fri, Jan 27, 2017 at 3:10 AM, Cory Benfield wrote: > > On 26 Jan 2017, at 21:17, Donald Stufft wrote: > > > On Jan 26, 2017, at 4:18 AM, Cory Benfield wrote: > > For this reason I’m inclined to lean towards the more verbose approach of

Re: [Security-sig] Unified TLS API for Python: Draft 3

2017-01-27 Thread Cory Benfield
> On 26 Jan 2017, at 21:17, Donald Stufft wrote: > > >> On Jan 26, 2017, at 4:18 AM, Cory Benfield > > wrote: >> >> For this reason I’m inclined to lean towards the more verbose approach of >> just writing down what all of the

Re: [Security-sig] Unified TLS API for Python: Draft 3

2017-01-26 Thread Donald Stufft
> On Jan 26, 2017, at 4:18 AM, Cory Benfield wrote: > > For this reason I’m inclined to lean towards the more verbose approach of > just writing down what all of the cipher suites are in an enum. That way, it > gets much easier to validate what’s going on. There’s still no