Re: PKCS#11 vs OpenSSL (BIND Future Development Question)

2018-06-04 Thread Ondřej Surý
> On 4 Jun 2018, at 10:21, Mathieu Arnold wrote: > > On Sun, Jun 03, 2018 at 06:00:08AM +, Ondřej Surý wrote: >> The PKCS#11 interface is very fragile, as the different vendors implement >> different parts of the >> standard, and BIND needs to be compiled with a specific PKCS#11 provider

Re: PKCS#11 vs OpenSSL (BIND Future Development Question)

2018-06-04 Thread Mathieu Arnold
On Sun, Jun 03, 2018 at 06:00:08AM +, Ondřej Surý wrote: > The PKCS#11 interface is very fragile, as the different vendors implement > different parts of the > standard, and BIND needs to be compiled with a specific PKCS#11 provider > defined at the > compile time. This is certainly

Re: PKCS#11 vs OpenSSL (BIND Future Development Question)

2018-06-03 Thread Timothe Litt
On 03-Jun-18 02:00, Ondřej Surý wrote: > Hi all, > > BIND 9 currently supports two major cryptography provider libraries - > OpenSSL[1] and PKCS#11. > > The PKCS#11 interface is very fragile, as the different vendors implement > different parts of the > standard, and BIND needs to be compiled

PKCS#11 vs OpenSSL (BIND Future Development Question)

2018-06-03 Thread Ondřej Surý
Hi all, BIND 9 currently supports two major cryptography provider libraries - OpenSSL[1] and PKCS#11. The PKCS#11 interface is very fragile, as the different vendors implement different parts of the standard, and BIND needs to be compiled with a specific PKCS#11 provider defined at the