which ssl backend and how to keep ca updated

[xquery]

No description provided.

[jay]

The OpenSSL backend has a disproportionately large user base so that's what I would use. The ca I would use curl's lib/mk-ca-bundle.pl and if possible find some way to automate adding it to the image.

edit: Do docker images have their own certificate bundle? If so then why not use that?

[xquery]

On Thu, 2 May 2019 at 21:33, Jay Satiro ***@***.***> wrote: The OpenSSL backend has a disproportionately large user base so that's what I would use. The ca I would use curl's lib/mk-ca-bundle.pl <https://github.com/curl/curl/blob/curl-7_64_1/lib/mk-ca-bundle.pl> and if possible find some way to automate adding it to the image.

good point - as suggested previously - going to use the good idea of using the survey to drive what options are enabled and auditing the various platforms enabled features/build options to see how to 'thread the needle(s)' . I also wondered about the idea of a dynamic docker build eg. click these options and build a custom docker image ... thats obviously off topic and a distraction but maybe something I will do as an adjunct shell script. still working ... Jim

…

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFHHSG63DR7FYOQXOBIAYDPTM6XZANCNFSM4HJ5G6JA> .

[xquery]

with alpine it seemed simple enough to use

apk add --no-cache ca-certificates

as proposed by the fix #6